Agent skill · Data & Analytics

plannotator-visual-explainer

Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.

Michael Ramos7,402★ · +233/wk · 1 repos on radarProfile →
claude-codecodexships scriptsApache-2.0
Install
npx skills add backnotprop/plannotator --skill plannotator-visual-explainer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 6 KB
Bundled scripts: yes
Path: apps/skills/extra/plannotator-visual-explainer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 7,510 · +108 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Plannotator Visual Explainer Three paths depending on content type. Each has its own references and structure. ## Route by content type **Implementation plan, design doc, or proposal** → Follow the [Plan path](#plan-path). Read `references/design-system.md` and `references/svg-patterns.md`. Prescriptive structure. **PR explainer, diff review, or code change walkthrough** → Follow the [PR path](#pr-path). Read `references/design-system.md` and `references/pr-components.md`. Prescriptive structure. **Everything else** (architecture diagrams, data tables, slide decks, project recaps, general visual explanations) → Follow the [Visual explainer path](#visual-explainer-path). Delegates to nicobailon/visual-explainer with Plannotator theme tokens. ## Delivery Always deliver via Plannotator's annotation UI. Do NOT use `open` or `xdg-open`. For any deliverable that uses Mermaid, render every diagram with Mermaid 11 in both the light and dark palettes before opening the annotation UI. Rendering is a hard gate: an exception, empty SVG, or error output such as `aria-roledescription="error"` or `Syntax error in text` means the explainer is not deliverable. Fix the diagram or theme configurati

What's inside
Steps it walks through
  1. Route by content type
  2. Delivery
  3. Plan path
  4. PR path
  5. Visual explainer path
  6. Design philosophy (all paths)
Ships with 5 files
  • SKILL.test.ts
  • references/design-system.md
  • references/pr-components.md
  • references/svg-patterns.md
  • references/theme-override.md
Commands it runs
plannotator annotate <file> --gate
plannotator annotate <file>
More from plannotator
All skills →
About this skill
What does the plannotator-visual-explainer skill do?

Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.

How do I install it?

Run `npx skills add backnotprop/plannotator --skill plannotator-visual-explainer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From backnotprop/plannotator, a repository with 7,510 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going