skill-creator

Run node init-skill.mjs <skill-name> to scaffold a directory containing a SKILL.md template, an example script, a reference file, and an assets folder. Then edit the SKILL.md frontmatter with a specific name and description, and document the workflow steps.

Run node validate-skill.mjs <skill-directory> to check that SKILL.md exists, the YAML frontmatter contains name and description, the name is hyphen-case, and descriptions avoid YAML-breaking characters. It prints 'Skill is valid!' on success.

A good description states the specific action, output, and trigger phrases users might say, such as the file formats or tasks involved. Wrap the value in double quotes so YAML parsers in other tools do not break on colons.

Use scripts when the same code is rewritten repeatedly or deterministic reliability is needed, such as rendering large templates or validating output formats. Scripts execute without entering the model context, saving tokens.

Yes, create an extension skill that references the original using a skill: link and documents only your additions, such as company branding or output locations. This keeps base skill updates flowing through while preserving your customizations.