Use this skill to design, document, and structure AI agent skills for Gemini, Claude, and Codex. It provides architectural rules, directory standards, and writing best practices.
You are an expert in designing and implementing AI Agent Skills. Your goal is to help users create highly effective, self-contained skills that provide specialized expertise and procedural guidance to LLMs.
Skills should be designed to manage context efficiency using a three-level loading system:
Match the specificity of your instructions to the task's fragility:
Follow this standard directory structure:
skill-name/
├── SKILL.md # Primary entry point (Metadata + Instructions)
├── references/ # (Optional) Static documentation, schemas, or large guides
└── assets/ # (Optional) Code templates, boilerplates, or static files (images, fonts)
references/: Use for knowledge that is only needed sometimes (e.g., api_docs.md, finance_schema.md). Avoid cluttering SKILL.md with static data.assets/: Use for files that are part of the output or product (e.g., logo.png, frontend-template/).Place the skill in the directory corresponding to the target agent:
<project-root>/.gemini/skills/ or ~/.gemini/skills/<project-root>/.claude/skills/ or ~/.claude/skills/<project-root>/.codex/skills/ or ~/.codex/skills/The SKILL.md is the brain of the skill.
Must include:
name: Unique, kebab-case identifier (e.g., go-style-guide).description: Clear, concise text explaining what the skill does and when to trigger it. This is the only part the agent sees before activation.metadata: (Optional) Additional fields like short-description.Pattern 1: High-level guide with references Keep the body lean and link to deep dives.
## Advanced features
- **Form filling**: See [references/FORMS.md](references/FORMS.md)
- **API reference**: See [references/API.md](references/API.md)
Pattern 2: Domain-specific organization If a skill covers multiple distinct areas, separate them to avoid context pollution.
# Analytics Skill
## Domains
- **Sales**: See [references/sales.md](references/sales.md)
- **Marketing**: See [references/marketing.md](references/marketing.md)
Pattern 3: Conditional details Show basics, link to complexity.
## Editing
For simple edits, modify directly.
For **tracked changes**, see [references/REDLINING.md](references/REDLINING.md).
activate_skill("git-expert")).bug-fixer).references/assets/SKILL.md starting with the Frontmatter. Apply "Progressive Disclosure".Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer