This guide covers how to create high-quality Agent Skills for the skild ecosystem.
# Create a new Skill
skild init my-skill
cd my-skill
# Validate structure
skild validate .
# Test locally
skild install ./my-skill --localA minimal Skill requires a SKILL.md file:
my-skill/
├── SKILL.md # Required: Main skill definition
├── assets/ # Optional: Images, diagrams
├── references/ # Optional: Additional context files
└── scripts/ # Optional: Executable scripts
---
name: my-skill
description: What this skill does
version: 0.1.0
---
# My Skill
Instructions for the AI agent on how to use this skill.
## When to Use
Describe the scenarios where this skill should be activated.
## How to Use
Step-by-step instructions or examples.
## Examples
\`\`\`
Example input/output pairs or usage patterns.
\`\`\`| Field | Required | Description |
|---|---|---|
name |
Yes | Skill identifier (lowercase, hyphens) |
description |
Yes | One-line description |
version |
Yes | Semver version (e.g., 1.0.0) |
author |
No | Author name or handle |
license |
No | License identifier (e.g., MIT) |
tags |
No | Array of tags for discovery |
Tell the agent exactly when to use this skill:
## When to Use
Use this skill when:
- Processing PDF documents
- Extracting text from uploaded PDFs
- Generating PDF reportsBreak down complex skills into clear sections:
- Prerequisites — What the agent needs before starting
- Steps — Numbered, actionable instructions
- Edge Cases — How to handle errors or unusual inputs
- Examples — Concrete input/output pairs
For complex skills, add supporting files:
references/
├── api-spec.md # API documentation
├── examples.json # Example data
└── troubleshooting.md
Reference them in SKILL.md:
See [API specification](./references/api-spec.md) for endpoint details.Before publishing:
- Install locally:
skild install ./my-skill --local - Test with your target agent (Claude, Codex, Copilot)
- Validate:
skild validate ./my-skill
When your Skill is ready, publish it to share with the community:
skild publishSee Publishing Skills for the complete guide.
Use Semantic Versioning:
1.0.0→ Initial release1.0.1→ Bug fixes1.1.0→ New features (backward compatible)2.0.0→ Breaking changes
Update the version field in SKILL.md before each publish.