Skill Creation Workflow FAQs

Question 1

What is the 'Iron Law' of skill creation?

Accepted Answer

The Iron Law states that no skill should be created or edited without a failing test first. You must watch an AI agent fail to follow a process before writing the skill to ensure the documentation actually solves the problem.

Question 2

Why is token efficiency important for skills?

Accepted Answer

Frequently-referenced skills are loaded into the conversation context. Keeping them concise (under 200 tokens for common skills) saves space for actual coding tasks and reduces costs.

Question 3

What is Claude Search Optimization (CSO)?

Accepted Answer

CSO is a set of techniques to ensure Claude can find your skills. This includes using rich 'when_to_use' descriptions with specific error symptoms, descriptive naming, and keyword coverage.

Question 4

How do you test a Claude Skill?

Accepted Answer

Skills are tested by creating 'pressure scenarios' with subagents. If the agent violates the intended rule without the skill (Red) and follows it with the skill (Green), the documentation is considered effective.

Question 5

When should I create a skill instead of putting it in CLAUDE.md?

Accepted Answer

Create a skill for reusable techniques, patterns, or tools that apply across multiple projects. Use CLAUDE.md only for project-specific conventions and local settings.

Skill Creation Workflow

Key Features

Use Cases

Skill Creation Workflow

Key Features

Use Cases