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.

74

Quality

91%

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

100%

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 tight, actionable overview that routes cleanly across three paths with copy-paste commands, an explicit validation hard gate, and well-organized one-level-deep references.

DimensionReasoningScore

Conciseness

The body is lean and directive (routing, delivery commands, per-path structures) with no explaining of concepts Claude already knows; it assumes competence and nearly every token earns its place.

3 / 3

Actionability

Copy-paste-ready commands ("plannotator annotate <file> --gate", "npx skills add nicobailon/visual-explainer -g --yes") and concrete structural specs (HIGH/MED/LOW risk chips, stat cards, before/after panels) give fully actionable guidance.

3 / 3

Workflow Clarity

The sequence routes by content type then read-references then build then deliver, with an explicit Mermaid validate→fix→rerun "hard gate" feedback loop including concrete error signals (aria-roledescription="error", "Syntax error in text").

3 / 3

Progressive Disclosure

The overview routes to four clearly-signaled one-level-deep references (design-system.md, svg-patterns.md, pr-components.md, theme-override.md), all of which exist in ./references/, with content appropriately split out of the body.

3 / 3

Total

12

/

12

Passed

Description

82%

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 concrete and has an explicit trigger clause with good natural-term coverage, but it relies on essentially one primary action and its broad visual-explanation scope overlaps with the skill it delegates to and a sibling skill.

Suggestions

Add one or two more distinct concrete verbs (e.g. "build", "render", "theme") so specificity reaches the multiple-distinct-actions bar.

Narrow the catch-all "any visual explanation of technical concepts" or state the boundary with visual-explainer more sharply to reduce distinctiveness/conflict risk.

Lead with the trigger clause ("Use for ...") before the delegation detail so the when-guidance is unambiguous at a glance.

DimensionReasoningScore

Specificity

"Generate self-contained HTML visualizations with Plannotator theming" names one concrete primary action plus a delegation branch, but unlike the 3-anchor it is a single verb with variations rather than multiple distinct concrete actions.

2 / 3

Completeness

It answers both what ("Generate self-contained HTML visualizations...") and when via the explicit "Use for ..." trigger clause, matching the 3-anchor with an explicit trigger.

3 / 3

Trigger Term Quality

"implementation plans, PR explainers, architecture diagrams, data tables, slide decks" gives strong coverage of natural terms a user would actually say when requesting visual explanations.

3 / 3

Distinctiveness Conflict Risk

"any visual explanation of technical concepts" plus explicit delegation to nicobailon/visual-explainer and a sibling plannotator skill creates real overlap with similar visual skills, so it is not yet a conflict-free niche.

2 / 3

Total

10

/

12

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.