CtrlK
BlogDocsLog inGet started
Tessl Logo

build-report

Build a durable analytical report with an answer-first narrative, evidence-backed findings, charts or tables, caveats, recommendations, and source context.

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./packages/opencode/src/skill/builtin/.bundle/data-analytics/workflows/build-report/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an efficient, well-structured instruction-only skill with a concrete report template, explicit constraints, and a QA checklist. It scores consistently at 4 across dimensions, with headroom toward 5 via tighter prose and a clearer validate-fix-retry QA loop.

Suggestions

Tighten the format-selection section and step 1 to reduce phrasing that restates the obvious, pushing conciseness toward 5.

Add an explicit validate-fix-retry loop in the QA section (e.g., "if a chart does not match its source data, fix it and re-check") to lift workflow_clarity.

Since the skill is instruction-only and references one sibling skill, confirm that reference path resolves and consider noting when to consult it earlier in the workflow.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding of concepts Claude already knows; a few phrasings (e.g., the format-selection rationale) could be tightened slightly.

4 / 5

Actionability

Concrete guidance is present: a ready-to-adapt markdown structure, explicit tool constraints ("Do not install or require React, Recharts, Vite..."), and a specific QA checklist, though as an instruction-only skill it lacks copy-paste commands.

4 / 5

Workflow Clarity

An explicit 8-step "Build the report" sequence is followed by a QA-and-handoff checklist with validation steps ("Recalculate headline values", "Check that every claim is supported"); report writing is not destructive, so no cap applies, but checkpoints are guidance-level rather than validate-fix-retry loops.

4 / 5

Progressive Disclosure

Sections are clearly organized and the one external reference ("../visualize-data/SKILL.md") is one level deep and well-signaled; at ~60 lines it slightly exceeds the under-50-line simple-skill exception, so it sits at 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

66%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 concrete and third-person with good trigger terms and a clear niche, but it lacks an explicit "Use when..." trigger clause, which caps completeness at 3. Adding trigger guidance would lift the score noticeably.

Suggestions

Append an explicit "Use when..." clause naming the situations that call for a durable report (e.g., when the user needs a deliverable, a written analysis, or a handoff artifact rather than a chat answer).

Add natural trigger synonyms like "write up", "report", or "deliverable" to broaden keyword coverage.

Consider phrasing the components as actions ("structure an answer-first narrative", "place evidence-backed findings") to strengthen specificity toward 5.

DimensionReasoningScore

Specificity

Names several concrete report components ("answer-first narrative, evidence-backed findings, charts or tables, caveats, recommendations, and source context") rather than vague language, though they describe report parts more than distinct actions.

4 / 5

Completeness

Has a clear "what" (build a durable analytical report with listed elements) but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ("analytical report", "findings", "recommendations", "caveats", "charts or tables"), but is missing common synonyms and a "report"-style phrasing variation.

4 / 5

Distinctiveness Conflict Risk

"Build a durable analytical report" carves a distinct report-building niche with minimal conflict risk, though it has minor overlap with general analysis or writing skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
XiaomiMiMo/MiMo-Code
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.