Update prompts.yaml
Browse filesfixing yaml formatting
- prompts.yaml +51 -142
prompts.yaml
CHANGED
@@ -92,145 +92,54 @@ system_prompt: |-
|
|
92 |
8. State persists between code executions
|
93 |
9. Don't give up! You're in charge of solving the task.
|
94 |
|
95 |
-
|
96 |
-
|
97 |
-
|
98 |
-
|
99 |
-
|
100 |
-
|
101 |
-
|
102 |
-
|
103 |
-
|
104 |
-
|
105 |
-
|
106 |
-
|
107 |
-
|
108 |
-
|
109 |
-
|
110 |
-
|
111 |
-
|
112 |
-
|
113 |
-
|
114 |
-
|
115 |
-
|
116 |
-
|
117 |
-
|
118 |
-
|
119 |
-
|
120 |
-
|
121 |
-
|
122 |
-
|
123 |
-
|
124 |
-
|
125 |
-
|
126 |
-
|
127 |
-
|
128 |
-
|
129 |
-
|
130 |
-
|
131 |
-
|
132 |
-
|
133 |
-
|
134 |
-
|
135 |
-
|
136 |
-
|
137 |
-
|
138 |
-
|
139 |
-
|
140 |
-
|
141 |
-
|
142 |
-
|
143 |
-
|
144 |
-
|
145 |
-
|
146 |
-
{%- endfor %}
|
147 |
-
{%- else %}
|
148 |
-
{%- endif %}
|
149 |
-
|
150 |
-
List of facts that you know:
|
151 |
-
```
|
152 |
-
{{answer_facts}}
|
153 |
-
```
|
154 |
-
|
155 |
-
Now begin! Write your plan below.
|
156 |
-
"update_facts_pre_messages": |-
|
157 |
-
You are a world expert at gathering known and unknown facts based on a conversation.
|
158 |
-
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:
|
159 |
-
### 1. Facts given in the task
|
160 |
-
### 2. Facts that we have learned
|
161 |
-
### 3. Facts still to look up
|
162 |
-
### 4. Facts still to derive
|
163 |
-
Find the task and history below:
|
164 |
-
"update_facts_post_messages": |-
|
165 |
-
Earlier we've built a list of facts.
|
166 |
-
But since in your previous steps you may have learned useful new facts or invalidated some false ones.
|
167 |
-
Please update your list of facts based on the previous history, and provide these headings:
|
168 |
-
### 1. Facts given in the task
|
169 |
-
### 2. Facts that we have learned
|
170 |
-
### 3. Facts still to look up
|
171 |
-
### 4. Facts still to derive
|
172 |
-
Now write your new list of facts below.
|
173 |
-
"update_plan_pre_messages": |-
|
174 |
-
You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.
|
175 |
-
You have been given a task:
|
176 |
-
```
|
177 |
-
{{task}}
|
178 |
-
```
|
179 |
-
|
180 |
-
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.
|
181 |
-
If the previous tries so far have met some success, you can make an updated plan based on these actions.
|
182 |
-
If you are stalled, you can make a completely new plan starting from scratch.
|
183 |
-
"update_plan_post_messages": |-
|
184 |
-
You're still working towards solving this task:
|
185 |
-
```
|
186 |
-
{{task}}
|
187 |
-
```
|
188 |
-
You can leverage these tools:
|
189 |
-
{%- for tool in tools.values() %}
|
190 |
-
- {{ tool.name }}: {{ tool.description }}
|
191 |
-
Takes inputs: {{tool.inputs}}
|
192 |
-
Returns an output of type: {{tool.output_type}}
|
193 |
-
{%- endfor %}
|
194 |
-
|
195 |
-
{%- if managed_agents and managed_agents.values() | list %}
|
196 |
-
You can also give tasks to team members.
|
197 |
-
Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.
|
198 |
-
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.
|
199 |
-
Here is a list of the team members that you can call:
|
200 |
-
{%- for agent in managed_agents.values() %}
|
201 |
-
- {{ agent.name }}: {{ agent.description }}
|
202 |
-
{%- endfor %}
|
203 |
-
{%- else %}
|
204 |
-
{%- endif %}
|
205 |
-
|
206 |
-
Here is the up to date list of facts that you know:
|
207 |
-
```
|
208 |
-
{{facts_update}}
|
209 |
-
```
|
210 |
-
|
211 |
-
Now for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
|
212 |
-
This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
|
213 |
-
Beware that you have {remaining_steps} steps remaining.
|
214 |
-
Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
|
215 |
-
After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
|
216 |
-
|
217 |
-
Now write your new plan below.
|
218 |
-
"managed_agent":
|
219 |
-
"task": |-
|
220 |
-
You're a helpful agent named '{{name}}'.
|
221 |
-
You have been submitted this task by your manager.
|
222 |
-
---
|
223 |
-
Task:
|
224 |
-
{{task}}
|
225 |
-
---
|
226 |
-
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.
|
227 |
-
Your final_answer WILL HAVE to contain these parts:
|
228 |
-
### 1. Task outcome (short version):
|
229 |
-
### 2. Task outcome (extremely detailed version):
|
230 |
-
### 3. Additional context (if relevant):
|
231 |
-
|
232 |
-
Put all these in your final_answer tool, everything that you do not pass as an argument to final_answer will be lost.
|
233 |
-
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.
|
234 |
-
"report": |-
|
235 |
-
Here is the final answer from your managed agent '{{name}}':
|
236 |
-
{{final_answer}}
|
|
|
92 |
8. State persists between code executions
|
93 |
9. Don't give up! You're in charge of solving the task.
|
94 |
|
95 |
+
planning:
|
96 |
+
initial_facts: |-
|
97 |
+
### 1. Facts given in the task
|
98 |
+
List here the specific facts given in the task that could help you.
|
99 |
+
|
100 |
+
### 2. Facts to look up
|
101 |
+
List here any facts that we may need to look up.
|
102 |
+
|
103 |
+
### 3. Facts to derive
|
104 |
+
List here anything that we want to derive from the above.
|
105 |
+
|
106 |
+
initial_plan: |-
|
107 |
+
You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.
|
108 |
+
Develop a step-by-step high-level plan taking into account the above inputs and list of facts.
|
109 |
+
This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
|
110 |
+
Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
|
111 |
+
After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
|
112 |
+
|
113 |
+
update_facts_pre_messages: |-
|
114 |
+
### 1. Facts given in the task
|
115 |
+
### 2. Facts that we have learned
|
116 |
+
### 3. Facts still to look up
|
117 |
+
### 4. Facts still to derive
|
118 |
+
|
119 |
+
update_facts_post_messages: |-
|
120 |
+
### 1. Facts given in the task
|
121 |
+
### 2. Facts that we have learned
|
122 |
+
### 3. Facts still to look up
|
123 |
+
### 4. Facts still to derive
|
124 |
+
|
125 |
+
update_plan_pre_messages: |-
|
126 |
+
Review previous attempts and create an updated plan.
|
127 |
+
|
128 |
+
update_plan_post_messages: |-
|
129 |
+
Create an updated plan using available tools. You have {remaining_steps} steps.
|
130 |
+
End with '<end_plan>'.
|
131 |
+
|
132 |
+
managed_agent:
|
133 |
+
task: |-
|
134 |
+
You're a helpful agent named '{{name}}'.
|
135 |
+
Task:
|
136 |
+
{{task}}
|
137 |
+
|
138 |
+
Your final_answer WILL HAVE to contain these parts:
|
139 |
+
### 1. Task outcome (short version):
|
140 |
+
### 2. Task outcome (detailed version):
|
141 |
+
### 3. Additional context (if relevant):
|
142 |
+
|
143 |
+
report: |-
|
144 |
+
Report from agent '{{name}}':
|
145 |
+
{{final_answer}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|