Data Visualization Helper - Auto-activating skill for Visual Content. Triggers on: data visualization helper, data visualization helper Part of the Visual Content skill category.
34
Quality
0%
Does it follow best practices?
Impact
100%
1.01xAverage 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/data-visualization-helper/SKILL.mdQuality
Discovery
0%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 a placeholder with no substantive content. It provides only the skill name and a vague category without any concrete actions, natural trigger terms, or guidance on when to use it. The description would be completely ineffective for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, such as 'Creates bar charts, line graphs, scatter plots, and pie charts from tabular data'
Include a 'Use when...' clause with natural trigger terms like 'chart', 'graph', 'plot', 'visualize', 'histogram', 'dashboard'
Specify the types of data inputs supported (CSV, JSON, spreadsheets) and output formats to distinguish from other visual content skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Data Visualization Helper' is just a name, and 'Visual Content' is an abstract category. There are no specific capabilities like 'create charts', 'plot graphs', or 'generate dashboards' mentioned. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent guidance for skill selection. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'data visualization helper' repeated twice, which is the skill's own name rather than natural user language. Users would say things like 'chart', 'graph', 'plot', 'visualize my data', not the skill's title. | 1 / 3 |
Distinctiveness Conflict Risk | 'Visual Content' is extremely generic and could overlap with image generation, diagram creation, presentation skills, or any visual output. There are no distinct triggers to differentiate this skill from others in a visual/data domain. | 1 / 3 |
Total | 4 / 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 substantive content. It describes what a data visualization skill should do without providing any actual guidance, code examples, or actionable instructions. The entire content could be replaced with a single sentence: 'This skill helps with data visualization' - which would be equally unhelpful but more concise.
Suggestions
Add concrete, executable code examples for common visualization tasks (e.g., creating charts with Mermaid, generating SVG diagrams, using matplotlib/plotly)
Include specific guidance on choosing visualization types for different data scenarios (e.g., 'Use bar charts for categorical comparisons, line charts for time series')
Provide actual step-by-step workflows for creating visualizations, such as: 1. Analyze data structure, 2. Select chart type, 3. Generate code, 4. Validate output
Add references to detailed documentation files for specific visualization tools (e.g., MERMAID.md, CHARTS.md, PRESENTATIONS.md)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need explained. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual instructions on how to create data visualizations. The content only describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or processes for creating visualizations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed materials, no links to examples, and no structured navigation to related resources despite mentioning 'Related Skills'. | 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 | |
0c08951
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.