chart-rendering

Render governed Kun charts and tables from structured data for trustworthy comparison and lookup.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/chart-rendering/SKILL.md

Quality

Content

86%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 content is lean, well-structured, and actionable with a clear workflow and completion gates, making efficient use of the token budget. Its only gap is the absence of concrete tool-call examples illustrating common rendering cases.

Suggestions

Add one or two concrete render_chart invocation examples (e.g., a sample column/field/format declaration for a bar chart and a table) to make guidance copy-paste ready.

Consider a brief validation step in the workflow (e.g., verify the rendered output matches the source data) to reach full workflow-clarity maturity.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean and efficient with no padded explanations of concepts Claude already knows; every line is actionable guidance. Not 4 because there is nothing to trim.	5 / 5
Actionability	Provides concrete, specific guidance via a tool-routing table, a sequenced workflow, and a completion-gate checklist; as an instruction-only skill the absence of code is not penalized. Not 5 because no concrete render_chart call examples or sample column/field declarations are shown to cover common cases.	4 / 5
Workflow Clarity	A clearly sequenced 5-step workflow with completion gates serving as checkpoints; the destructive/batch cap does not apply since rendering is a single non-destructive operation. Not 5 because there is no explicit validation/feedback loop; not 3 because checkpoints are present.	4 / 5
Progressive Disclosure	Under 50 lines with no external references needed and no bundle files, yet well-organized into clear sections (Tool routing, Workflow, Completion gates, Boundaries, Delivery), qualifying for the simple-skill exception to score 5.	5 / 5
	Total	18 / 20 Passed

Description

58%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 clearly states what the skill does and targets a specific niche, but lacks an explicit 'Use when...' trigger clause and has thin keyword coverage missing common synonyms. It is solid but not exemplary.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user asks to visualize structured data as charts or tables for comparison or lookup').

Broaden trigger terms to include natural synonyms a user might say, such as 'graphs', 'plots', 'dashboards', 'visualizations', and relevant file extensions.

Enumerate the concrete actions more distinctly (e.g., 'Render bar, line, area, pie, donut, and table outputs from structured data') to strengthen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Kun charts and tables') and several concrete actions (render charts, render tables, comparison, lookup), with only minor bundling gaps. Not 5 because the actions are not comprehensively enumerated as distinct items; not 3 because it clearly lists more than 1-2 concrete actions.	4 / 5
Completeness	Has a clear 'what' (render charts/tables from structured data) but no explicit 'Use when...' trigger clause, only a weakly implied 'when' via 'trustworthy comparison and lookup'. Per the rubric, a missing 'Use when...' clause caps completeness at 3, so it cannot reach 4.	3 / 5
Trigger Term Quality	Includes relevant terms ('charts', 'tables', 'comparison', 'lookup', 'structured data') but misses common synonyms and variations users would say (graph, plot, dashboard, visualization, file extensions). Not 4 because coverage is thin and 'governed Kun' is jargon; not 2 because there is more than one generic keyword.	3 / 5
Distinctiveness Conflict Risk	The named 'governed Kun' system gives it a clear niche with minimal conflict risk versus unrelated skills, though it still overlaps somewhat with general charting/data-viz skills. Not 5 due to that residual overlap; not 3 because it is more specific than 'somewhat specific'.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: KunAgent/Kun
Path: resources/bundled-skills/chart-rendering/SKILL.md
Commit: ebce7f6

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.