CtrlK
BlogDocsLog inGet started
Tessl Logo

data-report

Turns CSV, Excel, or JSON data into a polished visual report page.

54

Quality

61%

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 ./skills/data-report/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is a tight, well-organized template spec that captures non-obvious gotchas like the Chart.js ResizeObserver height trap and the requirement to parse real data. Its main gap is the lack of a complete executable HTML scaffold and explicit render-validation checkpoints.

Suggestions

Add a minimal complete HTML scaffold (doctype, CDN script tags, one canvas wrapper, one KPI card) so the guidance is copy-paste ready.

Include an explicit validation step, e.g. after rendering, confirm each chart parent has a fixed height and that parsed data is non-empty before drawing.

Show a concrete data-parsing snippet (e.g. parsing a CSV/JSON blob into the chart's datasets) to make the "parse actual data" requirement actionable.

DimensionReasoningScore

Conciseness

The body is a lean bulleted spec with no padding and no explanation of concepts Claude already knows; even the longer ResizeObserver bullet is genuinely non-obvious critical knowledge that earns its tokens, matching the level-3 anchor.

3 / 3

Actionability

It gives concrete specifics (Chart.js/ECharts, jsdelivr CDN, a div wrapper snippet with exact style, pixel ranges, table styling attributes), but there is no complete copy-paste executable HTML example, so it stops at the level-2 anchor of concrete but incomplete guidance.

2 / 3

Workflow Clarity

Sections are ordered top-to-bottom (header, KPI grid, charts, table, insights, footer) with explicit constraints ("must parse actual data", fixed-height rule), but there is no validate→fix→retry checkpoint for rendering, fitting the level-2 anchor of sequenced steps with missing validation.

2 / 3

Progressive Disclosure

The skill is under 50 lines with no external references needed and is organized as a clear bulleted template list, so per the simple-skills guideline progressive disclosure scores 3 on well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

50%

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 competent and concrete about what the skill does, naming clear input formats and a clear output artifact. Its main weakness is the absence of any "Use when..." trigger clause, which caps both completeness and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user has CSV, Excel, or JSON data and wants a visual report, dashboard, or charted summary page."

Expand output-side natural keywords ("report", "chart", "dashboard", "data visualization") to improve trigger-term coverage.

Optionally enumerate concrete actions (parse data, render KPI cards, draw charts, build a styled table) to lift specificity to level 3.

DimensionReasoningScore

Specificity

Names the input domain ("CSV, Excel, or JSON data") and a concrete output action ("polished visual report page"), but lists only a single action rather than multiple specific concrete actions, so it falls short of the level-3 anchor.

2 / 3

Completeness

It clearly answers the "what" but provides no "Use when..." clause or equivalent explicit trigger guidance, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Natural input-format terms like "CSV", "Excel", and "JSON" appear, but coverage of output-side natural variations (e.g. "chart", "dashboard", "data visualization", "report") is thin, matching the level-2 anchor of relevant keywords missing common variations.

2 / 3

Distinctiveness Conflict Risk

The data-to-report niche is reasonably specific, but without explicit trigger guidance it could still overlap with general charting or data skills, fitting the level-2 anchor.

2 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.