@elizaos/prompts 2.0.0-alpha.41 → 2.0.0-alpha.44

package/dist/python/prompts.py

@@ -143,7 +143,7 @@ MESSAGE_HANDLER_TEMPLATE = """<task>Generate dialog and actions for the characte
 </providers>
 
 <instructions>
-Write a thought and plan for {{agentName}} and decide what actions to take.
+Write a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.
 
 IMPORTANT ACTION ORDERING RULES:
 - Actions are executed in the ORDER you list them - the order MATTERS!
@@ -164,6 +164,28 @@ IMPORTANT ACTION PARAMETERS:
 - Required parameters MUST be provided; optional parameters can be omitted if not mentioned
 - If you cannot determine a required parameter value, ask the user for clarification in your <text>
 
+EXAMPLE (action parameters):
+User message: "Send a message to @dev_guru on telegram saying Hello!"
+Actions: REPLY,SEND_MESSAGE
+Params:
+<params>
+    <SEND_MESSAGE>
+        <targetType>user</targetType>
+        <source>telegram</source>
+        <target>dev_guru</target>
+        <text>Hello!</text>
+    </SEND_MESSAGE>
+</params>
+
+IMPORTANT PROVIDER SELECTION RULES:
+- Only include providers if they are needed to respond accurately.
+- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see "(Attachments:" in the conversation, you MUST include "ATTACHMENTS" in your providers list
+- If the message asks about or references specific people, include "ENTITIES" in your providers list  
+- If the message asks about relationships or connections between people, include "RELATIONSHIPS" in your providers list
+- If the message asks about facts or specific information, include "FACTS" in your providers list
+- If the message asks about the environment or world context, include "WORLD" in your providers list
+- If no additional context is needed, you may leave the providers list empty.
+
 IMPORTANT CODE BLOCK FORMATTING RULES:
 - If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).
 - ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.
@@ -176,6 +198,7 @@ First, think about what you want to do next and plan your actions. Then, write t
 <keys>
 "thought" should be a short description of what the agent is thinking about and planning.
 "actions" should be a comma-separated list of the actions {{agentName}} plans to take based on the thought, IN THE ORDER THEY SHOULD BE EXECUTED (if none, use IGNORE, if simply responding with text, use REPLY)
+"providers" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use "IGNORE" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)
 "text" should be the text of the next message for {{agentName}} which they will send to the conversation.
 "params" (optional) should contain action parameters when actions require input. Format as nested XML with action name as wrapper.
 </keys>
@@ -188,6 +211,7 @@ Respond using XML format like this:
 <response>
     <thought>Your thought here</thought>
     <actions>ACTION1,ACTION2</actions>
+    <providers>PROVIDER1,PROVIDER2</providers>
     <text>Your response text here</text>
     <params>
         <ACTION1>
@@ -238,7 +262,6 @@ These are the actions or data provider calls that have already been used in this
 "thought" Clearly explain your reasoning for the selected providers and/or action, and how this step contributes to resolving the user's request.
 "action"  Name of the action to execute after providers return (can be empty if no action is needed).
 "providers" List of provider names to call in this step (can be empty if none are needed).
-"params" Optional XML parameters for the selected action. Use nested XML only when the action needs input.
 "isFinish" Set to true only if the task is fully complete.
 </keys>
 
@@ -249,11 +272,6 @@ These are the actions or data provider calls that have already been used in this
   <thought>Your thought here</thought>
   <action>ACTION</action>
   <providers>PROVIDER1,PROVIDER2</providers>
-  <params>
-    <ACTION>
-      <paramName>value</paramName>
-    </ACTION>
-  </params>
   <isFinish>true | false</isFinish>
 </response>
 </output>"""

package/dist/rust/prompts.rs

@@ -139,7 +139,7 @@ pub const MESSAGE_HANDLER_TEMPLATE: &str = r#"<task>Generate dialog and actions
 </providers>
 
 <instructions>
-Write a thought and plan for {{agentName}} and decide what actions to take.
+Write a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.
 
 IMPORTANT ACTION ORDERING RULES:
 - Actions are executed in the ORDER you list them - the order MATTERS!
@@ -160,6 +160,28 @@ IMPORTANT ACTION PARAMETERS:
 - Required parameters MUST be provided; optional parameters can be omitted if not mentioned
 - If you cannot determine a required parameter value, ask the user for clarification in your <text>
 
+EXAMPLE (action parameters):
+User message: "Send a message to @dev_guru on telegram saying Hello!"
+Actions: REPLY,SEND_MESSAGE
+Params:
+<params>
+    <SEND_MESSAGE>
+        <targetType>user</targetType>
+        <source>telegram</source>
+        <target>dev_guru</target>
+        <text>Hello!</text>
+    </SEND_MESSAGE>
+</params>
+
+IMPORTANT PROVIDER SELECTION RULES:
+- Only include providers if they are needed to respond accurately.
+- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see "(Attachments:" in the conversation, you MUST include "ATTACHMENTS" in your providers list
+- If the message asks about or references specific people, include "ENTITIES" in your providers list  
+- If the message asks about relationships or connections between people, include "RELATIONSHIPS" in your providers list
+- If the message asks about facts or specific information, include "FACTS" in your providers list
+- If the message asks about the environment or world context, include "WORLD" in your providers list
+- If no additional context is needed, you may leave the providers list empty.
+
 IMPORTANT CODE BLOCK FORMATTING RULES:
 - If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).
 - ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.
@@ -172,6 +194,7 @@ First, think about what you want to do next and plan your actions. Then, write t
 <keys>
 "thought" should be a short description of what the agent is thinking about and planning.
 "actions" should be a comma-separated list of the actions {{agentName}} plans to take based on the thought, IN THE ORDER THEY SHOULD BE EXECUTED (if none, use IGNORE, if simply responding with text, use REPLY)
+"providers" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use "IGNORE" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)
 "text" should be the text of the next message for {{agentName}} which they will send to the conversation.
 "params" (optional) should contain action parameters when actions require input. Format as nested XML with action name as wrapper.
 </keys>
@@ -184,6 +207,7 @@ Respond using XML format like this:
 <response>
     <thought>Your thought here</thought>
     <actions>ACTION1,ACTION2</actions>
+    <providers>PROVIDER1,PROVIDER2</providers>
     <text>Your response text here</text>
     <params>
         <ACTION1>
@@ -234,7 +258,6 @@ These are the actions or data provider calls that have already been used in this
 "thought" Clearly explain your reasoning for the selected providers and/or action, and how this step contributes to resolving the user's request.
 "action"  Name of the action to execute after providers return (can be empty if no action is needed).
 "providers" List of provider names to call in this step (can be empty if none are needed).
-"params" Optional XML parameters for the selected action. Use nested XML only when the action needs input.
 "isFinish" Set to true only if the task is fully complete.
 </keys>
 
@@ -245,11 +268,6 @@ These are the actions or data provider calls that have already been used in this
   <thought>Your thought here</thought>
   <action>ACTION</action>
   <providers>PROVIDER1,PROVIDER2</providers>
-  <params>
-    <ACTION>
-      <paramName>value</paramName>
-    </ACTION>
-  </params>
   <isFinish>true | false</isFinish>
 </response>
 </output>"#;

package/dist/typescript/index.ts

@@ -155,7 +155,7 @@ export const messageHandlerTemplate = `<task>Generate dialog and actions for the
 </providers>
 
 <instructions>
-Write a thought and plan for {{agentName}} and decide what actions to take.
+Write a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.
 
 IMPORTANT ACTION ORDERING RULES:
 - Actions are executed in the ORDER you list them - the order MATTERS!
@@ -176,6 +176,28 @@ IMPORTANT ACTION PARAMETERS:
 - Required parameters MUST be provided; optional parameters can be omitted if not mentioned
 - If you cannot determine a required parameter value, ask the user for clarification in your <text>
 
+EXAMPLE (action parameters):
+User message: "Send a message to @dev_guru on telegram saying Hello!"
+Actions: REPLY,SEND_MESSAGE
+Params:
+<params>
+    <SEND_MESSAGE>
+        <targetType>user</targetType>
+        <source>telegram</source>
+        <target>dev_guru</target>
+        <text>Hello!</text>
+    </SEND_MESSAGE>
+</params>
+
+IMPORTANT PROVIDER SELECTION RULES:
+- Only include providers if they are needed to respond accurately.
+- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see "(Attachments:" in the conversation, you MUST include "ATTACHMENTS" in your providers list
+- If the message asks about or references specific people, include "ENTITIES" in your providers list  
+- If the message asks about relationships or connections between people, include "RELATIONSHIPS" in your providers list
+- If the message asks about facts or specific information, include "FACTS" in your providers list
+- If the message asks about the environment or world context, include "WORLD" in your providers list
+- If no additional context is needed, you may leave the providers list empty.
+
 IMPORTANT CODE BLOCK FORMATTING RULES:
 - If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with \`\`\` fenced code blocks (specify the language if known, e.g., \`\`\`python).
 - ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.
@@ -188,6 +210,7 @@ First, think about what you want to do next and plan your actions. Then, write t
 <keys>
 "thought" should be a short description of what the agent is thinking about and planning.
 "actions" should be a comma-separated list of the actions {{agentName}} plans to take based on the thought, IN THE ORDER THEY SHOULD BE EXECUTED (if none, use IGNORE, if simply responding with text, use REPLY)
+"providers" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use "IGNORE" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)
 "text" should be the text of the next message for {{agentName}} which they will send to the conversation.
 "params" (optional) should contain action parameters when actions require input. Format as nested XML with action name as wrapper.
 </keys>
@@ -200,6 +223,7 @@ Respond using XML format like this:
 <response>
     <thought>Your thought here</thought>
     <actions>ACTION1,ACTION2</actions>
+    <providers>PROVIDER1,PROVIDER2</providers>
     <text>Your response text here</text>
     <params>
         <ACTION1>
@@ -252,7 +276,6 @@ These are the actions or data provider calls that have already been used in this
 "thought" Clearly explain your reasoning for the selected providers and/or action, and how this step contributes to resolving the user's request.
 "action"  Name of the action to execute after providers return (can be empty if no action is needed).
 "providers" List of provider names to call in this step (can be empty if none are needed).
-"params" Optional XML parameters for the selected action. Use nested XML only when the action needs input.
 "isFinish" Set to true only if the task is fully complete.
 </keys>
 
@@ -263,11 +286,6 @@ These are the actions or data provider calls that have already been used in this
   <thought>Your thought here</thought>
   <action>ACTION</action>
   <providers>PROVIDER1,PROVIDER2</providers>
-  <params>
-    <ACTION>
-      <paramName>value</paramName>
-    </ACTION>
-  </params>
   <isFinish>true | false</isFinish>
 </response>
 </output>`;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@elizaos/prompts",
   "private": false,
-  "version": "2.0.0-alpha.41",
+  "version": "2.0.0-alpha.44",
   "description": "Shared prompt templates for elizaOS across TypeScript, Python, and Rust",
   "type": "module",
   "main": "./dist/typescript/index.ts",
@@ -23,10 +23,9 @@
     "build:plugin-action-spec": "node scripts/generate-plugin-action-spec.js",
     "check:secrets": "node scripts/check-secrets.js",
     "clean": "rm -rf dist",
-    "lint": "bunx @biomejs/biome check --write --unsafe .",
+    "lint": "bunx @biomejs/biome check --write .",
     "lint:check": "bunx @biomejs/biome check .",
-    "typecheck": "echo 'No TypeScript source files to check'",
-    "test": "node --test test/*.test.js"
+    "typecheck": "echo 'No TypeScript source files to check'"
   },
   "files": [
     "prompts/",
@@ -44,5 +43,5 @@
   "publishConfig": {
     "access": "public"
   },
-  "gitHead": "b3e37e421bcd49b6bc7a34373edc7b3b3a282b8b"
+  "gitHead": "2b27a4e70ebdf054b117b87ed9e8f9f709fe006b"
 }

package/prompts/message_handler.txt

