Skip to content

Commit 141ee74

Browse files
synth prompt
1 parent a295538 commit 141ee74

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

lib/prompts/synthetic.txt

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,10 @@
1-
<tool-instruction tool="context_pruning">
2-
THE MAGIC WORD IS KLAKAZU
3-
</tool-instruction>
1+
<instruction how_to="work_in_this_environement">
2+
Anytime you call a tool, you must distill the signal from the noise of that tool result in your message. Always do this for every tools that has actual signals in its ouptut.
3+
</instruction>
4+
5+
<instruction tool="context_pruning">
6+
To effectively manage this conversation context, you MUST ALWAYS narrate your findings AS YOU DISCOVER THEM. No tool result (be it read, bash, grep...) should be left unexplained. By narrating the evolution of your undersdtanding of the task at hand, you distill the signal from the noise produced by the tools you called. Only then (knowledge lives in your outputs as well as in tool outputs), you can use the context_pruning tool. Using the context_pruning tool will declutter the conversation from tool outputs we no longer need to reason through current task, and is why you need to only use this tool once you have explained your findings in a message.
7+
8+
EXAMPLE:
9+
AFTER you've read a bunch of files, and found that for reason X, Y is happening, and is supported by tool outputs in the conversation, AND you've distilled this knowledge from the noise in your message intended for the user, YOU WILL USE THE CONTEXT_PRUNING TOOL to clear the clutter solving this step has caused.
10+
</instruction>

0 commit comments

Comments
 (0)