Install
$ agentstack add skill-lavidrori0702-tableau-dashboard-creator-skill-tableau-route ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
tableau-route
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.
How to run
- 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:
``bash python "${CLAUDE_SKILL_DIR}/scripts/route.py" "" ``
(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.
Interpreting the result
The script reports one of four situations:
- fresh project (no
STATE.md) → recommendstableau-initto scaffold the
project.
- a step is ready → recommends that step's skill (the first step whose status
is pending or stale, with its required inputs satisfied).
- blocked → a required upstream artifact is unresolved or missing on disk;
the script points at the upstream skill to run first.
- done → every step is
approvedorskipped; 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.md at the repo root. This skill deliberately restates only what it > needs; route.py is the executable mirror of that contract.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: laviDrori0702
- Source: laviDrori0702/tableau-dashboard-creator-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.