Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill visualization-best-practicesVisualization Best Practices - Auto-activating skill for Data Analytics. Triggers on: visualization best practices, visualization best practices Part of the Data Analytics skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped - it functions more as a label than a useful skill description. It lacks any concrete actions, has redundant and limited trigger terms, and provides no guidance on when Claude should select this skill. The description would be nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Recommends chart types, color palettes, axis formatting, and layout principles for effective data visualization'
Include a 'Use when...' clause with natural trigger terms like 'chart', 'graph', 'plot', 'data viz', 'how should I visualize', 'best way to show data'
Remove the redundant trigger term and expand to include variations users would naturally say when seeking visualization guidance
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only names a domain ('visualization best practices') without describing what the skill actually does (e.g., create charts, recommend color schemes, format axes). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and has no explicit 'when to use' guidance - only mentions it's 'auto-activating' without explaining the conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant (lists 'visualization best practices' twice) and miss natural variations users would say like 'chart', 'graph', 'plot', 'data viz', 'how to visualize', or specific chart types. | 1 / 3 |
Distinctiveness Conflict Risk | Being part of 'Data Analytics' category provides some context, but 'visualization best practices' is broad enough to potentially conflict with charting tools, dashboard skills, or general data analysis skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is an empty template with no actual substance about visualization best practices. It contains only meta-descriptions of what the skill claims to do without providing any concrete guidance, examples, code, or actionable instructions. The content would be identical if the topic were any other subject—it's entirely generic boilerplate.
Suggestions
Add concrete visualization best practices content: chart type selection guidelines, color palette recommendations, accessibility considerations, and when to use specific chart types (bar vs line vs scatter)
Include executable code examples showing how to create effective visualizations using common libraries (matplotlib, seaborn, plotly) with before/after comparisons
Provide a decision tree or checklist for choosing appropriate visualizations based on data type and communication goal
Add specific anti-patterns to avoid (e.g., 3D pie charts, truncated axes, misleading scales) with visual examples or code showing the correct approach
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about visualization best practices. It explains when the skill activates and what it claims to do, but contains zero substantive guidance. | 1 / 3 |
Actionability | No concrete guidance, code, examples, or specific instructions are provided. The content only describes what the skill claims to do in abstract terms without any executable or actionable content. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences for any visualization task. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, no examples, no links to related documentation. The content is a shallow placeholder with no depth or navigation. | 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
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.