plotly-dashboard-skill
Skill9 starsChanged 4 months agoMITView on GitHub
Build Plotly Dash apps with one shared figure template and fast callbacks. Use when data needs an interactive multi-view dashboard.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- ai-scientist-evaluatorSkill
- arxiv-searchSkill
- beautiful-data-vizSkill
- bio-annotationSkill
- bio-assembly-qcSkill
- bio-binning-qcSkill
- bio-fasta-database-curatorSkill
- bio-foundation-housekeepingSkill
- bio-gene-callingSkill
- bioinformatics-projectSkill
- bio-interdomain-hgtSkill
- bio-logicSkill
- bio-phylogenomicsSkill
- bio-prefect-dask-nextflowSkill
- bio-protein-clustering-pangenomeSkill
- bio-reads-qc-mappingSkill
- biorxiv-searchSkill
- bio-stats-ml-reportingSkill
- bio-structure-annotationSkill
- bio-viromicsSkill
- bio-workflow-methods-docwriterSkill
- crossref-lookupSkill
- csag-extractionSkill
- exploratory-data-analysisSkill
- manuscript-review-councilSkill
- notebooksSkill
- pdf-to-mdSkill
- polars-dovmedSkill
- proposal-reviewSkill
- public-db-lookupSkill
- scientific-impact-assessmentSkill
- scientific-writingSkill
- tracking-taxonomy-updatesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 18
Start from examples/app.py, the runnable app this skill tests.
- Distinctive: line 35
Run the smoke test before calling a dashboard done:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plotly Dashboard Skill
Build interactive Dash dashboards with a single source of truth for UI and figure styling. Visual rules (greyscale first, color only to encode information, direct labels, accessibility) come from /beautiful-data-viz; this skill applies them to Dash and adds app structure and performance.
Instructions
- Capture audience, questions, and data constraints.
- Pick a layout pattern and component library. Layout, typography, color, and the shared figure template are in references/style.md. Charts start grey; add color only for a category the reader must tell apart, the one highlighted finding or selection, or an ordered or signed quantity.
- Register the figure template once, before building any chart, so no figure is styled by hand.
- Build the layout skeleton before callbacks.
- Implement callbacks with clear inputs and outputs. Project structure, the data-callback-to-render-callback fan-out, and the advanced callback tools are in references/architecture.md.
- Optimize slow callbacks with caching, pre-aggregation, or background callbacks; the same reference covers when each applies.
- Start from examples/app.py, the runnable app this skill tests. Copy its structure rather than writing a skeleton from scratch.
Input Requirements
- Audience and key decisions
- Data sources and update cadence
- Required filters and views
- Deployment constraints
Output
- Dash app scaffold (layout + callbacks)
- Consistent theming and figure templates
- README with usage notes
Quality Gates
Run the smoke test before calling a dashboard done:
uv run --script examples/app.py --smoke --latency-budget-ms 300It must return HTTP 200 with a measured pure-callback p95 inside the declared budget.
Visual and interaction:
- Page has a clear title and a "last updated" stamp
- Filters are grouped, have sensible defaults, and their current state is visible
- Spacing, alignment, and legend placement are consistent; legends do not cover data
- Charts carry readable titles and axis labels or units in the title
- Tooltips include units and clean formatting
- Marks are grey unless color encodes a category, the highlighted finding, or an ordered or signed quantity; colors are colorblind-safe and never the only encoding
- Empty states are handled; no blank white cards
- Mobile and tablet views are usable, with no unintended horizontal scroll
- Click-to-filter is obvious and reversible, with a clear reset action
Performance:
- Common interactions stay under roughly 300 ms
- Expensive work is cached or moved to background callbacks
- Large tables use AG Grid virtualization
- No callback chains that create spaghetti dependencies
Code and documentation:
- Structure separates pages, components, callbacks, and utils
- Callbacks are small; reusable figure helpers replace repeated styling code
- Requirements are pinned
- README covers purpose, audience, local run, configuration, data sources, and a screenshot
- A data dictionary defines key metrics and known caveats
Non-Goals
- Static publication figures. Use
/beautiful-data-viz, which also sets the visual rules this skill follows. - Data analysis itself. This skill presents results; it does not compute them.
Troubleshooting
Issue: Slow callbacks Solution: Cache expensive steps or pre-aggregate data. See references/architecture.md.
Issue: Charts drift out of a shared look Solution: A figure is being styled inline instead of inheriting the registered template. Move the override into the template in references/style.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

