CtrlK
BlogDocsLog inGet started
Tessl Logo

plotly

Interactive visualization library. Use when you need hover info, zoom, pan, or web-embeddable charts. Best for dashboards, exploratory analysis, and presentations. For static publication figures use matplotlib or scientific-visualization.

60

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/plotly/SKILL.md

The canonical home for this skill is plotly in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%Scale 1-5

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

This is a competent skill that provides actionable, executable guidance for using Plotly with good API choice framing and concrete examples. Its main weaknesses are moderate verbosity — particularly the chart type catalog and common workflows sections that could be offloaded to reference files — and the fact that referenced bundle files don't actually exist. The skill would benefit from being trimmed to a tighter overview that delegates more content to the referenced files.

Suggestions

Move the 'Common Workflows' section content into a reference file (e.g., workflows.md) and replace with a brief summary linking to it, keeping the main SKILL.md as a concise overview.

Remove or significantly condense the chart type catalog in 'Core Capabilities' — Claude already knows Plotly's chart types; a simple 'See reference/chart-types.md for the full catalog' suffices.

Ensure the referenced bundle files (plotly-express.md, graph-objects.md, etc.) actually exist in the bundle to support the progressive disclosure structure.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary content. The 'Core Capabilities' section listing all 40+ chart types by category is largely a catalog that Claude already knows. The 'Common Workflows' section repeats patterns already shown or easily inferred. The 'Additional Resources' section with external URLs adds little value. However, the code examples themselves are tight and the API choice guidance is useful.

3 / 5

Actionability

The skill provides concrete, executable code examples throughout — scatter plots, subplots, exports, hover templates, Dash integration. Code is copy-paste ready with proper imports. Minor gap: some examples reference undefined variables (e.g., `correlation_matrix`, `z_data`, `data`) without setup, which reduces immediate executability.

4 / 5

Workflow Clarity

The skill clearly sequences the API choice decision (px vs go), shows how to combine them, and provides clear export workflows with install prerequisites. The workflows section provides good multi-step patterns. No destructive or batch operations are involved, so validation checkpoints aren't critical. Minor gap: no explicit guidance on debugging common issues (e.g., kaleido installation failures, figure not rendering).

4 / 5

Progressive Disclosure

The skill references five separate reference files (plotly-express.md, graph-objects.md, chart-types.md, layouts-styling.md, export-interactivity.md) with clear signaling, which is good structure. However, no bundle files were provided, so these references are unverifiable. Additionally, the main SKILL.md inlines substantial content (the entire 'Common Workflows' section, the chart type catalog, the Dash integration) that would be better placed in reference files, making the overview longer than necessary.

3 / 5

Total

14

/

20

Passed

Description

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

This is a well-crafted description that excels at completeness and distinctiveness, explicitly stating when to use it and when to use alternatives. Its main weakness is that it describes features of the visualization library rather than concrete actions the skill performs (e.g., creating specific chart types). It also omits the library name, which would be a strong natural trigger term.

Suggestions

Add concrete actions like 'Creates interactive line charts, bar charts, scatter plots, and heatmaps' to improve specificity beyond just listing library features.

Include the library name (e.g., 'Plotly') as a trigger term, since users often request tools by name.

DimensionReasoningScore

Specificity

Names the domain ('interactive visualization library') and lists a few concrete capabilities (hover info, zoom, pan, web-embeddable charts), but doesn't specify what concrete actions the skill performs (e.g., 'creates line charts, bar charts, scatter plots, heatmaps'). The actions listed are more features than tasks.

3 / 5

Completeness

Clearly answers both 'what' (interactive visualization with hover, zoom, pan, web-embeddable charts) and 'when' (dashboards, exploratory analysis, presentations), and even provides explicit boundary guidance on when NOT to use it ('For static publication figures use matplotlib or scientific-visualization').

5 / 5

Trigger Term Quality

Includes good natural terms like 'hover', 'zoom', 'pan', 'dashboards', 'exploratory analysis', 'presentations', 'web-embeddable charts'. However, it's missing the library name (likely Plotly), file formats, or common synonyms like 'interactive plots', 'interactive graphs', or 'HTML charts'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive by explicitly differentiating from matplotlib and scientific-visualization skills. The focus on interactivity (hover, zoom, pan) and web-embeddable output creates a clear niche with minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.