CtrlK
BlogDocsLog inGet started
Tessl Logo

data-report

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

60

Quality

70%

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

78%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 a concise, actionable template spec with concrete code fragments and a valuable ResizeObserver gotcha, well-organized for a single-purpose generation skill with no need for external references.

DimensionReasoningScore

Conciseness

A lean bullet list that assumes Claude's competence and avoids explaining basics; the one long bullet is a non-obvious ResizeObserver gotcha that earns its tokens, matching anchor 4 ('efficient; minor instances that could be trimmed') rather than 5 because that bullet is somewhat padded.

4 / 5

Actionability

Gives concrete guidance — 'Chart.js or ECharts (jsdelivr CDN)', '<div style="position:relative;height:NNNpx">', 'responsive:true, maintainAspectRatio:false', heights ~40px/~240–280px — but 'NNNpx' is a placeholder and there is no complete copy-paste HTML example, so anchor 4 ('mostly executable, minor gaps') fits over 5.

4 / 5

Workflow Clarity

The component list implies a clear top-to-bottom page sequence (header → KPI → charts → table → insights → footer) and the single build task is unambiguous, matching anchor 4; not 5 because there is no explicit validation/feedback checkpoint, though this generation skill is not destructive so the cap-at-3 rule does not apply.

4 / 5

Progressive Disclosure

The body is under 50 lines (~11 lines), no bundle files exist (references/scripts/assets absent), no external files are referenced, and sections are well-organized bullets, so the simple-skill exception in the rubric scores this 5.

5 / 5

Total

17

/

20

Passed

Description

61%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 and well-keyworded with concrete input formats and a clear output, but it omits any 'Use when...' trigger guidance, which caps completeness and limits distinctiveness.

Suggestions

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

Broaden trigger terms with synonyms/extensions users say ('spreadsheets', '.xlsx', 'charts', 'dashboard') to raise trigger-term coverage.

Mention the concrete sub-actions (KPI cards, charts, data tables) to lift specificity from a single verb to comprehensive coverage.

DimensionReasoningScore

Specificity

Quotes 'Turns CSV, Excel, or JSON data into a polished visual report page' — it names the input domain (CSV/Excel/JSON) and a single concrete output action, but lists only one verb so it is not comprehensive; anchor 3 ('names domain and 1-2 concrete actions') fits better than 4 ('several specific actions').

3 / 5

Completeness

Has a clear 'what' ('Turns ... data into a polished visual report page') but no 'Use when...' or equivalent trigger guidance, so per the rubric cap completeness at 3; not 4 because 'when' is entirely missing rather than weakly implied.

3 / 5

Trigger Term Quality

Includes natural format keywords users say — 'CSV', 'Excel', 'JSON' — plus 'data' and 'visual report page', giving good keyword coverage matching anchor 4; not a 5 because synonyms/extensions like 'spreadsheet', '.xlsx', or 'charts' are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (data → visual report) with concrete format triggers, making it mostly distinct with only minor overlap risk against general charting skills; not 5 because the lack of explicit trigger phrases leaves some ambiguity.

4 / 5

Total

14

/

20

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.