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.

67

Quality

80%

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

100%

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 tight, well-structured instruction-only workflow: lean prose, concrete checklists and a structure template, a clearly sequenced build process with explicit QA validation, and appropriately scoped one-level references. It is a strong example of an analytical-report skill body.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains concepts Claude already knows and every section earns its place (e.g. the React/Recharts guardrail and the QA checklist are load-bearing), matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Although instruction-only with no code, the guidance is concrete and specific: an 8-step build list that names exactly what to keep explicit ('metric definitions, grain, time range, filters, units, exclusions, and source freshness'), a copy-paste markdown structure template, and a detailed QA checklist — meeting the instruction-only 'concrete, specific guidance' bar.

3 / 3

Workflow Clarity

A clearly sequenced 8-step build process is followed by a dedicated 'QA and handoff' section with explicit validation checkpoints ('Recalculate headline values', 'Check that every claim is supported') and fix actions for found issues, matching 'clear sequence with explicit validation steps' and a feedback loop.

3 / 3

Progressive Disclosure

Content is well-organized into clear sections and the only external pointer is a clearly signaled one-level reference ('Read ../visualize-data/SKILL.md when creating charts'); for a sub-60-line skill with no needed bundle, the simple-skills note allows a top score on well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

60%

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 action-rich but omits any explicit 'when to use' trigger guidance and uses a single, somewhat formal phrasing, limiting trigger quality and completeness. Adding a 'Use when...' clause with natural user variations would lift it into the top tier.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user needs a durable analytical report rather than a quick inline answer, or asks for findings, recommendations, or a written report.'

Include natural term variations users actually say (report, analysis report, memo, brief, dashboard narrative) alongside 'analytical report'.

Sharpen distinctiveness by contrasting the trigger with sibling skills (e.g. analysis workflows vs. this report-structuring skill).

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Build a durable analytical report', 'answer-first narrative', 'evidence-backed findings', 'charts or tables', 'caveats', 'recommendations', and 'source context'), matching the 'lists multiple specific concrete actions' anchor rather than the partial-coverage level 2.

3 / 3

Completeness

It clearly answers 'what' (build a report with the listed components) but lacks any 'Use when...' clause or equivalent trigger guidance, so per the guidelines completeness is capped at 2 ('has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

Natural terms like 'analytical report', 'charts', 'tables', and 'findings' appear, but the phrasing is singular and slightly formal, missing common variations (e.g. 'report', 'analysis', 'memo', 'brief') and explicit trigger keywords — the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

'Build a durable analytical report' is a recognizable niche, but the domain overlaps with sibling analysis and data-visualization skills (the body even points to ../visualize-data), so it 'could still overlap with similar skills' rather than having fully distinct triggers.

2 / 3

Total

9

/

12

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.