← ClaudeAtlas

discovery-dashboardlisted

Cross-domain / Research platform observability — Read-only live operations dashboard for a Microsoft Discovery workspace, built by scraping `.discovery/` and git. Shows leaf-task progress with approved-complete and awaiting-review kept strictly separate, the executing / ready / blocked work front from live `dependsOn` edges, engine liveness verified against real process identity, agent runs deduplicated across an alias graph, observed CLIO investigations, and a coverage panel separating "could not read" from "genuinely empty". Never writes to the workspace. WHEN: "project dashboard", "discovery dashboard", "what's the status of this project", "what's stuck", "how close are we to done", "are the engines still running", "is anything running", "are any agents running", "is clio running", "open the dashboard".
timothymeyers/discovery-tools · ★ 1 · AI & Automation · score 70
Install: claude install-skill timothymeyers/discovery-tools
# discovery-dashboard — Discovery workspace live operations A read-only view of what is actually happening in a Discovery workspace. Its design goal is **not** to show everything available. It is to answer four questions honestly: how close are we, what is stuck, what is actually running, and what can this view not see. ## Resolve the payload — once per session This skill can be installed as a personal skill, a project skill, or as part of a plugin, so never hardcode its location. Run this first and reuse `$DASH`: ```bash DASH=$(find ~/.copilot/skills ~/.copilot/installed-plugins ~/.agents/skills \ .github/skills .claude/skills .agents/skills \ -name discovery_dashboard.py -path '*discovery-dashboard*' \ 2>/dev/null | head -1) echo "$DASH" ``` If `$DASH` is empty, tell the user the skill payload could not be located and stop. Standard library only — there is nothing to install. ## Default behavior 1. **Resolve the workspace.** If the user names a path, use it. Otherwise use the current working directory. If `<workspace>/.discovery/` does not exist, say so and stop — this skill has nothing to read. 2. **Pick a mode.** Prefer `--once` when the user asked a question in passing; only start a server when they want to look at something. | Intent | Command | |---|---| | "what's stuck?" / "where are we?" | `python3 "$DASH" --workspace <ws> --once` | | "open the dashboard" | `python3 "$DASH" --workspace <ws> --no-open`