d106520d22
- Split differrent caching mechanisms (types, version tree, config) into different cachers - Improve resource usage on starting components, and correct gevent usage - Refine repopack usage for eveai_app (too large) - Change nginx dockerfile to allow for specialist overviews being served statically
27 lines
1.2 KiB
YAML
27 lines
1.2 KiB
YAML
version: "1.0.0"
|
|
name: "SPIN Question Identification"
|
|
task_description: >
|
|
Define, taking into account the history of the discussion (in between triple %), the latest reply and the currently
|
|
known SPIN-elements (in between triple $), the top questions that need to be asked to understand the full SPIN context
|
|
of the customer. If you think this user could be a potential customer, please indicate so.
|
|
{custom_description}
|
|
Use the following {tenant_language} to define the SPIN-elements. If you have a full SPIN context, just skip and don't
|
|
ask for more information or confirmation.
|
|
History:
|
|
%%%{history}%%%
|
|
Known SPIN:
|
|
$$${SPIN}$$$
|
|
Latest reply:
|
|
{question}
|
|
expected_output: >
|
|
The SPIN questions:
|
|
- At max {nr_of_spin_questions} questions to complete the SPIN-context of the customer, as a markdown list without '```'.
|
|
Potential Customer Indication:
|
|
- An indication if - given the current SPIN - this could be a good customer (True) or not (False).
|
|
{custom_expected_output}
|
|
metadata:
|
|
author: "Josako"
|
|
date_added: "2025-01-08"
|
|
description: "A Task that identifies questions to complete the SPIN context in a conversation"
|
|
changes: "Initial version"
|