Menu
PLACEHOLDER — not yet authored, excluded from release. Will migrate a project when its storage layer changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add a new Katalyst check type end-to-end across check execution, config parsing, CLI validation, tests, fixtures, and the generated Hugo check-types reference docs. Use when the user asks to add, extend, or document a new check type in this repository.
Take stock of an existing body of content with katalyst: profile what's there, surface its recurring kinds of item (candidate collections), and get oriented before declaring any structure. Use when a user points at an existing wiki, docs tree, or notes corpus and wants to understand it, "see what's in here", or prepare to onboard it into katalyst. Precedes katalyst-identify-collections.
Define each collection's schema in a katalyst project — the fields its items must have and the constraints they must satisfy — plus the checks that enforce them. Use when a user has collections and wants to declare their structure, add required fields, types, or validation rules. Step 2 of the Define stage; its prerequisite is katalyst-identify-collections.
Gate writes to a katalyst project's content so every change is validated as it happens, rather than only at commit time. Use when a user wants writes checked the moment they occur, an agent workflow where edits must pass checks before they land, or enforcement without a git commit step. Paired with katalyst-deploy (chooses the mechanism) and katalyst-deploy-precommit-hook (the alternative).
Install a git pre-commit hook that runs `katalyst check` (and `katalyst fix --check`) so malformed frontmatter or non-canonical formatting fail the commit instead of landing. Use when a user wants katalyst enforced at commit time, a "pre-commit hook", or to block bad content before it reaches the branch. Paired with katalyst-deploy (chooses the mechanism) and katalyst-deploy-cli-gating (the alternative).
Set up automatic enforcement of a katalyst project once, so its checks run on every change without anyone remembering to invoke them. Knows both mechanisms (a git pre-commit hook and CLI-gated writes), helps choose between them, and routes to the specific setup skill. Use when a user wants katalyst to "run automatically", "enforce on commit", "guard the content", or stop relying on manual `katalyst check` runs.
| name | katalyst-migrate-storage |
| status | placeholder |
| description | PLACEHOLDER — not yet authored, excluded from release. Will migrate a project when its storage layer changes. |
Placeholder reserving the name and intent for the Reshape stage. When a project's storage layer changes (for example, filesystem to a database backend), this skill will guide moving content across.
Not yet authored. Marked status: placeholder in its front matter and excluded
from packaging/release until it carries real content.
