develop-agent-skills_skill

This skill helps you create or audit agent skills by guiding modular design, concise context, and referenced resources.
  • Shell

7

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill gwenwindflower/.charmschool --skill develop-agent-skills

  • overview.md34.1 KB
  • SKILL.md3.9 KB

Overview

This skill guides creators through designing, building, and improving Agent Skills: compact, reusable packages that extend an AI agent with workflows, code, references, and assets. It focuses on minimizing context bloat, choosing appropriate degrees of freedom, and organizing files so the agent loads only what it needs. Use it to create new skills or audit and improve existing ones.

How this skill works

The guide inspects skill structure, metadata, and resource choices and prescribes a progressive-disclosure layout: minimal frontmatter, concise SKILL.md body, and optional bundled scripts/references/assets loaded only when needed. It walks through a stepwise creation process—understand usage examples, plan reusable contents, initialize scaffolding, validate structure, and iterate against best practices. It also recommends when to move content out of SKILL.md into reference files or scripts for token efficiency and determinism.

When to use it

  • Creating a new Agent Skill from scratch
  • Auditing an existing skill for context efficiency and correctness
  • Designing what scripts, references, or assets to bundle
  • Converting verbose documentation into concise SKILL.md + references
  • Preparing a skill for reliable, repeatable execution

Best practices

  • Keep SKILL.md concise; frontmatter must include clear name and description
  • Prefer scripts for repeated deterministic code and assets for output files
  • Use references/ for domain docs; link them from SKILL.md with clear relative links
  • Apply progressive disclosure: metadata always loaded, body only when triggered, resources on demand
  • When unsure, restrict degrees of freedom—start strict and relax later

Example use cases

  • Create a pdf-editor skill with scripts/rotate_pdf.py and references for advanced features
  • Audit a bigquery-skill and move large schemas to references/schema.md with a TOC
  • Design a frontend-template skill that stores boilerplate in assets/ and minimal usage notes in SKILL.md
  • Improve an image-editing skill by replacing verbose procedural text with compact triggers and targeted reference files
  • Validate skill structure with skillutil and iterate based on agent feedback

FAQ

Keep only essential workflow instructions and selection guidance in SKILL.md. Move large examples, schemas, API docs, and extended patterns into references/ and link to them from SKILL.md.

When should I include scripts/ instead of inline code examples?

Include executable scripts when you repeatedly rewrite the same code or need deterministic reliability. Scripts save tokens and can be executed without loading into context.

How do I avoid loading irrelevant content into the agent context?

Use short frontmatter, concise SKILL.md, and organize variant-specific or domain-specific material into separate reference files so the agent reads only the relevant file when triggered.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational