Home / Skill paths
PUBLISHED PATHS
Skill combinations with every evidence boundary attached
A path is more than a list of tools. Each stage states its input, output, handoff, verification level, known failure, and the next test required before the path can be called workflow-verified.
Current coverage: these first paths are evidence-backed
candidates. None is labeled workflow-verified yet. That distinction is the point of this page.
PARTIAL EVIDENCELanding page → visual QAUse hallmark for judgment, kill-ai-slop for mechanical recall, and visual-skills for a model-specific social-card brief.PARTIAL EVIDENCEScreenshots → promo videoUse video-shotcraft for shot direction and the official Remotion skills for implementation discipline, then verify the rendered file.NEEDS RETESTNotes → Obsidian vaultUse the Obsidian skills pack to define Markdown, Bases, Canvas, and CLI-compatible structures, then verify links and classification on a real desktop vault.
How a path earns “workflow verified”
- Freeze one Outcome Contract and one input pack.
- Run every required stage and preserve each handoff.
- Produce the final artifact and pass its mechanical verifier.
- Repeat the complete workflow, retaining failures.
- Publish the result, environment, pinned commits, and reproduction pack.