Agent
Skill8 starsChanged 8 months agoMITView on GitHub
Use when creating, validating, or integrating reusable skill packages for AI agents. Reach for this skill when building domain-specific instructions, packaging workflows, or setting up skill discovery in agent systems.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- nnawar706/fluentotheir own version, first seen Nov 8, 2026
- venom444556/StoryFlowtheir own version, first seen Nov 1, 2026
- aihu-project/aihutheir own version, first seen Oct 20, 2026
- urmzd/saigetheir own version, first seen Oct 9, 2026
- atopile/atopiletheir own version, first seen Oct 8, 2026
- anthonymaley/Kerdtheir own version, first seen Sep 20, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- atopile/atopile★ 4ksame name
- urmzd/saige★ 6same name
- aihu-project/aihu★ 4same name
- gabriellst/codm★ 4same name
- venom444556/StoryFlow★ 4same name
- anthonymaley/Kerd★ 3same name
- SprintsAI/lightsprint-claude-code-plugin★ 2same name
- lyoneel/ly-agent-skills★ 0same name
- nnawar706/fluento★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 5 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 64
Use relative paths from skill root:
- Very specific: line 104
Start with YAML frontmatter: name and description (required)
- Distinctive: line 105
Write the Markdown body with clear instructions
- Distinctive: line 106
Keep the main file under 500 lines
- Very specific: line 107
Use relative paths for file references: scripts/extract.py, references/GUIDE.md
- Very specific: line 120
Test the skill: Read the SKILL.md file to verify instructions are clear and complete
- Distinctive: line 139
Inject into system prompt: Add the XML to your agent's system prompt so it knows available skills:
- Very specific: line 150
Activate on demand: When a user task matches a skill's description, load the full SKILL.md into context (~5000 tokens max)
- Very specific: line 159
Absolute paths in file references: Always use relative paths from skill root (scripts/extract.py), never absolute paths …
- Very specific: line 161
Missing location field for filesystem agents: When injecting skills into filesystem-based agent prompts, include the absolute path to …
- Very specific: line 162
Not validating before deployment: Always run skills-ref validate before sharing or deploying a skill.
- Distinctive: line 167
Before submitting a skill:
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Skills
Product summary
Agent Skills is a lightweight, open format for extending AI agent capabilities with specialized knowledge and workflows. Skills are directories containing a SKILL.md file (YAML frontmatter + Markdown instructions) plus optional supporting files (scripts, references, assets). Use the skills-ref CLI to validate skills and generate prompt XML for agent integration. Primary documentation: https://agentskills.io
When to use
Reach for this skill when:
- Creating a new skill: You need to package domain expertise, repeatable workflows, or new agent capabilities into a reusable format
- Validating skills: You're checking that a skill's SKILL.md file meets format requirements before deployment
- Integrating skills into agents: You're setting up skill discovery, loading metadata, or injecting skills into agent system prompts
- Authoring instructions: You're writing the Markdown body of a skill to guide agent behavior
- Managing skill resources: You're organizing scripts, templates, reference files, or assets alongside skill instructions
Quick reference
SKILL.md frontmatter (required fields)
| Field | Constraints | Example |
name | Max 64 chars, lowercase + hyphens only, no leading/trailing hyphens | pdf-processing |
description | Max 1024 chars, non-empty, describes what skill does and when to use | Extract text and tables from PDFs, fill forms, merge documents. |
SKILL.md optional frontmatter fields
| Field | Purpose | Example |
license | License name or reference to bundled license file | MIT or licenses/LICENSE.txt |
compatibility | Environment requirements (max 500 chars) | Requires Python 3.8+, pdfplumber library |
metadata | Arbitrary key-value pairs for custom properties | author: org-name version: "1.0" |
allowed-tools | Space-delimited pre-approved tools (experimental) | Bash(git:*) Bash(jq:*) |
Directory structure
skill-name/
├── SKILL.md # Required: frontmatter + instructions
├── scripts/ # Optional: executable code
├── references/ # Optional: detailed reference material
└── assets/ # Optional: templates, images, data filesskills-ref CLI commands
# Validate a skill directory
skills-ref validate ./my-skill
# Generate <available_skills> XML for agent prompts
skills-ref to-prompt /path/to/skill1 /path/to/skill2File references in SKILL.md
Use relative paths from skill root:
See [the guide](references/REFERENCE.md) for details.
Run the script: `scripts/extract.py`Decision guidance
When to use filesystem-based vs tool-based agent integration
| Approach | When to use | Activation | Resource access |
| Filesystem-based | Agent has shell/bash environment; maximum capability needed | Agent issues cat /path/to/skill/SKILL.md | Shell commands access bundled files |
| Tool-based | Agent lacks dedicated computer environment; sandboxed execution | Developer implements custom tools | Tools provide access to bundled assets |
When to include optional frontmatter fields
| Field | Include when | Skip if |
license | Skill uses third-party code or has specific licensing | Skill is internal-only or unlicensed |
compatibility | Skill requires specific system packages, Python versions, or network access | Skill is pure Markdown instructions |
metadata | Tracking author, version, or custom properties is important | Not needed for simple skills |
allowed-tools | Restricting which tools the skill can invoke is required | Agent doesn't support tool restrictions |
When to move content to separate files
| Content type | Keep in SKILL.md | Move to separate file |
| Core instructions | < 500 lines | Detailed reference material |
| Quick examples | Yes | Exhaustive API documentation |
| Decision trees | Yes | Large lookup tables or schemas |
| Step-by-step workflows | Yes | Multi-page tutorials |
Workflow
Creating a new skill
- Create the directory structure: Make a folder named
skill-name(lowercase, hyphens only) - Write the SKILL.md file:
- Start with YAML frontmatter:
nameanddescription(required) - Write the Markdown body with clear instructions
- Keep the main file under 500 lines
- Use relative paths for file references:
scripts/extract.py,references/GUIDE.md
- Start with YAML frontmatter:
- Organize supporting files:
scripts/: Executable code (Python, Bash, etc.)references/: Detailed documentation, lookup tables, schemasassets/: Templates, images, data files
- Validate the skill:
Fix any frontmatter errors (name format, description length, etc.)skills-ref validate ./skill-name - Test the skill: Read the SKILL.md file to verify instructions are clear and complete
Integrating skills into an agent
- Discover skills: Scan configured directories for folders containing
SKILL.mdfiles - Load metadata at startup: Parse only the YAML frontmatter from each skill:
This keeps initial context usage low (~100 tokens per skill)name: pdf-processing description: Extract text and tables from PDFs... - Generate prompt XML:
Output includes name, description, and location for each skillskills-ref to-prompt /path/to/skills/* - Inject into system prompt: Add the XML to your agent's system prompt so it knows available skills:
<available_skills> <skill> <name>pdf-processing</name> <description>Extract text and tables from PDFs...</description> <location>/path/to/skills/pdf-processing/SKILL.md</location> </skill> </available_skills> - Activate on demand: When a user task matches a skill's description, load the full SKILL.md into context (~5000 tokens max)
- Execute resources: Load referenced files or run scripts only when the skill instructions require them
Common gotchas
- Name format violations: Names must be lowercase with hyphens only, no leading/trailing hyphens.
my-skill✓,MySkill✗,-my-skill✗ - Description too long: Max 1024 characters. Descriptions longer than this will fail validation. Be concise about what the skill does and when to use it.
- Forgetting YAML delimiters: Frontmatter must start and end with
---on its own line. Missing delimiters break parsing. - Absolute paths in file references: Always use relative paths from skill root (
scripts/extract.py), never absolute paths (/home/user/scripts/extract.py) - Bloated SKILL.md: Keeping the main file under 500 lines is a guideline, not a hard limit, but large files waste context. Move detailed reference material to
references/subdirectory. - Missing location field for filesystem agents: When injecting skills into filesystem-based agent prompts, include the absolute path to SKILL.md. Tool-based agents can omit this.
- Not validating before deployment: Always run
skills-ref validatebefore sharing or deploying a skill. Frontmatter errors are silent until validation. - Unclear "when to use" description: The description field is critical for agent matching. Write it as a clear trigger: "Use when the user needs to extract text from PDFs" not "PDF processing skill".
Verification checklist
Before submitting a skill:
- SKILL.md frontmatter has
name(max 64 chars, lowercase + hyphens) anddescription(max 1024 chars) - Frontmatter is wrapped in
---delimiters on separate lines - All file references use relative paths from skill root (e.g.,
scripts/extract.py) - Main SKILL.md is under 500 lines; detailed material moved to
references/orassets/ - Skill passes validation:
skills-ref validate ./skill-name - Instructions are clear and actionable (imperative voice, step-by-step)
- Optional fields (license, compatibility, metadata) are accurate if included
- Skill description clearly states when an agent should use it (not just what it does)
Resources
- Comprehensive navigation: https://agentskills.io/llms.txt
- Full specification: https://agentskills.io/specification
- Integration guide: https://agentskills.io/integrate-skills
- Example skills: GitHub repository (linked from agentskills.io)
For additional documentation and navigation, see: https://agentskills.io/llms.txt
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