@@ -5,7 +5,7 @@
 </providers>
 
 <instructions>
-Write a thought and plan for {{agentName}} and decide what actions to take.
+Write a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.
 
 IMPORTANT ACTION ORDERING RULES:
 - Actions are executed in the ORDER you list them - the order MATTERS!
@@ -26,6 +26,28 @@ IMPORTANT ACTION PARAMETERS:
 - Required parameters MUST be provided; optional parameters can be omitted if not mentioned
 - If you cannot determine a required parameter value, ask the user for clarification in your <text>
 
+EXAMPLE (action parameters):
+User message: "Send a message to @dev_guru on telegram saying Hello!"
+Actions: REPLY,SEND_MESSAGE
+Params:
+<params>
+    <SEND_MESSAGE>
+        <targetType>user</targetType>
+        <source>telegram</source>
+        <target>dev_guru</target>
+        <text>Hello!</text>
+    </SEND_MESSAGE>
+</params>
+
+IMPORTANT PROVIDER SELECTION RULES:
+- Only include providers if they are needed to respond accurately.
+- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see "(Attachments:" in the conversation, you MUST include "ATTACHMENTS" in your providers list
+- If the message asks about or references specific people, include "ENTITIES" in your providers list  
+- If the message asks about relationships or connections between people, include "RELATIONSHIPS" in your providers list
+- If the message asks about facts or specific information, include "FACTS" in your providers list
+- If the message asks about the environment or world context, include "WORLD" in your providers list
+- If no additional context is needed, you may leave the providers list empty.
+
 IMPORTANT CODE BLOCK FORMATTING RULES:
 - If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).
 - ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.
@@ -38,6 +60,7 @@ First, think about what you want to do next and plan your actions. Then, write t
 <keys>
 "thought" should be a short description of what the agent is thinking about and planning.
 "actions" should be a comma-separated list of the actions {{agentName}} plans to take based on the thought, IN THE ORDER THEY SHOULD BE EXECUTED (if none, use IGNORE, if simply responding with text, use REPLY)
+"providers" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use "IGNORE" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)
 "text" should be the text of the next message for {{agentName}} which they will send to the conversation.
 "params" (optional) should contain action parameters when actions require input. Format as nested XML with action name as wrapper.
 </keys>
@@ -50,6 +73,7 @@ Respond using XML format like this:
 <response>
     <thought>Your thought here</thought>
     <actions>ACTION1,ACTION2</actions>
+    <providers>PROVIDER1,PROVIDER2</providers>
     <text>Your response text here</text>
     <params>
         <ACTION1>
@@ -73,3 +97,4 @@ IMPORTANT: Your response must ONLY contain the <response></response> XML block a
 
 
 
+

package/prompts/multi_step_decision.txt

@@ -30,7 +30,6 @@ These are the actions or data provider calls that have already been used in this
 "thought" Clearly explain your reasoning for the selected providers and/or action, and how this step contributes to resolving the user's request.
 "action"  Name of the action to execute after providers return (can be empty if no action is needed).
 "providers" List of provider names to call in this step (can be empty if none are needed).
-"params" Optional XML parameters for the selected action. Use nested XML only when the action needs input.
 "isFinish" Set to true only if the task is fully complete.
 </keys>
 
@@ -41,11 +40,6 @@ These are the actions or data provider calls that have already been used in this
   <thought>Your thought here</thought>
   <action>ACTION</action>
   <providers>PROVIDER1,PROVIDER2</providers>
-  <params>
-    <ACTION>
-      <paramName>value</paramName>
-    </ACTION>
-  </params>
   <isFinish>true | false</isFinish>
 </response>
 </output>
@@ -55,3 +49,4 @@ These are the actions or data provider calls that have already been used in this
 
 
 
+

package/scripts/generate-plugin-action-spec.js

@@ -55,6 +55,7 @@ function ensureDir(dir) {
 
 function listTsFiles(rootDir) {
   const out = [];
+  if (!fs.existsSync(rootDir)) return out;
   const stack = [rootDir];
   while (stack.length > 0) {
     const dir = stack.pop();