writing-claude-skills

Structure Claude skills using CLAUDE.md files with explicit naming conventions, actionable descriptions, and defined activation triggers. Follow best practices for composability and portability across Claude apps, Claude Code, and API scenarios to ensure discoverability and correct activation.

Write domain-specific descriptions that state the skill's exact function, activation criteria, and use cases. Include examples and templates that clarify scope and expected outputs, enabling users to find and activate skills correctly without ambiguity.

Define skill triggers by specifying the conditions, inputs, or user intents that activate the skill. Document activation patterns explicitly so Claude understands when to invoke the skill across different platforms and scenarios.

Well-named skills use clear, domain-specific terminology that describes the exact task performed. Poorly-named skills use vague terms or internal jargon, reducing discoverability and causing misactivation across Claude apps and APIs.

Yes. Skills designed with portability principles—clear naming, explicit descriptions, and standard CLAUDE.md formatting—transfer across Claude Code, Claude apps, and API scenarios without modification.