Skill Creation TDD FAQs

Question 1

What does it mean to apply TDD to skill writing?

Accepted Answer

It means writing a pressure scenario for Claude, watching it fail to perform correctly (RED), writing the skill documentation, watching the agent pass the scenario (GREEN), and then refining the documentation for token efficiency (REFACTOR).

Question 2

How do I optimize a skill for token efficiency?

Accepted Answer

Aim for under 200 words for frequently-loaded skills, move heavy API references to separate files, and use cross-references instead of repeating common instructions.

Question 3

Why should the description avoid summarizing the skill's workflow?

Accepted Answer

If the description summarizes the process, Claude may follow the brief summary instead of reading the full skill, leading to missed steps and inconsistent behavior.

Question 4

When is it appropriate to create a new skill versus a CLAUDE.md entry?

Accepted Answer

Skills should be created for reusable techniques, patterns, or tools that apply broadly across projects. Project-specific conventions belong in CLAUDE.md.

Question 5

What is the best naming convention for new skills?

Accepted Answer

Use active, verb-first names or gerunds, such as 'creating-skills' or 'debugging-with-logs', to clearly describe the action being performed.

Skill Creation TDD

主な機能

ユースケース

Skill Creation TDD

主な機能

ユースケース