CtrlK
BlogDocsLog inGet started
Tessl Logo

data-visualizer

Use this skill when the user wants to create charts, graphs, or dashboards from data — bar charts, line charts, scatter plots, heatmaps, or multi-panel dashboards.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./external/community/data-visualizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-organized, executable code-utility skill that assumes competence and stays lean. Its main weakness is workflow clarity: capabilities are listed as a function catalog without an explicit, sequenced usage flow.

Suggestions

Add a short numbered workflow (e.g., 1) describe data + goal, 2) pick a chart type via the selector, 3) call the matching function, 4) verify the output file) to give the catalog a clear usage sequence.

Flesh out the remaining chart types from the enum (heatmap, histogram, box, area, pie, scatter) with the same executable function pattern used for bar/line/dashboard, or explicitly note they rely on the one-liner quick-reference forms.

Trim the inline chart-type-selector Anthropic API block into a smaller helper or move it to a references/ file, keeping the SKILL.md overview focused on the rendering functions.

DimensionReasoningScore

Conciseness

The body is lean, code-dense, and assumes Claude's competence (no library primers), but the full chart-type-selector API block and the "Includes AI-powered chart type selection" line are minor instances of over-content that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready functions for bar, line, and dashboard charts, but heatmap and histogram appear only as quick-reference one-liners and three of the eight enum chart types lack implementations, leaving minor gaps.

4 / 5

Workflow Clarity

Functions are presented as a catalog rather than a sequenced workflow; the select-chart-type → render order is only implicit and there are no checkpoints or guidance on when to use the AI selector versus calling functions directly.

3 / 5

Progressive Disclosure

No bundle files exist and the body is self-contained with well-organized section headers (Overview, Chart Type Selector, Matplotlib, Plotly, Quick Reference); it inlines full implementations at >50 lines rather than splitting them out, a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

83%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.

A strong, trigger-led description that clearly states both capability and use-conditions with concrete chart-type examples. It is slightly held back by a single-capability framing and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Names the data-visualization domain plus six concrete chart types ("bar charts, line charts, scatter plots, heatmaps, or multi-panel dashboards"), but all are variations of a single "create charts" capability rather than multiple distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both: the "what" (create charts, graphs, dashboards from data) and the "when" ("Use this skill when the user wants to create charts…") with concrete trigger phrases and chart-type examples.

5 / 5

Trigger Term Quality

Includes natural user terms ("charts, graphs, or dashboards from data") but omits common synonyms such as "plot", "visualize", or "visualization", so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

The data-visualization niche is distinct with chart-specific triggers, but "dashboards from data" carries minor overlap risk with spreadsheet/BI dashboard skills.

4 / 5

Total

17

/

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
ProwlrBot/prowlr-marketplace
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.