skill-forge

Create new skills or review and improve existing ones. Use when user says create skill, new skill, improve skill, review skill, audit skills, or skill quality.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "skill-forge" with this command: npx skills add maroffo/claude-forge/maroffo-claude-forge-skill-forge

ABOUTME: Skill creation and improvement based on Anthropic's skills guide

ABOUTME: Validates structure, descriptions, triggers, progressive disclosure, and conventions

Skill Forge

Create new skills or audit/improve existing ones. Encodes Anthropic's official guide + our conventions.

Modes

Create: /skill-forge create <name>

  1. Gather context: ask what the skill does, when to use it, what tools it needs
  2. Generate SKILL.md following the template below
  3. Validate against the checklist
  4. Present for approval before writing

Review: /skill-forge review <name> or /skill-forge review all

  1. Read the skill's SKILL.md
  2. Score against the checklist (0-100)
  3. Report findings grouped by severity (critical, major, minor)
  4. Propose fixes as diffs

Skill Template

---
name: kebab-case-name
description: "[What it does]. Use when [trigger conditions]. [Key capabilities]. Not for [negative triggers if overlapping skills exist]."
compatibility: "Only if external deps needed"
---

# ABOUTME: [One-line what]
# ABOUTME: [One-line key capabilities]

# Skill Title

## Quality Notes (if multi-step workflow)

- Take your time with each step
- Quality over speed
- Do not skip validation

## [Core Instructions]

### Step 1: ...
[Specific, actionable instructions with examples]

### Step 2: ...
[Clear expected output]

## Common Issues

| Issue | Solution |
|-------|----------|

## References (if >150 lines needed)

For detailed patterns, consult `references/<topic>.md`

Validation Checklist

Structure (critical)

CheckRule
Folder namekebab-case, no spaces/capitals/underscores
File nameExactly SKILL.md (case-sensitive)
Frontmatter--- delimiters, name + description required
ABOUTMETwo lines after frontmatter: what + capabilities
No README.mdAll docs in SKILL.md or references/

Description (critical)

CheckRule
Formula[What] + [When/triggers] + [Capabilities]
Trigger phrasesInclude words users actually say
Negative triggers"Not for X" if overlapping skills exist
LengthUnder 1024 characters
No XML tagsNo < or > in description
QuotesWrapped in double quotes

Test: Ask yourself "When would you use the [name] skill?" If the description doesn't answer clearly, it needs work.

Content (major)

CheckRule
SpecificActionable commands, not "validate the data"
ExamplesConcrete code/commands, not abstract descriptions
Error handlingCommon issues table for workflow skills
Progressive disclosureSKILL.md <150 lines core; detailed content in references/
Quality notesMulti-step workflows get anti-laziness section

Optional Fields (minor)

FieldWhen to use
compatibilityExternal deps (app, CLI, API key, MCP server)
allowed-toolsRestrict to specific tools
toolsSimpler tool restriction
metadataDistribution (author, version, mcp-server)

Scoring

Start at 100, subtract per finding:

SeverityDeductionExamples
Critical-25No frontmatter, no description, wrong file name
Major-10No trigger phrases, vague instructions, no ABOUTME
Minor-3Missing compatibility, no error handling, no examples
ScoreVerdict
90+Ship it
70-89Needs fixes
<70Rewrite

Our Conventions (beyond Anthropic's guide)

  • ABOUTME headers: 2-line comment block after frontmatter (what + capabilities)
  • Cross-references: link to _AST_GREP.md, _PATTERNS.md, source-control where relevant
  • _INDEX.md: register new skills in the routing table
  • CLAUDE.md.example: add to skills table if user-invocable
  • Token budget: every word in SKILL.md costs context; be ruthless
  • No em dashes: use commas, colons, semicolons, or parentheses

Quality Notes

  • Read each skill file thoroughly before scoring
  • Compare against existing high-quality skills (rails, source-control, clickup)
  • Propose concrete diffs, not vague suggestions

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

newsletter-digest

No summary provided by upstream source.

Repository SourceNeeds Review
General

rails

No summary provided by upstream source.

Repository SourceNeeds Review
General

react-nextjs

No summary provided by upstream source.

Repository SourceNeeds Review
General

email-cleanup

No summary provided by upstream source.

Repository SourceNeeds Review