Spaces:
Runtime error
Runtime error
Update prompts.yaml
Browse files- prompts.yaml +27 -26
prompts.yaml
CHANGED
@@ -255,25 +255,26 @@ update_facts_post_messages: |-
|
|
255 |
update_plan_pre_messages: |-
|
256 |
You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.
|
257 |
You have been given a task:
|
258 |
-
{{task}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
259 |
|
260 |
-
|
261 |
-
|
262 |
-
|
|
|
|
|
|
|
263 |
|
264 |
-
|
265 |
-
You
|
266 |
-
{{task}}
|
267 |
-
|
268 |
-
You can leverage these tools:
|
269 |
-
{%- for tool in tools.values() %}
|
270 |
-
- {{ tool.name }}: {{ tool.description }}
|
271 |
-
Takes inputs: {{tool.inputs}}
|
272 |
-
Returns an output of type: {{tool.output_type}}
|
273 |
-
{%- endfor %}
|
274 |
|
275 |
-
{%- if managed_agents and managed_agents.values() | list %}
|
276 |
-
You can also give tasks to team members.
|
277 |
Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.
|
278 |
Given that this team member is a real human, you should be very verbose in your task, it should be a long string providing informations as detailed as necessary.
|
279 |
Here is a list of the team members that you can call:
|
@@ -284,16 +285,16 @@ Here is a list of the team members that you can call:
|
|
284 |
{%- endif %}
|
285 |
|
286 |
Here is the up to date list of facts that you know:
|
287 |
-
{{facts_update}}
|
288 |
-
|
289 |
-
Now for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
|
290 |
-
This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
|
291 |
-
Beware that you have {remaining_steps} steps remaining.
|
292 |
-
Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
|
293 |
-
After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
|
294 |
-
|
295 |
-
Now write your new plan below.
|
296 |
-
|
297 |
managed_agent:
|
298 |
task: |-
|
299 |
You're a helpful agent named '{{name}}'.
|
|
|
255 |
update_plan_pre_messages: |-
|
256 |
You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.
|
257 |
You have been given a task:
|
258 |
+
{{task}}
|
259 |
+
|
260 |
+
Find below the record of what has been tried so far to solve it. Then you will be asked to make an updated plan to solve the task.
|
261 |
+
If the previous tries so far have met some success, you can make an updated plan based on these actions.
|
262 |
+
If you are stalled, you can make a completely new plan starting from scratch.
|
263 |
+
|
264 |
+
update_plan_post_messages: |-
|
265 |
+
You're still working towards solving this task:
|
266 |
+
{{task}}
|
267 |
|
268 |
+
You can leverage these tools:
|
269 |
+
{%- for tool in tools.values() %}
|
270 |
+
- {{ tool.name }}: {{ tool.description }}
|
271 |
+
Takes inputs: {{tool.inputs}}
|
272 |
+
Returns an output of type: {{tool.output_type}}
|
273 |
+
{%- endfor %}
|
274 |
|
275 |
+
{%- if managed_agents and managed_agents.values() | list %}
|
276 |
+
You can also give tasks to team members.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
277 |
|
|
|
|
|
278 |
Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.
|
279 |
Given that this team member is a real human, you should be very verbose in your task, it should be a long string providing informations as detailed as necessary.
|
280 |
Here is a list of the team members that you can call:
|
|
|
285 |
{%- endif %}
|
286 |
|
287 |
Here is the up to date list of facts that you know:
|
288 |
+
{{facts_update}}
|
289 |
+
|
290 |
+
Now for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
|
291 |
+
This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
|
292 |
+
Beware that you have {remaining_steps} steps remaining.
|
293 |
+
Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
|
294 |
+
After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
|
295 |
+
|
296 |
+
Now write your new plan below.
|
297 |
+
|
298 |
managed_agent:
|
299 |
task: |-
|
300 |
You're a helpful agent named '{{name}}'.
|