chart-type-recommender
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill chart-type-recommenderChart Type Recommender - Auto-activating skill for Data Analytics. Triggers on: chart type recommender, chart type recommender Part of the Data Analytics skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It fails to explain what the skill does, provides no meaningful trigger terms (just repeats the skill name), and gives no guidance on when Claude should select it. The only redeeming quality is that 'chart type' provides minimal domain specificity.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Analyzes data characteristics and recommends appropriate chart types (bar, line, scatter, pie, etc.) based on data structure and visualization goals.'
Replace the duplicate trigger terms with natural user phrases like 'what chart should I use', 'best visualization for', 'recommend a graph type', 'which chart works best'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs help choosing between chart types, asks what visualization to use, or wants recommendations for displaying their data.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Chart Type Recommender') without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'recommends', 'analyzes', 'suggests' are present. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no meaningful use cases). The 'Triggers on' section just repeats the skill name rather than providing actual trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('chart type recommender, chart type recommender'). Missing natural user phrases like 'what chart should I use', 'best visualization', 'graph type', 'which chart for my data'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Chart Type Recommender' is somewhat specific to chart/visualization selection, which provides some distinctiveness. However, the lack of detail means it could overlap with general data visualization or analytics skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actual content. It describes what a chart type recommender skill would do but provides zero actionable guidance on how to actually recommend chart types based on data characteristics. The entire content could be replaced with a simple decision matrix or flowchart that would be infinitely more useful.
Suggestions
Add a decision matrix mapping data types (categorical, continuous, time-series) to appropriate chart types (bar, scatter, line, etc.)
Include concrete examples: 'For comparing categories → bar chart; for showing trends over time → line chart; for correlation between two variables → scatter plot'
Provide a simple workflow: 1) Identify data dimensions, 2) Determine comparison type (composition, distribution, relationship, comparison), 3) Select chart type from lookup
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual chart selection criteria
| 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 meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no specific commands, no examples of chart types, no decision criteria. The skill describes what it claims to do but never actually instructs how to recommend chart types. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. A chart type recommender should have clear steps like: analyze data structure, identify variable types, match to appropriate visualizations. None of this exists. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure for discovery. No references to detailed materials, no examples section, no decision trees or lookup tables that would be appropriate for this type of skill. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.