chart-type-recommender
Chart Type Recommender - Auto-activating skill for Data Analytics. Triggers on: chart type recommender, chart type recommender Part of the Data Analytics skill category.
34
3%
Does it follow best practices?
Impact
87%
0.96xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/chart-type-recommender/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 a placeholder that repeats the skill name without providing any substantive information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it very difficult for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions such as 'Analyzes dataset characteristics (variable types, distributions, relationships) and recommends appropriate chart types like bar charts, scatter plots, histograms, or heatmaps.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks what type of chart to use, which visualization is best, how to plot their data, graph recommendations, or choosing between chart types.'
Include natural keyword variations users would actually say, such as 'visualization', 'graph', 'plot', 'best chart for', 'how to visualize', 'data visualization recommendation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Data Analytics') and a concept ('Chart Type Recommender') but does not describe any concrete actions. There are no specific capabilities listed such as 'analyzes datasets', 'suggests bar/line/scatter charts', or 'evaluates data distributions'. | 1 / 3 |
Completeness | The description barely answers 'what does this do' (recommends chart types, implied only by the name) and has no meaningful 'when should Claude use it' clause. The 'Triggers on' line just repeats the skill name rather than providing explicit usage guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'chart type recommender' repeated twice. It misses natural user phrases like 'what chart should I use', 'best visualization', 'graph type', 'plot recommendation', 'which chart', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The concept of 'chart type recommender' is a somewhat specific niche within data analytics, which provides some distinctiveness. However, the vague 'Data Analytics' category label could overlap with many other analytics-related 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 shell with no substantive content. It consists entirely of generic boilerplate that describes what a chart type recommender skill would do without providing any actual guidance, decision logic, examples, or code. It adds zero value to Claude's capabilities.
Suggestions
Add a concrete decision matrix or flowchart mapping data characteristics (e.g., number of variables, data types, comparison vs. composition vs. distribution) to specific chart types with rationale.
Include executable code examples showing how to analyze a dataset and programmatically recommend appropriate chart types (e.g., using Python/pandas to inspect data shape and suggest visualizations).
Provide 3-4 concrete input/output examples: given a described dataset, show the recommended chart type and why, so Claude has actionable patterns to follow.
Remove all boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) that contain no actionable information and replace with actual chart recommendation logic.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'chart type recommender' excessively, and provides zero actual information about how to recommend chart types. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no decision logic, no chart type mappings, no examples of input data matched to recommended chart types. It only describes what the skill claims to do without actually doing it. | 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 any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat list of generic sections with no meaningful structure, no references to detailed materials, and no actual content to organize. The sections are empty boilerplate headings. | 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
4dee593
- 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.