agentleFS
tomique34tomique34/claude-skill-creator/CLAUDE.md

claude-skill-creator

CLAUDE.md8 starsChanged 13 months agoMITView on GitHub

This is a Claude Agent Skill for creating and structuring other Claude Agent Skills. It's a meta-skill that helps users understand, create, and validate Claude skills following best practices. The validation script checks: - SKILL.md exists - YAML frontmatter is valid - Name requirements (lowercase, hyphens, <64 chars, no reserved words) - Description requirements (<1024 chars, includes "when to use", no XML tags) - Content structure When helping users create skills: Skills should layer information: - Level 1 (Metadata): Concise…

The file

Show its rules and text

We split this CLAUDE.md into the rules it gives an agent

14 rules. About 0 are common, 10 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All Claude Agent Skills follow this pattern:

    line 12
  2. Distinctive:

    Only lowercase letters, numbers, and hyphens

    line 50
  3. Distinctive:

    Must describe what the skill does AND when to use it

    line 56
  4. Distinctive:

    Should include trigger phrases like "Use when..."

    line 58
  5. Distinctive:

    When helping users create skills:

    line 70
  6. Very specific:

    Create SKILL.md: Use progressive disclosure - overview → quick start → detailed instructions → examples

    line 74
  7. Distinctive:

    Add resources: Only create additional files if truly needed (templates, scripts, comprehensive guides)

    line 75
  8. Very specific:

    Validate: Run validate_skill.py to check structure

    line 76
  9. Distinctive:

    Use for straightforward workflows with clear instructions.

    line 81
  10. Very specific:

    Use when main instructions need supplementary guides (GETTING_STARTED.md, ADVANCED.md, REFERENCE.md).

    line 84
  11. Distinctive:

    Use when skill needs executable utilities (Python, shell scripts).

    line 87
  12. Distinctive:

    Use for complex skills with multiple components and resources.

    line 90
  13. Distinctive:

    When creating skills with multiple files:

    line 101
  14. Very specific:

    Keep references explicit and complete in SKILL.md overview or resources section

    line 104

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “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
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

This is a Claude Agent Skill for creating and structuring other Claude Agent Skills. It's a meta-skill that helps users understand, create, and validate Claude skills following best practices.

Key Architecture

Skill Structure Pattern

All Claude Agent Skills follow this pattern:

  • SKILL.md (required): Contains YAML frontmatter with name and description, plus markdown instructions
  • Optional files: Additional markdown files, scripts, templates referenced in SKILL.md
  • Skills use progressive disclosure: metadata → SKILL.md instructions → additional resources

Directory Layout

claude-skill-creator/
├── SKILL.md              # Main skill instructions (agent-skill-creator)
├── EXAMPLES.md           # Real-world skill examples
├── templates/
│   └── SKILL_TEMPLATE.md # Template for creating new skills
└── scripts/
    └── validate_skill.py # Python validation script

Development Commands

Validation

# Validate a skill structure
python3 claude-skill-creator/scripts/validate_skill.py path/to/skill

# Validate from within the skill directory
python3 scripts/validate_skill.py ../your-skill-directory

The validation script checks:

  • SKILL.md exists
  • YAML frontmatter is valid
  • Name requirements (lowercase, hyphens, <64 chars, no reserved words)
  • Description requirements (<1024 chars, includes "when to use", no XML tags)
  • Content structure

Skill Requirements Reference

Name Constraints

  • Maximum 64 characters
  • Only lowercase letters, numbers, and hyphens
  • No XML tags
  • Cannot contain "anthropic" or "claude"

Description Constraints

  • Maximum 1024 characters
  • Must describe what the skill does AND when to use it
  • No XML tags
  • Should include trigger phrases like "Use when..."

YAML Frontmatter Format

---
name: skill-name
description: What it does and when Claude should use it
---

Creating New Skills

When helping users create skills:

  1. Define requirements: Get skill name, description, and use cases
  2. Choose pattern: Single-file (SKILL.md only) or multi-file (with templates/scripts)
  3. Create SKILL.md: Use progressive disclosure - overview → quick start → detailed instructions → examples
  4. Add resources: Only create additional files if truly needed (templates, scripts, comprehensive guides)
  5. Validate: Run validate_skill.py to check structure

Common Skill Patterns

Pattern 1: Simple (SKILL.md only)

Use for straightforward workflows with clear instructions.

Pattern 2: With Resources (SKILL.md + markdown files)

Use when main instructions need supplementary guides (GETTING_STARTED.md, ADVANCED.md, REFERENCE.md).

Pattern 3: With Scripts (SKILL.md + scripts/)

Use when skill needs executable utilities (Python, shell scripts).

Pattern 4: Comprehensive (SKILL.md + scripts/ + templates/)

Use for complex skills with multiple components and resources.

Progressive Disclosure Principle

Skills should layer information:

  • Level 1 (Metadata): Concise description (~100 tokens) - determines when skill is invoked
  • Level 2 (SKILL.md): Main instructions (~5k tokens) - loaded when skill is used
  • Level 3 (Resources): Detailed guides, scripts, templates - referenced as needed

File References

When creating skills with multiple files:

  • Reference additional files in SKILL.md using relative paths: [EXAMPLES.md](EXAMPLES.md)
  • For subdirectories: [script.py](scripts/script.py)
  • Keep references explicit and complete in SKILL.md overview or resources section

Resources

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.