CtrlK
BlogDocsLog inGet started
Tessl Logo

kpi-reporting

Prepare KPI readouts, scorecards, WBR/MBR/QBR updates, and executive summaries from quantitative business or product metrics; use when the task is to report status, compare against targets, explain validated drivers, and state operating implications.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-structured, actionable workflow skill with a clear 9-step sequence and explicit validation feedback loops. Its main weakness is density: most procedural detail is inline in SKILL.md and the prose could be tightened, leaving progressive disclosure and conciseness as the lower dimensions.

Suggestions

Move the detailed Metric/Status/Driver/Presentation Standards into a references file (e.g., references/reporting-standards.md) and keep SKILL.md as a lean overview that links to it, improving progressive disclosure.

Trim overlapping framing between the intro, the "Skill Configuration" guardrails, and the Standards sections to reduce repetition and tighten conciseness.

Consolidate the inline reference-pointing instructions (e.g., the handoff checklist and template-loading guidance) so each external reference is introduced once and clearly.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but at ~140 lines of dense procedural guidance some passages repeat or could be tightened (e.g., overlapping framing in the intro and Standards sections).

2 / 3

Actionability

Though instruction-only, it gives concrete executable guidance: named skill handoffs ($metric-diagnostics, $build-report, $validate-data), specific data lanes (~~structured_data, ~~company_docs), and exact formatting like `123k (+8% w/w, +19% m/m)`.

3 / 3

Workflow Clarity

A clearly sequenced 9-step workflow with explicit validation checkpoints ("Lock Metric Definitions And Sources" via $analyze-data-quality, step 8 "Validate The Readout" via $validate-data) and feedback loops that resolve material issues before handoff.

3 / 3

Progressive Disclosure

Sections are well-organized and the single reference (report-templates.md) is clearly signaled and one level deep, but the bulk of detailed procedural and Standards guidance lives inline in SKILL.md rather than being split across reference files.

2 / 3

Total

10

/

12

Passed

Description

100%

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 concise, third-person description that names concrete deliverables and pairs them with an explicit "use when" trigger clause covering both what and when. It is specific, natural-sounding, and clearly distinguishable from neighboring analytics skills.

DimensionReasoningScore

Specificity

The description enumerates concrete actions — "Prepare KPI readouts, scorecards, WBR/MBR/QBR updates, and executive summaries" — listing multiple specific deliverables rather than vague language.

3 / 3

Completeness

It explicitly answers both what it does and when to use it via the "use when the task is to report status, compare against targets, explain validated drivers, and state operating implications" clause.

3 / 3

Trigger Term Quality

It surfaces natural terms a user would say ("KPI readouts", "scorecards", "WBR/MBR/QBR", "executive summaries", "report status", "compare against targets") with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The KPI-reporting niche is clearly bounded with distinct triggers (WBR/MBR/QBR, scorecards, validated drivers), making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.