identation Error
Browse files- prompts.yaml +97 -97
prompts.yaml
CHANGED
|
@@ -208,101 +208,101 @@
|
|
| 208 |
|
| 209 |
Here is your task:
|
| 210 |
Task:
|
| 211 |
-
{{task}}
|
| 212 |
-
textYou can leverage these tools:
|
| 213 |
-
{%- for tool in tools.values() -%}
|
| 214 |
-
- {{ tool.name }}: {{ tool.description }}
|
| 215 |
-
|
| 216 |
-
|
| 217 |
-
{%- endfor -%}
|
| 218 |
-
|
| 219 |
-
{%- if managed_agents and managed_agents.values() | list -%}
|
| 220 |
-
You can also give tasks to team members.
|
| 221 |
-
Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'request', a long string explaining your request.
|
| 222 |
-
Given that this team member is a real human, you should be very verbose in your request.
|
| 223 |
-
Here is a list of the team members that you can call:
|
| 224 |
-
{%- for agent in managed_agents.values() -%}
|
| 225 |
-
- {{ agent.name }}: {{ agent.description }}
|
| 226 |
-
{%- endfor -%}
|
| 227 |
-
{%- else -%}
|
| 228 |
-
{%- endif -%}
|
| 229 |
-
|
| 230 |
-
List of facts that you know:
|
| 231 |
-
{{answer_facts}}
|
| 232 |
-
textNow begin! Write your plan below.
|
| 233 |
-
"update_facts_pre_messages": |-
|
| 234 |
-
You are a world expert at gathering known and unknown facts based on a conversation.
|
| 235 |
-
Below you will find a task, and a history of attempts made to solve the task. You will have to produce a list of these:
|
| 236 |
-
### 1. Facts given in the task
|
| 237 |
-
### 2. Facts that we have learned
|
| 238 |
-
### 3. Facts still to look up
|
| 239 |
-
### 4. Facts still to derive
|
| 240 |
-
Find the task and history below:
|
| 241 |
-
"update_facts_post_messages": |-
|
| 242 |
-
Earlier we've built a list of facts.
|
| 243 |
-
But since in your previous steps you may have learned useful new facts or invalidated some false ones.
|
| 244 |
-
Please update your list of facts based on the previous history, and provide these headings:
|
| 245 |
-
### 1. Facts given in the task
|
| 246 |
-
### 2. Facts that we have learned
|
| 247 |
-
### 3. Facts still to look up
|
| 248 |
-
### 4. Facts still to derive
|
| 249 |
-
|
| 250 |
-
Now write your new list of facts below.
|
| 251 |
-
"update_plan_pre_messages": |-
|
| 252 |
-
You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.
|
| 253 |
-
|
| 254 |
-
You have been given a task:
|
| 255 |
-
{{task}}
|
| 256 |
-
textFind 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.
|
| 257 |
-
If the previous tries so far have met some success, you can make an updated plan based on these actions.
|
| 258 |
-
If you are stalled, you can make a completely new plan starting from scratch.
|
| 259 |
-
"update_plan_post_messages": |-
|
| 260 |
-
You're still working towards solving this task:
|
| 261 |
-
{{task}}
|
| 262 |
-
textYou can leverage these tools:
|
| 263 |
-
{%- for tool in tools.values() -%}
|
| 264 |
-
- {{ tool.name }}: {{ tool.description }}
|
| 265 |
-
|
| 266 |
-
|
| 267 |
-
{%- endfor -%}
|
| 268 |
-
|
| 269 |
-
{%- if managed_agents and managed_agents.values() | list -%}
|
| 270 |
-
You can also give tasks to team members.
|
| 271 |
-
Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.
|
| 272 |
-
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.
|
| 273 |
-
Here is a list of the team members that you can call:
|
| 274 |
-
{%- for agent in managed_agents.values() -%}
|
| 275 |
-
- {{ agent.name }}: {{ agent.description }}
|
| 276 |
-
{%- endfor -%}
|
| 277 |
-
{%- else -%}
|
| 278 |
-
{%- endif -%}
|
| 279 |
-
|
| 280 |
-
Here is the up to date list of facts that you know:
|
| 281 |
-
{{facts_update}}
|
| 282 |
-
textNow for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
|
| 283 |
-
This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
|
| 284 |
-
Beware that you have {remaining_steps} steps remaining.
|
| 285 |
-
Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
|
| 286 |
-
After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
|
| 287 |
-
|
| 288 |
-
Now write your new plan below.
|
| 289 |
"managed_agent":
|
| 290 |
-
"task": |-
|
| 291 |
-
You're a helpful agent named '{{name}}'.
|
| 292 |
-
You have been submitted this task by your manager.
|
| 293 |
-
---
|
| 294 |
-
Task:
|
| 295 |
-
{{task}}
|
| 296 |
-
---
|
| 297 |
-
You're helping your manager solve a wider task: so make sure to not provide a one-line answer, but give as much information as possible to give them a clear understanding of the answer.
|
| 298 |
-
|
| 299 |
-
Your final_answer WILL HAVE to contain these parts:
|
| 300 |
-
### 1. Task outcome (short version):
|
| 301 |
-
### 2. Task outcome (extremely detailed version):
|
| 302 |
-
### 3. Additional context (if relevant):
|
| 303 |
-
|
| 304 |
-
Put all these in your final_answer tool, everything that you do not pass as an argument to final_answer will be lost.
|
| 305 |
-
And even if your task resolution is not successful, please return as much context as possible, so that your manager can act upon this feedback.
|
| 306 |
-
"report": |-
|
| 307 |
-
Here is the final answer from your managed agent '{{name}}':
|
| 308 |
-
{{final_answer}}
|
|
|
|
| 208 |
|
| 209 |
Here is your task:
|
| 210 |
Task:
|
| 211 |
+
{{task}}
|
| 212 |
+
textYou can leverage these tools:
|
| 213 |
+
{%- for tool in tools.values() -%}
|
| 214 |
+
- {{ tool.name }}: {{ tool.description }}
|
| 215 |
+
Takes inputs: {{tool.inputs}}
|
| 216 |
+
Returns an output of type: {{tool.output_type}}
|
| 217 |
+
{%- endfor -%}
|
| 218 |
+
|
| 219 |
+
{%- if managed_agents and managed_agents.values() | list -%}
|
| 220 |
+
You can also give tasks to team members.
|
| 221 |
+
Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'request', a long string explaining your request.
|
| 222 |
+
Given that this team member is a real human, you should be very verbose in your request.
|
| 223 |
+
Here is a list of the team members that you can call:
|
| 224 |
+
{%- for agent in managed_agents.values() -%}
|
| 225 |
+
- {{ agent.name }}: {{ agent.description }}
|
| 226 |
+
{%- endfor -%}
|
| 227 |
+
{%- else -%}
|
| 228 |
+
{%- endif -%}
|
| 229 |
+
|
| 230 |
+
List of facts that you know:
|
| 231 |
+
{{answer_facts}}
|
| 232 |
+
textNow begin! Write your plan below.
|
| 233 |
+
"update_facts_pre_messages": |-
|
| 234 |
+
You are a world expert at gathering known and unknown facts based on a conversation.
|
| 235 |
+
Below you will find a task, and a history of attempts made to solve the task. You will have to produce a list of these:
|
| 236 |
+
### 1. Facts given in the task
|
| 237 |
+
### 2. Facts that we have learned
|
| 238 |
+
### 3. Facts still to look up
|
| 239 |
+
### 4. Facts still to derive
|
| 240 |
+
Find the task and history below:
|
| 241 |
+
"update_facts_post_messages": |-
|
| 242 |
+
Earlier we've built a list of facts.
|
| 243 |
+
But since in your previous steps you may have learned useful new facts or invalidated some false ones.
|
| 244 |
+
Please update your list of facts based on the previous history, and provide these headings:
|
| 245 |
+
### 1. Facts given in the task
|
| 246 |
+
### 2. Facts that we have learned
|
| 247 |
+
### 3. Facts still to look up
|
| 248 |
+
### 4. Facts still to derive
|
| 249 |
+
|
| 250 |
+
Now write your new list of facts below.
|
| 251 |
+
"update_plan_pre_messages": |-
|
| 252 |
+
You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.
|
| 253 |
+
|
| 254 |
+
You have been given a task:
|
| 255 |
+
{{task}}
|
| 256 |
+
textFind 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.
|
| 257 |
+
If the previous tries so far have met some success, you can make an updated plan based on these actions.
|
| 258 |
+
If you are stalled, you can make a completely new plan starting from scratch.
|
| 259 |
+
"update_plan_post_messages": |-
|
| 260 |
+
You're still working towards solving this task:
|
| 261 |
+
{{task}}
|
| 262 |
+
textYou can leverage these tools:
|
| 263 |
+
{%- for tool in tools.values() -%}
|
| 264 |
+
- {{ tool.name }}: {{ tool.description }}
|
| 265 |
+
Takes inputs: {{tool.inputs}}
|
| 266 |
+
Returns an output of type: {{tool.output_type}}
|
| 267 |
+
{%- endfor -%}
|
| 268 |
+
|
| 269 |
+
{%- if managed_agents and managed_agents.values() | list -%}
|
| 270 |
+
You can also give tasks to team members.
|
| 271 |
+
Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.
|
| 272 |
+
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.
|
| 273 |
+
Here is a list of the team members that you can call:
|
| 274 |
+
{%- for agent in managed_agents.values() -%}
|
| 275 |
+
- {{ agent.name }}: {{ agent.description }}
|
| 276 |
+
{%- endfor -%}
|
| 277 |
+
{%- else -%}
|
| 278 |
+
{%- endif -%}
|
| 279 |
+
|
| 280 |
+
Here is the up to date list of facts that you know:
|
| 281 |
+
{{facts_update}}
|
| 282 |
+
textNow for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
|
| 283 |
+
This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
|
| 284 |
+
Beware that you have {remaining_steps} steps remaining.
|
| 285 |
+
Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
|
| 286 |
+
After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
|
| 287 |
+
|
| 288 |
+
Now write your new plan below.
|
| 289 |
"managed_agent":
|
| 290 |
+
"task": |-
|
| 291 |
+
You're a helpful agent named '{{name}}'.
|
| 292 |
+
You have been submitted this task by your manager.
|
| 293 |
+
---
|
| 294 |
+
Task:
|
| 295 |
+
{{task}}
|
| 296 |
+
---
|
| 297 |
+
You're helping your manager solve a wider task: so make sure to not provide a one-line answer, but give as much information as possible to give them a clear understanding of the answer.
|
| 298 |
+
|
| 299 |
+
Your final_answer WILL HAVE to contain these parts:
|
| 300 |
+
### 1. Task outcome (short version):
|
| 301 |
+
### 2. Task outcome (extremely detailed version):
|
| 302 |
+
### 3. Additional context (if relevant):
|
| 303 |
+
|
| 304 |
+
Put all these in your final_answer tool, everything that you do not pass as an argument to final_answer will be lost.
|
| 305 |
+
And even if your task resolution is not successful, please return as much context as possible, so that your manager can act upon this feedback.
|
| 306 |
+
"report": |-
|
| 307 |
+
Here is the final answer from your managed agent '{{name}}':
|
| 308 |
+
{{final_answer}}
|