skill-name

To standardize skill creation, use a script-first philosophy with a structured directory layout containing a skill.md file, a scripts/ directory with executable Bash or Python files, and YAML frontmatter for name and description to ensure consistency across teams.

The best way to structure a skill unit is by organizing files into a clear directory structure with skill.md, a scripts/ directory for executable main.sh or main.py files, and a templates/ directory to promote reliable validation and reuse across projects.

YAML frontmatter enforces consistency in skill authoring by requiring essential metadata fields like name and description at the top of the skill.md file, ensuring all skill units follow a standardized format before executable scripts are run.

You should use Bash or Python for executable scripts in a skill unit because the script-first philosophy emphasizes using standalone .sh or .py files over inline code to maintain executability and maintainability.

Yes, you can add optional references and assets to a skill unit to provide extended context, supplementing the core executable scripts and frontmatter conventions without breaking the standardized layout.

Skill authoring recommends templates and a scripts directory over inline code to enable reliable reuse and validation across projects, ensuring that executable workflows remain maintainable and consistently structured across teams.