agentleFS
tswicegoodtswicegood/claude-skills/CLAUDE.md

claude-skills

CLAUDE.md2 starsChanged 6 months agoApache-2.0View on GitHub

This repository contains custom Claude skills. Skills are reusable prompts that extend Claude's capabilities with specialized workflows and domain expertise. Each skill must have a SKILL.md file at the root of its directory. The file follows this structure: Frontmatter (YAML): Content Sections: 1. Trigger Phrases: When the skill should activate 2. Context Adaptation: How the skill adapts to different project contexts 3. Workflow: Step-by-step execution flow (use Step 1, Step 2, etc.) 4. Output Structure: Detailed format of deliverables 5.…

The file

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

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Trigger Phrases: When the skill should activate

    line 34
  2. Distinctive:

    When creating a new skill:

    line 48
  3. Distinctive:

    Create a directory with a descriptive name (use kebab-case)

    line 50
  4. Very specific:

    Create SKILL.md with proper frontmatter

    line 51
  5. Distinctive:

    Add reference documents only if needed for detailed guidance

    line 54
  6. Distinctive:

    Ensure the description in frontmatter mentions when to use the skill

    line 55
  7. Distinctive:

    Two-phase workflows: When appropriate, confirm details before executing (see book-report Steps 1 & 2)

    line 69

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

Repository Overview

This repository contains custom Claude skills. Skills are reusable prompts that extend Claude's capabilities with specialized workflows and domain expertise.

Repository Structure

claude-skills/
├── {skill-name}/
│   ├── SKILL.md              # Main skill definition with frontmatter metadata
│   └── references/           # Optional: Additional guidance documents
│       └── *.md              # Referenced by the main SKILL.md

Skill Architecture

SKILL.md Structure

Each skill must have a SKILL.md file at the root of its directory. The file follows this structure:

Frontmatter (YAML):

---
name: skill-name
description: Brief description shown in skill selection. Should include trigger phrases.
---

Content Sections:

  1. Trigger Phrases: When the skill should activate
  2. Context Adaptation: How the skill adapts to different project contexts
  3. Workflow: Step-by-step execution flow (use Step 1, Step 2, etc.)
  4. Output Structure: Detailed format of deliverables
  5. Quality Standards: Requirements for thoroughness and quality
  6. Response Format: How to present results to the user
  7. Common Pitfalls: Things to avoid

Reference Documents

Reference documents in references/ provide detailed guidance that would clutter the main SKILL.md. They are explicitly referenced by the main skill file (e.g., "read references/context_adaptation.md for detailed guidance").

Creating New Skills

When creating a new skill:

  1. Create a directory with a descriptive name (use kebab-case)
  2. Create SKILL.md with proper frontmatter
  3. Include clear trigger phrases and context adaptation guidance
  4. Structure workflows with numbered steps
  5. Add reference documents only if needed for detailed guidance
  6. Ensure the description in frontmatter mentions when to use the skill

Example: book-report Skill

The book-report skill demonstrates key patterns:

  • Confirmation step: Verifies book details before proceeding with research
  • Multi-source research: Uses web_search extensively (5+ searches)
  • Context adaptation: Tailors recommendations to professional/personal/academic/hobby contexts
  • Structured deliverables: Creates markdown artifact with 8 standardized sections
  • Reference documents: context_adaptation.md provides detailed adaptation strategies

Key Skill Design Principles

  1. Two-phase workflows: When appropriate, confirm details before executing (see book-report Steps 1 & 2)
  2. Context awareness: Skills should adapt to the user's project context (business vs personal vs academic)
  3. Structured output: Define clear output formats (artifacts, sections, formatting)
  4. Quality standards: Specify research depth, source requirements, and thoroughness expectations
  5. Actionability: Focus on implementable insights, not just information gathering

Git Workflow

This repository uses a simple git workflow:

  • Main branch: main
  • Standard commit and push workflow

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.