YAML frontmatter contains `name` and `description` fields. **These are the only fields Claude reads to decide when to use a skill.**
Scanned 5/31/2026
Install via CLI
openskills install tools-only/X-Skills# SKILL.md Frontmatter Guide
YAML frontmatter contains `name` and `description` fields. **These are the only fields Claude reads to decide when to use a skill.**
## name Field
- **Format**: lowercase + hyphens
- **Length**: 1-64 characters
- **Constraints**:
- Must match directory name
- Reserved words not allowed: "anthropic", "claude"
- No hyphen at start/end
- No consecutive hyphens
- **Examples**: `pdf-editor`, `data-analyst`, `brand-guidelines`
## description Field
- **Length**: 1-1024 characters
- **Composition**: What the Skill does + specific trigger/context
- **Important**: **Include all "when to use" information here** - Do not include in Body. Body is only loaded after trigger
### Good description Example
```yaml
description: |
Comprehensive document creation, editing, and analysis with support for
tracked changes, comments, formatting preservation, and text extraction.
Use when Claude needs to work with professional documents (.docx files) for:
(1) Creating new documents, (2) Modifying or editing content,
(3) Working with tracked changes, (4) Adding comments, or any other document tasks
```
### Description Writing Checklist
- [ ] Explain what the Skill does
- [ ] Include specific trigger conditions
- [ ] List usage scenarios (1, 2, 3...)
- [ ] Mention file formats or specific keywords (e.g., .docx, PDF, BigQuery)
- [ ] Keep under 1024 characters
## Recommended Body Content Structure
```markdown
# {Skill Title}
## Overview
{Brief description}
## Core Concepts
{Concepts that need understanding}
## Usage
### Basic Usage
{Basic patterns}
### Advanced Patterns
{Advanced usage}
## Examples
### Example 1: {Scenario}
{Concrete example}
## Notes
- {Points to note}
```
**Recommended Length**: Keep SKILL.md under 500 lines.
## What NOT to Include
Do not create the following files/content:
- ❌ README.md
- ❌ INSTALLATION_GUIDE.md
- ❌ QUICK_REFERENCE.md
- ❌ CHANGELOG.md
- ❌ Other supplementary documents
Skills should only contain information necessary for the AI agent to perform tasks.
No comments yet. Be the first to comment!
Create Mermaid diagrams for flowcharts, sequences, ERDs, and
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.