creating-claude-skills

Design a Claude Skill by creating YAML frontmatter with name and description, then scaffold a SKILL.md file under 500 lines. Use gerund-based, lowercase, hyphenated names (64-character limit), add concrete examples from your codebase, and organize supporting references in a dedicated directory to ensure consistency and discoverability.

Claude Skill names must be gerund-based (verb+ing), lowercase, hyphenated, and limited to 64 characters. This standardized format ensures discoverability and consistency across your Kompass codebase when automating repeatable workflows.

Use YAML frontmatter to declare the Skill's name and description, then create a SKILL.md file with workflow guidance, concrete examples from your domain, and validation guidelines. Keep documentation under 500 lines and reference supporting templates and validation scripts for clarity.

Yes. Create personal or project-scoped Claude Skills within the Kompass event-sourced Rails codebase to codify domain patterns and repeatable workflows that Claude executes consistently. Scaffold the Skill with frontmatter, SKILL.md structure, examples, and validation guidelines tailored to your use case.

Include concrete examples extracted from your actual codebase to demonstrate the Skill's application, then define validation scripts and guidelines to ensure repeatable, consistent execution. Reference supporting templates and validation files in a dedicated directory alongside your SKILL.md.

Create a new Skill when you have a repeatable workflow or domain pattern that Claude should execute consistently across your Kompass project. Codifying it as a Skill with standardized naming, frontmatter, and documentation enables discoverability and reuse rather than ad-hoc automation.