skill forge

Design Community

Skill notes

What is a Skill

A skill is an "onboarding guide" for Claude — transforming it from a general-purpose agent into a specialized one with procedural knowledge, domain expertise, and bundled tools. Default assumption: Claude is already very smart. Only add what Claude doesn't already know. Challenge every paragraph: "Does this justify its token cost?"

Workflow

Copy this checklist and check off items as you complete them:

Step 1: Understand the Skill ⚠️ REQUIRED

Ask yourself: What specific problem does this skill solve that Claude can't do well on its own? What would a user literally type to trigger this skill? What are 3-5 concrete usage examples with realistic inputs and expected outputs? If unclear, ask the user (don't ask everything at once — start with the most critical):

Step 2: Plan Architecture

For each concrete example, ask: What operations are deterministic and repeatable? → scripts/ What domain knowledge does Claude need at specific steps? → references/ What files are used in output but not in reasoning? → assets/ Key constraints:

Step 3: Initialize ⛔ BLOCKING

Skip if working on an existing skill. Otherwise run: The script creates a template with Iron Law placeholder, workflow checklist, and proper directory structure.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@sanyuan0704 · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Understand the Skill ⚠️ REQUIRED

Ask yourself: What specific problem does this skill solve that Claude can't do well on its own? What would a user literally type to trigger this skill? What are 3-5 concrete usage examples with realistic inputs and expected outputs? If unclear, ask the user (don't ask everything at once — start with the most critical):

02
Step 2: Plan Architecture

For each concrete example, ask: What operations are deterministic and repeatable? → `scripts/` What domain knowledge does Claude need at specific steps? → `references/` What files are used in output but not in reasoning? → `assets/` Key constraints:

03
Step 3: Initialize ⛔ BLOCKING

Skip if working on an existing skill. Otherwise run: The script creates a template with Iron Law placeholder, workflow checklist, and proper directory structure.

04
Step 4: Write Description

This is the most underestimated part of a skill. The description determines: Whether the skill triggers automatically Whether users find it by search Load references/description-guide.md for the keyword bombing technique and good/bad examples. Key rule: NEVER put "When to Use" info in the SKILL.md body. The body loads AFTER triggering — too late.

05
Step 5: Write SKILL.md Body

Load reference files as needed for each sub-step:

06
Step 6: Build Resources

Step 6: Build Resources

07
Step 7: Review ⚠️ REQUIRED

Present the skill summary to the user and confirm before packaging.

08
Step 8: Package

Validates automatically before packaging. Fix errors and re-run.

09
Step 9: Iterate

After real usage: Notice where the model struggles or is inconsistent Identify which workflow step needs improvement Add more specific instructions, examples, or anti-patterns Re-test and re-package

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.