Home Gallery AISPA Paper GitHub Follow

dexto system prompt

Category: Multi-agent systems. Audited against the AISPA standard.

1 Prompts on record
0 Flagged instructions
AI audit Audit source
D1 · Identity Transparency D2 · Truthfulness & Information Integrity D3 · Privacy & Data Protection D4 · Tool/Action Safety D5 · User Agency & Manipulation Prevention D6 · Unsafe Request Handling D7 · Harm Prevention & User Safety D8 · Fairness, Inclusion & Neutrality

dexto - docs docs guides configuring dexto systemPrompt

5350 characters

--- sidebar_position: 3 sidebar_label: "System Prompt" --- # System Prompt Configuration Configure how your Dexto agent behaves and responds through system prompts that define personality, capabilities, and guidelines. :::tip Complete Reference For complete field documentation and all configuration options, see **[agent.yml → System Prompt](./agent-yml.md#system-prompt-configuration)**. ::: ## Overview System prompts define your agent's personality, behavior, and capabilities. They serve as the foundational instructions that guide how your agent interprets and responds to user requests. You can use either a simple string for basic scenarios or an advanced multi-contributor system for complex agents that need dynamic context, file-based instructions, or memory integration. **Key capabilities:** - Static instructions for consistent behavior - Dynamic context (date/time, MCP resources) - File-based documentation inclusion - Priority-based content ordering :::tip Memory Configuration For user memory integration, use the top-level [`memories`](./agent-yml.md#memories) configuration instead of system prompt contributors. ::: ## Configuration Types ### Simple String Prompt For straightforward agents, use a single string: ```yaml systemPrompt: | You are a helpful AI assistant with access to tools. Use these tools when appropriate to answer user queries. After each tool result, determine if you need more information or can provide a final answer. ``` ### Advanced Multi-Contributor System For complex scenarios requiring multiple content sources: ```yaml systemPrompt: contributors: - id: core-behavior type: static priority: 1 content: | You are a professional software development assistant. You help with coding, documentation, and project management. - id: current-time type: dynamic priority: 10 source: date - id: project-docs type: file priority: 20 files: - "${{dexto.agent_dir}}/README.md" - "${{dexto.agent_dir}}/CONTRIBUTING.md" options: includeFilenames: true errorHandling: "skip" # Memory is configured separately at the top level memories: enabled: true limit: 10 ``` ## Contributor Types ### Static Contributors Fixed text content for consistent instructions. ```yaml - id: guidelines type: static priority: 1 content: | Always be helpful, respectful, and thorough. Provide step-by-step solutions when possible. ``` ### Dynamic Contributors Runtime-generated content: - **`date`** - Current date context - **`resources`** - MCP server resources (disabled by default) ```yaml - id: timestamp type: dynamic priority: 10 source: date enabled: true ``` ### File Contributors Include external documentation files (`.md` and `.txt` only): ```yaml - id: project-context type: file priority: 20 files: - "${{dexto.agent_dir}}/docs/guidelines.md" - "../README.md" options: includeFilenames: true separator: "\n\n---\n\n" maxFileSize: 50000 ``` **Path resolution:** Relative paths are resolved from the config file location. ## Priority Ordering Contributors execute in ascending priority order (1 → 100+). Lower numbers appear first in the final system prompt. **Recommended ranges:** - **1-10:** Core behavior and role definition - **10-50:** Dynamic context (time, resources) - **50-100:** File-based documentation - **100+:** Additional context and overrides ## Use Cases | Scenario | Recommended Approach | |----------|---------------------| | Simple chatbot | Single string prompt | | Development assistant | Static + File contributors for guidelines | | Customer support | Static + top-level `memories` config | | Research agent | Static + Dynamic (resources) for live data | | Personal assistant | Static + File + Dynamic + `memories` config | ## Examples ### Production Agent ```yaml systemPrompt: contributors: - id: core type: static priority: 1 content: | You are a helpful AI assistant designed to work with tools and data. Provide clear, accurate responses and use available tools effectively. - id: timestamp type: dynamic priority: 10 source: date ``` ### Customer Support Agent ```yaml systemPrompt: contributors: - id: role type: static priority: 1 content: | You are a customer support assistant. Always be polite, professional, and solution-oriented. memories: enabled: true limit: 10 ``` ## Best Practices 1. **Keep it focused** - Clear, specific instructions work better than lengthy prompts 2. **Use priority ordering** - Structure from general (role) to specific (context) 3. **Test behavior** - Validate that prompts produce desired agent responses 4. **File contributors for docs** - Keep large documentation in separate files 5. **Enable resources selectively** - MCP resources can be large; only enable when needed 6. **Use top-level memories** - Configure memory retrieval via the `memories` config field ## See Also - [agent.yml Reference → System Prompt](./agent-yml.md#system-prompt-configuration) - Complete field documentation - [Memory Configuration](./memory.md) - Configure the memory system - [MCP Configuration](./mcpConfiguration.md) - Set up resource providers

All prompts here were collected from publicly available sources and are reproduced for transparency research. Browse the multi-agent systems category, the full gallery of 400+ products, or read the paper behind the AISPA standard.