agno-project-structure

Defines the standard folder layout and file structure for Agno agent projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When building multiple Agno agents, inconsistent folder layouts and ad-hoc configuration make projects hard to navigate, review, and reuse. This Skill provides a canonical project structure so every agent follows the same predictable organization. ## Core Features & Use Cases - Standard Agent Layout: Defines the directory structure for each agent (pyproject.toml, main.py, config.py, prompts/, tests/) with isolated dependencies managed via uv. - Model Factory Pattern: Provides a reusable config.py that centralizes provider selection (OpenAI, Groq, Ollama) through environment variables, keeping examples model-agnostic. - Prompt Management via S3: Establishes prompts/system_prompt.md as the canonical source, synced to an S3 bucket with local fallback so agents never start without a prompt. - Use Case: When creating a new study agent, apply this Skill to scaffold the folder layout, entry point, README requirements, and configuration files consistently with the rest of the workspace. ## Quick Start Ask the AI to create a new Agno agent following the standard project structure with a main.py entry point, config.py model factory, and prompts folder.

Frequently Asked Questions about agno-project-structure

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

FAQPage Schema
How do I structure an Agno agent project?▼

Use a per-agent folder containing pyproject.toml for isolated dependencies via uv, main.py as the single entry point, config.py for the model factory, a prompts/ directory with system_prompt.md, and a tests/ folder with an optional smoke test.

How do I make Agno agents work with multiple model providers?▼

Centralize provider selection in a config.py model factory that reads the MODEL_PROVIDER environment variable and returns the appropriate client, such as OpenAIChat, Groq, or Ollama. This keeps agent code model-agnostic.

Can Agno agents load system prompts from S3?▼

Yes. The canonical prompt lives in prompts/system_prompt.md and is uploaded to an S3 bucket during bootstrap. At runtime the agent reads from S3 and falls back to the local file if S3 is unavailable, so it never starts without a prompt.

When should I add extra modules to an Agno agent?▼

Add knowledge.py, memory.py, or tools.py only for larger agents that need RAG, storage/memory, or custom tools. Simple agents should stay self-contained with just main.py and config.py to avoid premature abstraction.

What should an Agno agent README contain?▼

Each agent README must include the concept being studied, prerequisites such as API keys or providers, how to run it with uv run python main.py, and what to observe when the example executes.