index

Route broad Data Analytics requests to the appropriate quantitative analysis, visualization, dashboard, report, notebook, KPI, market-sizing, validation, or semantic-layer workflow.

Quality

74%

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 ./packages/opencode/src/skill/builtin/.bundle/data-analytics/workflows/index/SKILL.md

Quality

Content

82%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.

A well-built router skill body: lean, highly actionable routing rules with an explicit ordering and validation steps, and one-level-deep references organized for discovery. The main defect is bundle integrity — the referenced demo asset file is missing.

Suggestions

Create assets/demo-product-growth.csv (or remove the reference) so the 'Offer assets/demo-product-growth.csv' instruction in Source access points to a real file.

State an explicit verify-before-proceeding checkpoint for the combined-workflow ordering (e.g. confirm source quality and metric definitions are validated before step 3) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	A lean ~50-line router where every line earns its place: per-condition routes, a five-step ordering, source-access fallbacks, and output-format constraints. No padding and no explanation of concepts Claude already knows.	5 / 5
Actionability	Concrete, immediately executable routing rules ('Metric changed, missed a target...: read `../metric-diagnostics/SKILL.md`') with explicit fallback behaviors (smallest useful artifact, never invent records). The one gap: the body offers 'assets/demo-product-growth.csv' but no assets directory exists in the bundle, so that instruction cannot be executed as written.	4 / 5
Workflow Clarity	The numbered ordering embeds validation steps ('2. Validate source quality and metric definitions', '4. Validate conclusions') and a conflict-feedback path ('surface the conflict and use the data-quality workflow'). Detailed verify-before-proceed checkpoints are delegated to sub-skills rather than stated here, so it does not reach 5.	4 / 5
Progressive Disclosure	Exemplary index structure: clearly signaled, one-level-deep references to sibling skills, each keyed to a trigger condition. Scored against the actual bundle structure, however, the referenced assets/demo-product-growth.csv does not exist (no assets/ directory), a broken referenced path that keeps it below 5.	4 / 5
	Total	17 / 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.

A clear, well-scoped router description with strong keyword coverage and a distinct analytics niche, weakened only by the absence of an explicit 'Use when...' trigger clause. Adding one sentence of trigger guidance would lift it to the top anchor level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a request involves metrics, KPIs, dashboards, charts, or an evidence-backed business decision and no single focused workflow obviously applies.'

Include the missing natural trigger terms such as 'chart', 'metric', and 'data quality' so the description matches phrases users actually say.

Mention the data-quality and business-context routing destinations so description coverage matches the 13 routes the body actually dispatches to.

Dimension	Reasoning	Score
Specificity	One concrete action ('Route broad Data Analytics requests to the appropriate... workflow') plus a broad enumeration of destination types (quantitative analysis, visualization, dashboard, report, notebook, KPI, market-sizing, validation, semantic-layer). Minor coverage gaps versus the 13 routes in the body (data quality and business-context gathering are unnamed), so it does not reach 5.	4 / 5
Completeness	The 'what' is clear (route analytics requests to focused workflows), but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'when' is only weakly implied by 'broad Data Analytics requests'. Per judging guidelines, a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains good natural keywords users would say ('dashboard', 'KPI', 'report', 'notebook', 'market-sizing', 'semantic-layer', 'visualization'). A few common variations are missing ('chart', 'metric', 'data quality'), which keeps it below 5 but clearly above anchor 3.	4 / 5
Distinctiveness Conflict Risk	Distinctive niche terms (semantic-layer, market-sizing, KPI) set it apart from non-analytics skills, and its dispatcher role is explicit. It still overlaps with the child analytics skills it routes to (by design), so it does not reach 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/data-analytics/workflows/index/SKILL.md
Commit: f0293bf

Reviewed: 2 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.