Workflow stage router

Skill ThanhNguyxnOrg/blendops/skills/workflow-stage-router

Given current artifacts and intent, name the next BlendOps skill or workflow stage and preconditions to advance.From its SKILL.md

Install

npx -y skills add ThanhNguyxnOrg/blendops --skill workflow-stage-router

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, 741 tokens by cl100k_base, as published. Nobody here has run it

workflow-stage-router

Purpose

Reduce skill-choice paralysis by mapping current state → next narrow skill across BlendOps workflows while preserving evidence and runtime boundaries.

Quick start

capture what exists now (brief, plan, renders, GLB, evidence logs)
compare against references/milestone-model.md
emit route via references/routing-decision-tree.md
fill references/stage-handoff-template.md

When to use

user asks "what skill next" after partial progress
agent risks loading too many skills at once
resume after interruption

When not to use

initial goal vague (use blendops-help / blender-brainstorming)
runtime bridge errors (use runtime-bridge-conflict-resolver)
final stakeholder wording (use non-blender-user-response-writer)

Trigger phrases

"where are we in the workflow"
"what's next"
"resume from here"
"next skill"

Prerequisites / readiness

honest inventory of artifacts + truth labels
user goal unchanged or explicitly revised

Input schema

Required inputs

Input	Why it is required
Current artifact inventory	Determines stage
Active intent	Prevents wrong branch

Optional inputs

Input	Use
Target pack/recipe	Narrows milestone track

Output schema

Primary output

current stage name
next skill + why
preconditions checklist for advancing

Evidence / caveat output

Runtime status: Not Run | Attempted | Produced | Verified | Failed | Blocked / Not Run
Artifact status: Not Run | Not Produced | Produced | Verified | Failed
Evidence used: <inventory references>
Limitations: <unknown state>

Required laws

../../laws/evidence-before-done.md
../../laws/non-blender-user-language.md
../../laws/no-arbitrary-python-interface.md
../../laws/official-runtime-only.md

Official runtime boundary

Routing only. If next step is runtime configuration, point to Path 1 / Path 2 / CLI appendix docs — never imply Connector replaces Lab MCP.

Operating procedure

Normalize inventory against milestone model.
Walk decision tree.
If multiple equally valid skills, pick narrowest.
Emit handoff template.

Mode handling

Text-only mode

Assume stated inventory is truthful; flag unverified claims.

Runtime-ready mode

Prefer readiness checker before mutation skills when inventory shows no runtime attempt yet user wants mutation.

Blocked runtime mode

Route to planning/evidence skills only.

Validation checklist

Stage named
Next skill singular primary recommendation
Preconditions listed
Evidence labels preserved

Pass / Warn / Fail rubric

Verdict	Criteria
Pass	Clear next skill + preconditions
Warn	Multiple branches — user must choose priority
Fail	Next skill contradicts evidence state

Cross-skill handoff

Pack entry → ../pack-prerequisite-checker/SKILL.md
Evidence updates → ../render-export-evidence/SKILL.md
Final gate → ../pre-handoff-verification/SKILL.md

References

references/milestone-model.md
references/routing-decision-tree.md
references/stage-handoff-template.md
../../docs/workflows/full-non-blender-user-workflow.md

What ships with it: 4 files

2.8 KB alongside SKILL.md

references/

EVAL.md711 B

Gives 0 of the 12 instructions most automation workflows skills give in 741 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

Write conventional commit messagesin 36 of 745, across 35 files
Delete branches after mergein 30 of 745, across 21 files
Make atomic commitsin 25 of 745, across 15 files
Write minimal code to pass testsin 22 of 745, across 10 files
Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
Use try-catch for error handlingin 20 of 745, across 8 files
Run tests before committingin 20 of 745, across 12 files
Write tests before implementationin 20 of 745, across 8 files
Configure branch protection rulesin 19 of 745, across 5 files
Explain the why in commit messagesin 19 of 745, across 9 files
Refactor code while tests remain greenin 19 of 745, across 6 files
Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

capture what exists now
compare inventory against milestone model
walk the routing decision tree
pick narrowest skill if multiple are valid
fill the stage handoff template
flag unverified claims

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.