Update prompts.yaml

prompts.yaml

@@ -102,7 +102,7 @@
   3. Always use the right arguments for the tools. DO NOT pass the arguments as a dict as in 'answer = wiki({'query': "What is the place where James Bond lives?"})', but use the arguments directly as in 'answer = wiki(query="What is the place where James Bond lives?")'.
   4. Take care to not chain too many sequential tool calls in the same code block, especially when the output format is unpredictable.
   5. Call a tool only when needed, and never re-do a tool call that you previously did with the exact same parameters.
-  6. Don't name any new variable with the same name as a tool: for instance don't name a variable 'final_answer'.
+ 6. Don't name any new variable with the same name as a tool: for instance don't name a variable 'final_answer'.
   7. Never create any notional variables in our code, as having these in our logs will derail you from the true variables.
   8. You can use imports in your code, but only from the following list of modules: {{authorized_imports}}
   9. The state persists between code executions: so if in one step you've created variables or imported modules, these will all persist.
@@ -233,4 +233,7 @@
     Ensure the answer is clear, concise, and addresses the task requirements.
     If the task requires specific formatting (e.g., sections for outcome and context), include those in the answer.
   "template": |-
-    The final answer to the task is: {{answer}}
+    The final answer to the task is: {{answer}}
+  "post_messages": |-
+    The final answer has been submitted using the `final_answer` tool.
+    Review the results and ensure the task requirements have been fully met.