agno-prompt-system

Writes and adapts Agno agent system prompts per model family with S3-backed prompt storage.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/allankltsn/setup_kiro --skill agno-prompt-system-allankltsn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agno-prompt-system
Source: https://github.com/allankltsn/setup_kiro/tree/main/.kiro/skills/agno-prompt-system
Command: npx skills add https://github.com/allankltsn/setup_kiro --skill agno-prompt-system-allankltsn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3.

What problem does it solve? Writing system prompts that behave consistently across different LLM providers is hard: each model family (GPT, Llama, Claude, Gemini, Grok, Kimi, Bedrock, Ollama) responds better to a different prompt style, and hardcoding prompts in code forces redeploys for every behavior tweak. This Skill provides best practices and per-model adaptation guidelines for Agno agent instructions, plus an S3-backed prompt source with local fallback. ## Core Features & Use Cases - General prompt best practices: structure prompts as persona, atomic rules, context, and explicit output contract, with anti-patterns and abstention rules to reduce hallucination. - Per-model adaptation guidance: concrete style adjustments for OpenAI GPT, Groq/Llama, Anthropic Claude, Google Gemini, xAI Grok, Moonshot Kimi, AWS Bedrock, and local Ollama models, keeping one canonical prompt and changing only form, never intent. - S3 prompt source with fallback: a port-and-adapter pattern that loads the canonical prompt from a versioned S3 bucket (LocalStack in dev) and falls back to a local baseline so the agent never starts without a prompt. - Use Case: When switching an Agno support agent from GPT to Llama via MODEL_PROVIDER_ORDER, apply the recency reinforcement rule (repeat the output format at the end of the prompt) without rewriting the persona, and run the same behavior tests to confirm parity. ## Quick Start Ask the AI to review or rewrite the description and instructions of your Agno agent following this skill's best practices and adapting the style to your target model provider.

Frequently Asked Questions about agno-prompt-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a system prompt for an Agno agent?▼

Separate the prompt into description (persona), instructions (atomic behavior rules), and context (factual data). Make rules specific and positive, define what the agent does when information is missing, and state the output format contract explicitly with one example.

How do I adapt one prompt for GPT, Llama, Claude, and Gemini?▼

Keep one canonical prompt and adjust only the style per family: Llama and Groq respond better to marked sections and format reinforcement at the end, Claude prefers XML tags, and GPT follows natural language with bullets. Never maintain divergent personas per provider.

Can I store agent prompts in S3 instead of hardcoding them?▼

Yes, model the prompt source as a port with an S3 adapter that reads a versioned object using boto3 with a late import. Always provide a local baseline fallback so the agent starts with a valid prompt even when S3 is unavailable.

Does Moonshot Kimi need step-by-step reasoning instructions?▼

No, Kimi reasons by default and produces reasoning_content, so asking it to think step by step is redundant. Control effort via use_thinking or reasoning_effort config, and note that Kimi structured output must be a JSON object, never a root array.

How do I test that prompt changes do not break agent behavior?▼

Treat the prompt as a contract and write at least one behavior test per critical rule, especially the abstention rule. Fix temperature to zero to reduce variance, and rerun the same tests after switching providers to detect where style adjustments are needed.