Plotly Chart Generator - Auto-activating skill for Visual Content. Triggers on: plotly chart generator, plotly chart generator Part of the Visual Content skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill plotly-chart-generator36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/plotly-chart-generator/SKILL.mdDiscovery
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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing useful trigger guidance. It lacks concrete actions, natural user keywords, and explicit usage scenarios. The redundant trigger terms and generic category reference provide minimal value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates interactive charts including line plots, bar charts, scatter plots, heatmaps, and 3D visualizations using Plotly.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks to plot data, create interactive charts, visualize datasets, or mentions Plotly, graphs, or data visualization.'
Add common file/data context triggers like 'working with CSV data', 'DataFrame visualization', or 'dashboard creation' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Plotly Chart Generator' without listing any concrete actions. It doesn't describe what the skill actually does (e.g., create line charts, scatter plots, bar graphs, interactive visualizations). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is circular (triggers on its own name). There's no explicit 'Use when...' clause with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('plotly chart generator' repeated twice) and miss natural user phrases like 'create a chart', 'plot data', 'visualization', 'graph', 'interactive chart', or specific chart types. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Plotly' specifically distinguishes it from other charting tools (matplotlib, seaborn), but 'Visual Content' is vague and could overlap with image generation or other 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 template with no actual Plotly-specific content. It provides zero actionable guidance, no code examples, and no workflow for creating charts. The entire content could apply to any skill by replacing 'plotly chart generator' with any other term.
Suggestions
Add executable Plotly code examples showing common chart types (line, bar, scatter) with copy-paste ready Python code
Include a quick-start workflow: install plotly, create figure, customize, export/display
Provide specific Plotly patterns like layout configuration, trace types, and export formats
Remove generic boilerplate sections ('When to Use', 'Example Triggers') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Plotly. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly ('generates production-ready code') but provides zero actual Plotly examples or syntax. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only lists vague capabilities without any sequence of actions for creating Plotly charts. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no depth or navigation. | 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 | |
Table of Contents
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.