Forge

Forge automates the complete skill development lifecycle—initialization, validation, and packaging. Use init_skill.py to generate skill templates with proper frontmatter structure, quick_validate.py to enforce standards before deployment, and package_skill.py to bundle completed skills into distributable .skill files.

Claude skills require SKILL.md frontmatter (name, description, license, allowed-tools, metadata, version, tags), hyphen-case naming, and organized directories for scripts, references, and assets. Forge templates and validation enforce these constraints automatically to ensure consistency and reliability.

Forge guides progressive disclosure design—keeping SKILL.md lean while making detailed information discoverable through scripts and references. This approach ensures skills use context efficiently without losing functionality or accessibility.

Yes. Forge's quick_validate.py catches structural and schema errors before deployment, verifying frontmatter compliance, naming conventions, and content constraints so skills meet official standards and best practices.

Run `scripts/init_skill.py my-new-skill --path skills/public` to scaffold a new skill with proper frontmatter and resource directories. Forge generates all required structure so you can focus on implementation logic.

Forge requires PyYAML to parse and validate skill frontmatter and configuration. It's the only external dependency needed to initialize, validate, and package skills.