experiment-graph
/experiment-graph
Render a read-only interactive graph of an experiment pipeline doc: dependencies, status and critical path at a glance. Use when the user wants to see the experiment steps as a graph, or says 'experiment graph', 'graph the experiments', 'visualize the pipeline', 'experiment status', 'experiment dependencies' or 'picture of the stages'.
- Author
- samuhs ↗
- Repository
- mad-science ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 12
- Scripts
- 6
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 6 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/ancestry.py, scripts/derive.py, scripts/docparse.py, scripts/model.py, scripts/render.py, scripts/test_model.py
What it does and when to use it
Render a read-only interactive graph of an experiment pipeline doc: dependencies, status and critical path at a glance. Use when the user wants to see the experiment steps as a graph, or says 'experiment graph', 'graph the experiments', 'visualize the pipeline', 'experiment status', 'experiment dependencies' or 'picture of the stages'.
Triggers from the description
Original author description
Render a read-only interactive graph of an experiment pipeline doc: dependencies, status and critical path at a glance. Use when the user wants to see the experiment steps as a graph, or says 'experiment graph', 'graph the experiments', 'visualize the pipeline', 'experiment status', 'experiment dependencies' or 'picture of the stages'.
How it works
- Overview
- When to Use
- Source of Truth Contract
- How to Run
- Architecture — do not rewrite the HTML
- Verification
- Common Mistakes
SKILL.md preview
--- name: experiment-graph description: "Render a read-only interactive graph of an experiment pipeline doc: dependencies, status and critical path at a glance. Use when the user wants to see the experiment steps as a graph, or says 'experiment graph', 'graph the experiments', 'visualize the pipeline', 'experiment status', 'experiment dependencies' or 'picture of the stages'." mode: true icon: crown color: cyan --- # Experiment Graph ## Overview Derive (read-only) an interactive graph of the experiments from a pipeline doc. The doc `docs/experiments-pipeline/<name>.md` is the **single source of truth**. The graph reflects **exactly what is written** in the doc — never what you think should be written. This skill only *renders a view*. It never edits the doc or the experiments. ## When to Use - The user wants a visual overview of the experiments (status, dependencies, critical path). - After updating a pipeline doc, to review the resulting graph. - To see at a glance: what is done, what is running, what is runnable now, what is blocked. Do **NOT** use to modify the pipeline doc or experiment statuses — that is `experiment-pipeline`'s job. ## Source of Truth Contract - Parse **only** from `docs/experiments-pipeline/<name>.md`. - Status values are literal: `not-implemented`, `waiting-to-run`, `running`, `completed`. - **NEVER "fix" an outdated status** (e.g. a doc that still says `not-implemented` for an experiment that clearly ran). Reflect it and flag it (see `references/layout.md`). - An unrecognized status value → treat as `not-implemented` and flag it. - The doc's own summary table and stated critical path are **claims to check**, not facts to trust. When they disagree with the edges, say so in the output. ## How to Run `<skill-dir>` is the directory containing this `SKILL.md` (it differs per agent and install method). ```bash python3 <skill-dir>/scripts/render.py docs/experiments-pipeline/<name>.md ``` That writes `<name>.html` (interactive, standalone) and `<name>.mmd` (Mermaid) next to the doc, and prints a summary line: ``` nodes=22 edges=26 layers=9 critPaths=6 runnable=9 anomalies=2 ``` Default doc: the newest `docs/experiments-pipeline/*.md`, or the one the user points to. Use `--html` / `--mmd` to redirect output. Then **show the user the HTML** (`open <name>.html` on macOS, `xdg-open` on Linux) and paste the Mermaid block in chat for pasting into an MR/issue/Backstage. ## Architecture — do not rewrite the HTML ``` scripts/ docparse.py doc -> experiments, stages, stated claims (pure, total) derive.py edges -> layers, critical path, runnable, blocked, anomalies ancestry.py reachability chains behind the selection highlight model.py compose the above, cross-check the doc's claims, serialise render.py fill the template, write both artifacts graph-template.html static presentation: HTML + CSS + JS, %%GRAPH_DATA%% placeholder test_model.py regression tests for the derivation references/ extraction.md doc -> model (what each field means) layout.md layers, critical path, runnable/blocked, anomalies interaction.md the interaction contract + verification checklist ``` **Division of responsibility.** `derive.py` owns every derived fact; `model.py` composes and serialises; the template owns pixels only and re-derives nothing. Never regenerate the HTML by hand-writing a new file — that is what made the previous version drift and become unreadable. To change the visuals, edit `graph-template.html`; to change what is derived, edit `derive.py`; to change what is read from the doc, edit `docparse.py`. Then re-run `render.py`. The modules import each other by bare name; the entry points (`render.py`, `test_model.py`) put `scripts/` on `sys.path`. `pyrightconfig.json` mirrors that for the editor. **Determinism.** The same doc always yields a byte-identical HTML (the template is static; only the payload varies). Verify with two runs + `diff`. ## Verification ```bash python3 <skill-dir>/scripts/test_model.py ``` Covers the real doc (node/edge/layer/critical-path counts, literal statuses, human work, reflected anomalies) plus a synthetic doc for the contract (unknown status, explicit `**Human**`, transitive blocking, longest-path layering). Run it after any change to `model.py`. The full manual checklist is in `references/interaction.md`. ## Common Mistakes - Trusting the summary table's layers instead of deriving from the edges (it contains errors). - "Correcting" an outdated status instead of reflecting it and flagging it. - Building a CDN-dependent HTML that fails offline or behind the proxy — the artifact must open from `file://`. - Reporting a single critical path when several maximal paths exist. - Hand-writing the HTML instead of editing the template and re-running `render.py`. - Detecting human work from the Result prose (it false-positives on words like "pool anotado"); the title is the signal. - Editing the pipeline doc while rendering the graph.
Files in this package (12)
- SKILL.md 5 KB
- references/extraction.md 3 KB
- references/interaction.md 7 KB
- references/layout.md 3 KB
- scripts/ancestry.py 2 KB
- scripts/derive.py 8 KB
- scripts/docparse.py 6 KB
- scripts/graph-template.html 41 KB
- scripts/model.py 7 KB
- scripts/pyrightconfig.json 1 KB
- scripts/render.py 3 KB
- scripts/test_model.py 7 KB
Versions
The database has no other skills named experiment-graph.
Database snapshot: 13.11.2026 · package version f57a6ce907f1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90experiment-pipeline
Break an experiment doc into small vertical slices (stages, phases, experiments) with goals, metrics, status and dependencies, tracked in docs/experiments-pipeline. Use when the experiment contract is settled and the user wants a run plan, wants to know which experiments can run… - 100karpathy-graph-visualize
Render a karpathy-graph for humans — an interactive HTML explorer, a Mermaid diagram for docs and PRs, and a health report — then explain what the picture actually shows. Use when the user asks to see, visualize, draw, or open the graph, wants a diagram for documentation, or… - 100finding-experiments
Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment ("split test demo", "the File… - 95monitor-experiments
Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what… - 95okf-visualize-bundle
OKF — Render an Open Knowledge Format (OKF) bundle as a single self-contained, interactive HTML graph (viz.html) of its concepts and links. Use when asked to visualize, graph, preview, or explore an OKF bundle. - 100experiment-bridge
Workflow 1.5: Bridge between idea discovery and auto review. Reads EXPERIMENT_PLAN.md, implements experiment code, deploys to GPU, collects initial results. Use when user says \"Obtain experiments\", \"implement experiments\", \"bridge\", \"From planning to running…