Reads STATE.md and recommends the next skill in the tableau-dashboard-plugin workflow. Use when asking "what's next" or "which skill do I run now".
How this skill is triggered — by the user, by Claude, or both
Slash command
/tableau-dashboard-plugin:tableau-routeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
A thin router over the file-based workflow contract. It reads `STATE.md` in the
A thin router over the file-based workflow contract. It reads STATE.md in the
analyst's project and tells them which one skill to run next — nothing more.
This skill is a router only. It NEVER invokes another skill inline. Running the next skill here would share this conversation's context and defeat the entire point of the plugin (each skill must run in its own fresh conversation). Your job ends at recommending the next skill and telling the analyst to run it themselves.
Determine the analyst's project directory (the directory that contains, or
should contain, STATE.md). Default to the current working directory.
Run the router script and capture its output:
python "${CLAUDE_SKILL_DIR}/scripts/route.py" "<project-dir>"
(Use python3 if python is unavailable.) The script reads STATE.md,
applies the ordering rule from CONTRACT.md, and prints the recommended next
skill plus a one-line reason. It is pure and read-only — it does not modify
any files.
Relay the script's recommendation to the analyst, then stop. Tell them to
open a fresh conversation and invoke the recommended skill themselves (e.g.
"Run tableau-data next"). Do not call the recommended skill yourself.
The script reports one of four situations:
STATE.md) → recommends tableau-init to scaffold the
project.pending or stale, with its required inputs satisfied).approved or skipped; point the analyst at their
deliverables under mock-version/v_N/.If STATE.md looks malformed or the recommendation is surprising, show the
analyst the relevant part of STATE.md and refer them to CONTRACT.md (the
canonical schema) rather than guessing.
The full schema and the ordering / staleness / versioning rules live in
CONTRACT.mdat the repo root. This skill deliberately restates only what it needs;route.pyis the executable mirror of that contract.
npx claudepluginhub lavidrori0702/tableau-dashboard-creator-skill --plugin tableau-dashboard-pluginScaffolds a new tableau-dashboard-plugin project with demo examples and initializes workflow state (step 1 of 8). Use when starting a new Tableau dashboard project.
Scans repository docs and metadata to identify testany-eng workflow stage, check baselines, and recommend next skill or branch like automation landing.
Scans project state (plans, reviews, tests, git) and recommends the next step in the 7-phase pipeline. Use when unsure what to do next.