skill-creator

To create a SKILL.md file for a z-schema workflow, you follow a structured process that captures intent, researches existing documentation, and writes concise frontmatter and body content. This ensures the skill aligns with z-schema exports and code conventions.

The best way to document JSON Schema validator workflows is by turning them into portable SKILL.md entries that codify intent and expectations. This approach uses structured frontmatter and references to ground accuracy in z-schema documentation.

Frontmatter works by providing structured metadata at the top of a SKILL.md file, defining the skill's scope and triggers. It pairs with a focused body and an optional references folder to organize detailed material separately.

Yes, you can upgrade existing z-schema skills without starting from scratch. The skill creation workflow supports refining current entries by reviewing and updating their frontmatter, body, and references to ensure ongoing alignment with z-schema options and error codes.

Yes, the skill creation process explicitly aligns with z-schema error codes. It guides builders to ensure their documented workflows match z-schema exports, options, and established code conventions for accurate validation behavior.

You need to use a references folder for skill creation when your SKILL.md body requires supplementary material. It helps organize detailed z-schema documentation separately, keeping the main skill file concise while grounding its accuracy.