create-agent-skill skill

Overview

This skill helps you create or edit Claude Code skills with expert guidance on structure, TypeScript patterns, and compound engineering best practices. It streamlines producing well-organized, maintainable skill code and offers concrete recommendations for intents, handlers, and tests. Use it to accelerate development and reduce structural errors when building Claude Code skills.

How this skill works

The skill inspects provided arguments describing the intended skill behavior, inputs, and outputs, then generates or updates TypeScript skill scaffolding, metadata, and example handlers. It validates structure against common compound engineering patterns, suggests naming conventions, and includes notes on types, error handling, and test hooks. Optionally it can propose CI/test workflow snippets and sample usage docs.

When to use it

• Starting a new Claude Code skill and needing a standard TypeScript scaffolding.
• Refactoring an existing skill to follow compound engineering patterns.
• Adding new intents, handlers, or type definitions to a skill.
• Preparing a skill for review or integration with a larger agent system.
• Generating example tests and CI steps for consistent quality assurance.

Best practices

• Keep each intent focused and map inputs to explicit TypeScript types for safety.
• Design small, composable handlers that can be composed into higher-level flows.
• Use clear metadata and versioning to track changes and compatibility.
• Include unit tests for handlers and integration tests for end-to-end behavior.
• Document expected inputs, outputs, and error cases in concise examples.

Example use cases

• Create a new TypeScript skill skeleton with intents, handlers, and type definitions.
• Extend a skill by adding a new handler and associated unit tests.
• Audit a skill for structural issues and receive a prioritized refactor plan.
• Produce CI workflow snippets that run tests and linting for the skill.
• Generate usage examples and minimal docs for integrators and reviewers.

FAQ