plotly-chart-generator
Plotly Chart Generator - Auto-activating skill for Visual Content. Triggers on: plotly chart generator, plotly chart generator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/plotly-chart-generator/SKILL.mdQuality
Discovery
7%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 description is essentially auto-generated boilerplate with no substantive content. It lacks concrete actions, meaningful trigger terms, and any 'use when' guidance. It would be nearly useless for Claude to distinguish this skill from other visualization or charting skills in a large skill library.
Suggestions
Add specific capabilities such as 'Creates interactive Plotly charts including bar charts, line charts, scatter plots, heatmaps, and 3D visualizations from data'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for interactive charts, Plotly visualizations, data plots, or graphing with Plotly.'
Include natural trigger terms users would say: 'chart', 'graph', 'plot', 'visualization', 'interactive chart', 'plotly', 'data visualization', 'scatter plot', 'bar chart', 'line graph'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Plotly Chart Generator') but does not describe any concrete actions like creating specific chart types, customizing layouts, or exporting visualizations. It is essentially a label, not a capability description. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name and completely lacks a 'when should Claude use it' clause. There is no explicit trigger guidance or use-case description. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'plotly chart generator' repeated twice. It misses natural user terms like 'chart', 'graph', 'plot', 'visualization', 'bar chart', 'line chart', 'scatter plot', 'interactive chart', or 'data visualization'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Plotly' specifically does narrow the scope to a particular charting library, which provides some distinctiveness. However, the vague 'Visual Content' category and lack of specific actions could cause overlap with other charting or visualization skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no actual instructional content. It contains only generic boilerplate descriptions of when the skill activates and vague capability claims, but provides zero Plotly-specific guidance, code examples, or actionable steps. It would be entirely useless for helping Claude generate Plotly charts.
Suggestions
Add executable Plotly code examples for common chart types (bar, line, scatter, heatmap) with realistic data, e.g., `import plotly.express as px; fig = px.bar(df, x='category', y='value')`.
Include a concrete workflow: 1) determine chart type from user request, 2) prepare data, 3) generate chart code, 4) customize layout/styling, 5) export (HTML, PNG, etc.).
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) and replace with actionable content covering Plotly Express vs Graph Objects, common customizations, and output formats.
Add specific guidance on Plotly best practices such as responsive sizing, color accessibility, annotation patterns, and subplots.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, contains no actual Plotly-specific information, and pads the file with generic trigger descriptions and vague capability claims. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no Plotly API usage, no commands, no chart type examples. Every section is abstract and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to disclose progressively. | 1 / 3 |
Total | 4 / 12 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.