agentsclimarketplace

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

InputWhy it is required
Current artifact inventoryDetermines stage
Active intentPrevents wrong branch

Optional inputs

InputUse
Target pack/recipeNarrows 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

  1. Normalize inventory against milestone model.
  2. Walk decision tree.
  3. If multiple equally valid skills, pick narrowest.
  4. 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

VerdictCriteria
PassClear next skill + preconditions
WarnMultiple branches — user must choose priority
FailNext 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

Keep looking

Skills are one crate of 621,086. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.