agentleFS
kstonekuankstonekuan/webskills/.agents/skills/agent/SKILL.md

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

  • Other versions9 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 9

    1. atopile/atopile★ 4ksame name
    2. urmzd/saige★ 6same name
    3. aihu-project/aihu★ 4same name
    4. gabriellst/codm★ 4same name
    5. venom444556/StoryFlow★ 4same name
    6. anthonymaley/Kerd★ 3same name
    7. SprintsAI/lightsprint-claude-code-plugin★ 2same name
    8. lyoneel/ly-agent-skills★ 0same name
    9. 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.

  • In this repository2 other files it gives its agents.

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
  1. Distinctive:

    Use relative paths from skill root:

    line 64
  2. Very specific:

    Start with YAML frontmatter: name and description (required)

    line 104
  3. Distinctive:

    Write the Markdown body with clear instructions

    line 105
  4. Distinctive:

    Keep the main file under 500 lines

    line 106
  5. Very specific:

    Use relative paths for file references: scripts/extract.py, references/GUIDE.md

    line 107
  6. Very specific:

    Test the skill: Read the SKILL.md file to verify instructions are clear and complete

    line 120
  7. Distinctive:

    Inject into system prompt: Add the XML to your agent's system prompt so it knows available skills:

    line 139
  8. Very specific:

    Activate on demand: When a user task matches a skill's description, load the full SKILL.md into context (~5000 tokens max)

    line 150
  9. Very specific:

    Absolute paths in file references: Always use relative paths from skill root (scripts/extract.py), never absolute paths …

    line 159
  10. Very specific:

    Missing location field for filesystem agents: When injecting skills into filesystem-based agent prompts, include the absolute path to …

    line 161
  11. Very specific:

    Not validating before deployment: Always run skills-ref validate before sharing or deploying a skill.

    line 162
  12. Distinctive:

    Before submitting a skill:

    line 167

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

FieldConstraintsExample
nameMax 64 chars, lowercase + hyphens only, no leading/trailing hyphenspdf-processing
descriptionMax 1024 chars, non-empty, describes what skill does and when to useExtract text and tables from PDFs, fill forms, merge documents.

SKILL.md optional frontmatter fields

FieldPurposeExample
licenseLicense name or reference to bundled license fileMIT or licenses/LICENSE.txt
compatibilityEnvironment requirements (max 500 chars)Requires Python 3.8+, pdfplumber library
metadataArbitrary key-value pairs for custom propertiesauthor: org-name version: "1.0"
allowed-toolsSpace-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 files

skills-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/skill2

File 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

ApproachWhen to useActivationResource access
Filesystem-basedAgent has shell/bash environment; maximum capability neededAgent issues cat /path/to/skill/SKILL.mdShell commands access bundled files
Tool-basedAgent lacks dedicated computer environment; sandboxed executionDeveloper implements custom toolsTools provide access to bundled assets

When to include optional frontmatter fields

FieldInclude whenSkip if
licenseSkill uses third-party code or has specific licensingSkill is internal-only or unlicensed
compatibilitySkill requires specific system packages, Python versions, or network accessSkill is pure Markdown instructions
metadataTracking author, version, or custom properties is importantNot needed for simple skills
allowed-toolsRestricting which tools the skill can invoke is requiredAgent doesn't support tool restrictions

When to move content to separate files

Content typeKeep in SKILL.mdMove to separate file
Core instructions< 500 linesDetailed reference material
Quick examplesYesExhaustive API documentation
Decision treesYesLarge lookup tables or schemas
Step-by-step workflowsYesMulti-page tutorials

Workflow

Creating a new skill

  1. Create the directory structure: Make a folder named skill-name (lowercase, hyphens only)
  2. Write the SKILL.md file:
    • Start with YAML frontmatter: name and description (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
  3. Organize supporting files:
    • scripts/: Executable code (Python, Bash, etc.)
    • references/: Detailed documentation, lookup tables, schemas
    • assets/: Templates, images, data files
  4. Validate the skill:
    skills-ref validate ./skill-name
    Fix any frontmatter errors (name format, description length, etc.)
  5. Test the skill: Read the SKILL.md file to verify instructions are clear and complete

Integrating skills into an agent

  1. Discover skills: Scan configured directories for folders containing SKILL.md files
  2. Load metadata at startup: Parse only the YAML frontmatter from each skill:
    name: pdf-processing
    description: Extract text and tables from PDFs...
    This keeps initial context usage low (~100 tokens per skill)
  3. Generate prompt XML:
    skills-ref to-prompt /path/to/skills/*
    Output includes name, description, and location for each skill
  4. 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>
  5. Activate on demand: When a user task matches a skill's description, load the full SKILL.md into context (~5000 tokens max)
  6. 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 validate before 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) and description (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/ or assets/
  • 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


For additional documentation and navigation, see: https://agentskills.io/llms.txt

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.