Skill Granularity Convention FAQs

Question 1

What is the Skill Granularity Convention for Claude Code?

Accepted Answer

It is a set of standards designed to ensure that Claude Code skills are modular and maintainable. It establishes the 'One Skill, One Purpose' principle, providing specific metrics for when to split complex skills or merge overly narrow ones.

Question 2

What are the signs that a skill should be split into multiple parts?

Accepted Answer

A skill should be split if it covers more than one purpose, has more than six responsibility items, requires more than five workflow phases, or has a description longer than one concise sentence.

Question 3

How does this skill improve my Claude Code workflow?

Accepted Answer

By maintaining proper granularity, you reduce context window bloat, increase the reusability of your skills across different projects, and make it easier for Claude to execute tasks without confusion from overlapping responsibilities.

Question 4

What metrics are used to judge skill design quality?

Accepted Answer

The convention suggests keeping descriptions under 50 characters, limiting responsibilities to 3-5 items, maintaining 2-5 workflow phases, and keeping the document size between 200 and 400 lines for optimal performance.

Question 5

When should I consider merging two or more skills?

Accepted Answer

You should merge skills if they are too small to be practical on their own (1-2 responsibility items), have strong dependencies where one cannot function without the other, or contain significant duplicate guidelines.

Skill Granularity Convention

Skill Granularity Convention

Key Features

Use Cases

Key Features

Use Cases