create-skill-file-EN_skill

Overview

This skill guides Claude in creating well-structured skill files that are easy to discover, trigger, and execute. It provides concrete naming rules, frontmatter conventions, and content organization patterns to ensure consistency and reliability. The goal is concise, actionable guidance that reduces activation errors and maintenance overhead.

How this skill works

The skill inspects a skill directory and its frontmatter for required fields, validates naming and description formats, and checks section structure and example coverage. It suggests a layered content layout, appropriate freedom levels for tasks, and when to split into subfiles or add scripts. It also offers checklist items for functional completeness and testing.

When to use it

• Authoring a new skill file to ensure it follows naming and description standards
• Refining an existing skill to improve triggerability and discoverability
• Preparing a skill for automation or script integration
• Auditing a skill for missing examples, error handling, or validation steps
• Deciding when to split large documentation into reference and examples

Best practices

• Use a lowercase hyphenated name that matches the directory and stays ≤64 characters
• Write a concise plain-text description (1–2 sentences) that includes trigger keywords and scenarios
• Keep content focused: include only project-specific knowledge Claude wouldn’t already know
• Organize content progressively: main document for overview, separate reference/examples/scripts when needed
• Provide clear workflows, conditional branches, and input/output examples with expected results
• Include scripts with usage, parameter validation, error handling, and explicit success/failure return codes

Example use cases

• Create a skill file that converts CSV to Excel with charts and specifies trigger phrases
• Document a type-check workflow that runs mypy with project-specific configurations
• Add a pre-deployment checklist with commands, stop-on-failure rules, and success criteria
• Provide a reusable script to run audits with usage docs and return codes
• Split a 600-line skill into a concise main file plus reference and examples subfiles