gather-business-context

Gather business context from connected or provided sources so downstream analysis starts with the right framing. Use when an analytical question depends on missing context, such as what a metric means, what changed recently, or which sources should be checked. If the same prompt asks for diagnosis, recommendation, or a deliverable, gather context first and continue to the focused skill.

Quality

92%

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

85%

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

The content is a well-sequenced, actionable instruction-only workflow with clear organization and no misplaced bundle references. Its main weakness is verbosity and repetition of the skill boundary across multiple sections.

Suggestions

Collapse the repeated boundary statements (intro paragraph, ## Boundary, and the restatements inside steps 4 and 8) into a single statement to reduce token overhead.

Tighten the multi-clause sentences in the Standards section into shorter, declarative rules to improve scannability.

Consider trimming step 2's search-anchor guidance, which elaborates the same narrow-vs-broad idea twice; a single concrete example would suffice.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but is verbose and restates the boundary (gather-context-not-analysis) across the intro, the Boundary section, and several steps; it could be tightened without losing clarity.	2 / 3
Actionability	As an instruction-only skill it provides concrete decision rules (build search anchors from names/aliases/owners, prefer newest decision artifacts over older plans, owner-written over third-party summaries) rather than vague direction.	3 / 3
Workflow Clarity	An explicit 8-step workflow is clearly sequenced, with checkpoints such as revising anchors when sources come back thin and explicit stop criteria in step 7; it is not a destructive/batch operation that would require a validate-fix-retry loop.	3 / 3
Progressive Disclosure	No bundle files exist, so the single SKILL.md is appropriately self-contained with well-organized sections (Workflow steps, Standards) and clear navigation, requiring no external references.	3 / 3
	Total	11 / 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.

The description is specific, third-person, and explicitly covers both what the skill does and when to use it with natural trigger terms. It cleanly distinguishes itself from downstream analysis skills.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ("Gather business context from connected or provided sources", "gather context first and continue to the focused skill") and enumerates specific context types (metric meaning, recent changes, sources to check).	3 / 3
Completeness	Explicitly answers both what (gather framing context from sources) and when ("Use when an analytical question depends on missing context") with explicit trigger guidance, so it is not capped at 2.	3 / 3
Trigger Term Quality	Includes natural phrases a user would say ("analytical question", "what a metric means", "what changed recently", "diagnosis, recommendation, or a deliverable") with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Clear niche as a retrieval/extraction skill that explicitly defers diagnosis, recommendation, and deliverables to focused skills, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 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/gather-business-context/SKILL.md
Commit: ff87d47

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