Skip to content
Back to skills

1845 Frontmatter Guide 8347f543

ASecurity

YAML frontmatter contains `name` and `description` fields. **These are the only fields Claude reads to decide when to use a skill.**

  • 9 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 31, 2026
documentationgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 31, 2026

npx -y skills add tools-only/X-Skills --skill 1845-frontmatter-guide_8347f543 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 1845 Frontmatter Guide 8347f543?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 1845 Frontmatter Guide 8347f543
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-1845-frontmatter-guide-8347f543/badge)](https://www.skillsdirectory.com/skills/tools-only-1845-frontmatter-guide-8347f543)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# 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.

Files in this skill

  • README.md1 KB
  • skill.md2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.