CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, navigable overview with a strong validation-gated workflow and clean progressive disclosure. Its only weakness is that concrete generation patterns live in referenced files rather than the body, slightly limiting standalone actionability.

Suggestions

Inline one minimal HTML/SVG skeleton (e.g. a single stat-card or timeline snippet) so the body is actionable without opening references.

Tighten the 'Design philosophy' section into a one-line checklist to recover a few tokens.

DimensionReasoningScore

Conciseness

The body is lean and directive — terse section lists and prescriptive bullets — with only minor explanatory prose (e.g. the 'Whitespace is a feature' design-philosophy block) that could be trimmed.

4 / 5

Actionability

Concrete commands ('plannotator annotate <file> --gate', 'npx skills add nicobailon/visual-explainer -g --yes') and explicit reference paths are given, but the body delegates the actual HTML/SVG patterns to reference files rather than providing copy-paste code.

4 / 5

Workflow Clarity

Clear route-then-generate-then-validate sequence with an explicit hard-gate feedback loop: render Mermaid in both palettes, treat 'aria-roledescription="error"' / 'Syntax error in text' as non-deliverable, fix and rerun until every SVG passes.

5 / 5

Progressive Disclosure

The body is an overview that points one level deep to four real, clearly signaled reference files (design-system.md, svg-patterns.md, pr-components.md, theme-override.md) plus a delegated skill, with easy per-path navigation.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinct, cleanly routing by content type while stating both capability and triggers. It is held back only by slightly incomplete trigger-term synonym coverage.

Suggestions

Add a few natural synonyms or file hints (e.g. 'charts', 'presentations', '.html output') to broaden trigger-term coverage.

Consider naming the delivery surface ('Plannotator's annotation UI') in the description so users associate the skill with where output lands.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and output types — 'Generate self-contained HTML visualizations', 'implementation plans, PR explainers, architecture diagrams, data tables, slide decks' — giving comprehensive coverage rather than a few generic actions.

5 / 5

Completeness

Explicitly answers both 'what' (generate self-contained HTML visualizations with Plannotator theming) and 'when' ('Use for implementation plans, PR explainers, architecture diagrams...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords users would say ('implementation plans', 'PR explainers', 'architecture diagrams', 'slide decks'), but lacks synonyms/extensions like 'charts', 'presentations', or '.html', so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche tied to Plannotator theming with distinct content-type triggers, and it explicitly draws the boundary against nicobailon/visual-explainer, minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
backnotprop/plannotator
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.