- Implementation of specialist execution api, including SSE protocol
- eveai_chat becomes deprecated and should be replaced with SSE - Adaptation of STANDARD_RAG specialist - Base class definition allowing to realise specialists with crewai framework - Implementation of SPIN_SPECIALIST - Implementation of test app for testing specialists (test_specialist_client). Also serves as an example for future SSE-based client - Improvements to startup scripts to better handle and scale multiple connections - Small improvements to the interaction forms and views - Caching implementation improved and augmented with additional caches
This commit is contained in:
@@ -1,12 +1,21 @@
|
||||
version: "1.0.0"
|
||||
name: "Define Identification Questions"
|
||||
task_description: >
|
||||
Ask questions to complete or confirm the identification information gathered.
|
||||
Current Identification Information:
|
||||
$$${Identification}$$$
|
||||
Gather the identification information gathered by your team mates , take into account the history (in between triple
|
||||
backquotes) of the conversation, and the latest reply of the user.
|
||||
Define questions to be asked to complete the personal and company information for the end user in the conversation.
|
||||
history:
|
||||
```{history}```
|
||||
latest reply:
|
||||
{query}
|
||||
|
||||
{custom_description}
|
||||
expected_output: >
|
||||
Top 2 questions to ask in order to complete identification.
|
||||
- Personal Identification information such as name, email, phone number, job title, and any additional information that
|
||||
may prove to be interesting in the current or future conversations.
|
||||
- Company information such as company name, industry, size, company website, ...
|
||||
{custom_expected_output}
|
||||
- Top {nr_of_questions} questions to ask in order to complete identification.
|
||||
{custom_expected_output}
|
||||
metadata:
|
||||
author: "Josako"
|
||||
|
||||
Reference in New Issue
Block a user