plano-agent-skills
katanemo/archgw/skills/plano-agent-skills/SKILL.md
Best practices for building agents and agentic applications with Plano, including configuration, routing, orchestration, guardrails, observability, and deployment.
Skill7.1k starsChanged 7 months ago
What's in it
- Plano Agent Skills
- When To Use
- How To Use
- Operating Workflow
- Response Style
- References
--- name: plano-agent-skills description: Best practices for building agents and agentic applications with Plano, including configuration, routing, orchestration, guardrails, observability, and deployment. license: Apache-2.0 metadata: author: katanemo version: "1.0.0" --- # Plano Agent Skills Comprehensive Plano guidance for coding agents. Use this umbrella skill when a task spans multiple areas (config, routing, orchestration, filters, observability, CLI, deployment). ## When To Use - Validating or fixing Plano `config.yaml` - Designing listener architecture (`model`, `prompt`, `agent`) - Improving model/provider routing quality and fallback behavior - Hardening filter chains and prompt guardrails - Debugging routing with traces and CLI workflows - Preparing deployment and production readiness checks ## How To Use 1. Classify the request by scope (single section vs. cross-cutting). 2. For focused work, prefer a section-specific skill (for example `plano-routing-model-selection`). 3. For broad work, apply this umbrella skill and reference section rules from `skills/AGENTS.md`. 4. Produce concrete edits first, then concise reasoning and validation steps. ## Operating Workflow 1. Identify the task area first: config, routing, orchestration, filters, observability, CLI, or deployment. 2. Apply the smallest correct change that satisfies the requested behavior. 3. Preserve security and reliability defaults: - `version: v0.3.0` - exactly one `default: true` model provider - secrets via `$ENV_VAR` substitution only - `host.docker.internal` for host services from inside Docker - guardrails before enrichment in filter chains 4. For debugging, prioritize traces over guesswork (`planoai up --with-tracing`, `planoai trace`). 5. Return concrete diffs and a short validation checklist. ## Response Style - Prefer actionable edits over generic advice. - Be explicit about why a config choice is correct. - Call out risky patterns (hardcoded secrets, missing default provider, bad filter ordering). - Keep examples minimal and production-viable. ## References - Repo: https://github.com/katanemo/plano - Full rulebook: `skills/AGENTS.md`
More agent context in katanemo/archgw
18 other files this repository gives its agents.
AGENTS.md
CLAUDE.md
Skill
- build-brightstaff.claude/skills/build-brightstaff/SKILL.md
- build-cli.claude/skills/build-cli/SKILL.md
- build-wasm.claude/skills/build-wasm/SKILL.md
- check.claude/skills/check/SKILL.md
- new-provider.claude/skills/new-provider/SKILL.md
- pr.claude/skills/pr/SKILL.md
- release.claude/skills/release/SKILL.md
- test-python.claude/skills/test-python/SKILL.md
- plano-advanced-patternsskills/plano-advanced-patterns/SKILL.md
- plano-agent-orchestrationskills/plano-agent-orchestration/SKILL.md
- plano-cli-operationsskills/plano-cli-operations/SKILL.md
- plano-config-fundamentalsskills/plano-config-fundamentals/SKILL.md
- plano-deployment-securityskills/plano-deployment-security/SKILL.md
- plano-filter-guardrailsskills/plano-filter-guardrails/SKILL.md
- plano-observability-debuggingskills/plano-observability-debugging/SKILL.md
- plano-routing-model-selectionskills/plano-routing-model-selection/SKILL.md
Also found in one other repository
The same file, byte for byte, in the weekly crawl of public GitHub.
- katanemo/plano7.1k
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Posts are public. Sign in to say whether it worked for you.Sign in to post
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.

