oh-my-ag iconoh-my-ag

Search Documentation

Search for documentation

Skills

Progressive Disclosure

Skills are selected from request intent. Manual skill selection is usually unnecessary.

Two-Layer Design

Each skill uses a token-optimized two-layer design:

LayerContentSize
SKILL.mdIdentity, routing conditions, core rules~40 lines (~800B)
resources/Execution protocols, examples, checklists, playbooks, snippets, tech stackLoaded on-demand

This achieves ~75% token savings on initial skill loading (3-7KB → ~800B per skill).

Shared Resource Layer (_shared/)

Common resources deduplicated across all skills:

ResourcePurpose
reasoning-templates.mdStructured fill-in-the-blank templates for multi-step reasoning
clarification-protocol.mdWhen to ask vs. assume, ambiguity levels
context-budget.mdToken-efficient file reading strategies per model tier
context-loading.mdTask-type to resource mapping for orchestrator prompt construction
skill-routing.mdKeyword-to-skill mapping and parallel execution rules
difficulty-guide.mdSimple/Medium/Complex assessment with protocol branching
lessons-learned.mdCross-session accumulated domain gotchas
verify.shAutomated verification script run after agent completion
api-contracts/PM creates contracts, backend implements, frontend/mobile consumes
serena-memory-protocol.mdCLI mode memory read/write protocol
common-checklist.mdUniversal code quality checks

Per-Skill Resources

Each skill provides domain-specific resources:

ResourcePurpose
execution-protocol.md4-step chain-of-thought workflow (Analyze → Plan → Implement → Verify)
examples.md2-3 few-shot input/output examples
checklist.mdDomain-specific self-verification checklist
error-playbook.mdFailure recovery with "3 strikes" escalation rule
tech-stack.mdDetailed technology specifications
snippets.mdCopy-paste ready code patterns

Why It Matters

This keeps initial context lean while still supporting deep execution when required.