- Move global config files to globals iso global folder, as the name global conflicts with python language
- Creation of Traicie Vancancy Definition specialist - Allow to invoke non-interaction specialists from withing Evie's mgmt interface (eveai_app) - Improvements to crewai specialized classes - Introduction to json editor for showing specialists arguments and results in a better way - Introduction of more complex pagination (adding extra arguments) by adding a global 'get_pagination_html' - Allow follow-up of ChatSession / Specialist execution - Improvement in logging of Specialists (but needs to be finished)
This commit is contained in:
37
config/tasks/traicie/TRAICIE_GET_KO_CRITERIA_TASK/1.0.0.yaml
Normal file
37
config/tasks/traicie/TRAICIE_GET_KO_CRITERIA_TASK/1.0.0.yaml
Normal file
@@ -0,0 +1,37 @@
|
||||
version: "1.0.0"
|
||||
name: "Get KO Criteria"
|
||||
task_description: >
|
||||
You are provided with a vacancy text, in beween triple backquotes.
|
||||
Use logical reasoning based on the realities of the job, taking into account:
|
||||
• The job title
|
||||
• The content of the job description
|
||||
• Typical characteristics of similar roles
|
||||
|
||||
Identify the minimum requirements that are absolutely essential to perform the job properly – even if they are not
|
||||
explicitly stated in the text.
|
||||
|
||||
Assess the job within its specific context and ask yourself questions such as:
|
||||
• Does the job require physical stamina?
|
||||
• Is weekend or shift work involved?
|
||||
• Is contact with certain materials (e.g. meat, chemicals) unavoidable?
|
||||
• Is independent working essential?
|
||||
• Is knowledge of a specific language or system critical for customer interaction or safety?
|
||||
• Are there any specific characteristics, contexts, or requirements so obvious that they are often left unstated, yet essential to perform the job?
|
||||
|
||||
Create a prioritised list of the 5 most critical knock-out criteria, ranked by importance.
|
||||
|
||||
Treat this as a logical and professional reasoning exercise.
|
||||
Respect the language of the vacancy text, and return answers / output in the same language.
|
||||
{custom_description}
|
||||
|
||||
Vacancy Text:
|
||||
```{vacancy_text}```
|
||||
|
||||
expected_output: >
|
||||
A list of title and description of the (knock-out) criteria for the given vacancy text.
|
||||
{custom_expected_output}
|
||||
metadata:
|
||||
author: "Josako"
|
||||
date_added: "2025-01-25"
|
||||
description: "A Task to collect all KO criteria from a vacancy text"
|
||||
changes: "Initial version"
|
||||
Reference in New Issue
Block a user