CtrlK
BlogDocsLog inGet started
Tessl Logo

visualization

Rules for charts and visualization. Use when the user asks for charts, graphs, plots, or visual representations (line, bar, pie, timeseries).

63

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/visualization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable with concrete tool calls, complete chart-spec examples, and a well-sequenced workflow featuring explicit validation and retry feedback loops; its only weaknesses are minor redundancy in the closing recap and a dangling reference to a non-existent bundle file.

Suggestions

Remove or merge the trailing ✅/❌ recap list, since it restates the a–d workflow and the execute_sql prohibition already covered above.

Resolve the references/system-query-log.md reference — either add the file to a references/ bundle or clarify that it belongs to the clickhouse-system-queries skill.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explaining what charts are), but the trailing ✅/❌ checklist recap and the repeated execute_sql prohibition in steps (c) and (d) duplicate content already stated in the workflow, leaving minor trimmable redundancy.

4 / 5

Actionability

It gives fully executable, copy-paste-ready guidance: exact tool calls (validate_sql, skill with ['sql-expert'], skill_resource), exact legendOption/values rules, and two complete chart-spec JSON examples covering line/bar and pie cases.

5 / 5

Workflow Clarity

The mandatory ordered workflow (a–d) has an explicit validation checkpoint (validate_sql before the spec), a feedback loop (retry up to 3 times by fixing SQL and re-validating), and a gating condition ('Only proceed if success: true'), with a closing checklist.

5 / 5

Progressive Disclosure

Content is well-organized into clear sections (WORKFLOW, CHART TYPE RULES, CRITICAL RULES, OUTPUT FORMAT) and appropriately inline for an ~80-line skill, but the reference to references/system-query-log.md points to a file absent from the bundle, a minor navigation gap.

4 / 5

Total

18

/

20

Passed

Description

65%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 has a strong, explicit 'Use when...' trigger clause with good natural keyword coverage and a distinct niche, but the 'what' is framed as 'Rules for' rather than concrete actions, slightly weakening specificity and completeness.

Suggestions

Replace the passive 'Rules for charts and visualization' with concrete verbs, e.g. 'Generates line/bar/pie chart specs from validated SQL'.

Add a couple more natural trigger synonyms (e.g. 'diagram', 'plot over time', 'dashboard') to round out trigger coverage.

DimensionReasoningScore

Specificity

The phrase 'Rules for charts and visualization' names the domain but uses no concrete action verbs (no 'generate', 'build', 'create'); the parenthetical '(line, bar, pie, timeseries)' lists chart types as scope rather than actions, so actions remain minimal and generic.

2 / 5

Completeness

Both 'what' ('Rules for charts and visualization') and 'when' ('Use when the user asks for charts, graphs, plots, or visual representations') are present, with the 'when' clause explicit and concrete; the 'what' is somewhat vague, keeping it just below a 5.

4 / 5

Trigger Term Quality

It lists natural trigger terms users say — 'charts, graphs, plots, or visual representations (line, bar, pie, timeseries)' — giving good keyword coverage, though a few natural variants like 'diagram' or 'dashboard' are missing and no file-extension-style triggers apply.

4 / 5

Distinctiveness Conflict Risk

The chart/visualization niche with specific type triggers (line, bar, pie, timeseries) is mostly distinct from other skills, with only minor overlap risk against general data-analysis skills that also produce charts.

4 / 5

Total

14

/

20

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
FrankChen021/datastoria
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.