product-business-analysis

Analyze product or business data to support a decision or recommendation. Use when a decision depends on metric-backed evidence, such as choosing a direction, prioritizing an opportunity, evaluating a change, segmenting users, sizing tradeoffs, or deciding what to do next.

Quality

85%

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

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-sequenced, actionable analytical workflow with strong validation checkpoints; the main gaps are some repeat-padded prose and a monolithic single-file structure with no progressive disclosure.

Suggestions

Consolidate the repeated 'avoid broad exploration' guidance into a single workflow-level note instead of restating it in steps 1, 2, 3, and 4.

Move the full decision-lenses catalog (Current scale, Momentum, Breadth, ...) into a references file (e.g., references/decision-lenses.md) and link to it from step 5 to reduce inline bulk.

Extract the detailed source-discovery and source-access guardrails into a references file, keeping SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not explain concepts Claude already knows, but the repeated 'do not turn into broad exploration' messaging across steps 1-4 and some restated guardrails could be tightened, matching the mostly-efficient-but-could-tighten anchor.	2 / 3
Actionability	As an instruction-only skill it gives concrete, specific guidance throughout: explicit 'State plainly' checklists, a named set of decision lenses, defined handoff conditions, and pointed sub-skill calls ($gather-business-context, $validate-data, $build-report).	3 / 3
Workflow Clarity	A clearly sequenced six-step workflow with explicit validation checkpoints ($validate-data before stakeholder-facing claims, reconcile dashboards vs. queries) and a stop-and-ask source-access guardrail, plus checklists for the framing and lenses steps.	3 / 3
Progressive Disclosure	The skill is a single ~130-line monolithic file with no bundle files in references/scripts/assets; sections are well-organized, but content that could be split out (the full lenses catalog, detailed source guardrails) is inline rather than one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

92%

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 strong description with explicit what/when triggers, natural keyword coverage, and concrete actions; the main weakness is overlap risk with several related business-analysis skills.

Suggestions

Add a one-clause distinction from $metric-diagnostics (e.g., 'Use $metric-diagnostics instead when the question is explaining a specific metric movement or anomaly') to reduce trigger overlap.

Tighten 'metric-backed evidence,' which reads as internal jargon, toward phrasing a user would actually say.

Dimension	Reasoning	Score
Specificity	The description names the core action ("Analyze product or business data to support a decision or recommendation") and lists multiple concrete analytical actions such as "segmenting users" and "sizing tradeoffs," matching the multiple-specific-actions anchor.	3 / 3
Completeness	It explicitly answers what ("Analyze product or business data to support a decision or recommendation") and when ("Use when a decision depends on metric-backed evidence, such as..."), satisfying the explicit what-and-when anchor.	3 / 3
Trigger Term Quality	The "Use when" clause gives natural business phrasing users would say ("choosing a direction, prioritizing an opportunity, evaluating a change, segmenting users, sizing tradeoffs, or deciding what to do next"), giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	The decision-support framing is a clear niche, but "product or business data" analysis overlaps with a cluster of related skills ($metric-diagnostics, $gather-business-context, $design-kpis), so it could still trigger for a neighboring skill.	2 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/data-analytics/workflows/product-business-analysis/SKILL.md
Commit: ff87d47

Reviewed: about 14 hours 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.