CtrlK
BlogDocsLog inGet started
Tessl Logo

visualization-best-practices

Review chart choice, labeling, accessibility, and storytelling quality for existing visualizations. Use as an explicit/manual helper for critique and cleanup, not as the main owner for scientific figure production or general chart generation.

62

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/visualization-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured but lacks concrete, actionable review guidance — it tells Claude what to look at rather than how to evaluate it. Adding a concrete review checklist or worked examples would substantially raise actionability.

Suggestions

Add a concrete review checklist (e.g., specific checks for label legibility, color-contrast thresholds, scale appropriateness) so Claude has executable criteria rather than category names.

Include one or two short worked examples contrasting a weak chart fix vs an improved one to make the critique guidance actionable.

Provide a lightweight ordered review procedure (assess encoding -> check labels/legend -> check scales -> check color/accessibility -> summarize fixes) to give the workflow explicit sequencing.

DimensionReasoningScore

Conciseness

The body is lean with no padding or over-explanation of concepts Claude already knows; every section earns its place, matching the score-5 anchor for efficient, competence-assuming content.

5 / 5

Actionability

Names review categories (labels, legends, scales, color, accessibility) but provides no concrete checklist, examples of good vs bad, or specific executable guidance, fitting score 2 (high-level hints missing the specific steps) rather than 3 (no concrete structured detail).

2 / 5

Workflow Clarity

As a simple single-purpose review skill the action is reasonably unambiguous and well-scoped, but there is no ordered review procedure or checklist, so it sits at score 4 (clear but light) rather than 5 (no explicit sequenced workflow).

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no inlined content needing separation; well-organized into clear sections, satisfying the simple-skill exception allowing score 5 with just well-organized sections.

5 / 5

Total

16

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, well-positioned, and clearly differentiated from sibling skills. Its main weakness is that the "when to use" guidance is framed as role positioning rather than concrete user-spoken trigger phrases.

DimensionReasoningScore

Specificity

Lists several concrete review actions ("chart choice, labeling, accessibility, and storytelling quality") with minor coverage gaps, matching the score-4 anchor rather than 3 (more than 1-2 actions) or 5 (not a comprehensive enumerated action set).

4 / 5

Completeness

Has a clear "what" and an explicit "Use as..." trigger/positioning clause, but the "when" is role-positioning rather than concrete user-trigger phrases, matching score 4 (both present, when could be more specific).

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms (chart, labeling, accessibility, visualizations, figures) but missing common synonyms and variations like "graphs", "plots", "dashboards", or file extensions, fitting score 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Explicitly carves a niche (reviewing existing charts) and distinguishes from scientific-visualization, creating-data-visualizations, and scientific-schematics, giving a clear niche with minimal conflict risk per the score-5 anchor.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
foryourhealth111-pixel/Vibe-Skills
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.