# Gather Business Context

Gather business context from connected or provided sources so downstream analysis...

- Repository: https://github.com/XiaomiMiMo/MiMo-Code (13741 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add XiaomiMiMo/MiMo-Code --skill gather-business-context -g -a claude-code -y`
Codex: `npx skills add XiaomiMiMo/MiMo-Code --skill gather-business-context -g -a codex -y`
Cursor: `npx skills add XiaomiMiMo/MiMo-Code --skill gather-business-context -g -a cursor -y`
Gemini CLI: `npx skills add XiaomiMiMo/MiMo-Code --skill gather-business-context -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Boundary

Use this skill to gather framing context, not to complete the downstream analysis.

If the same request also asks for a diagnosis, recommendation, dashboard, report, or other analytical deliverable, return only the context needed for that next step and continue with the appropriate focused skill, such as $metric-diagnostics, $product-business-analysis, $build-dashboard, or $build-report.

# Gather Business Context

Use this skill to collect the business context needed to understand an analytical question before doing deeper work. Focus on what the topic is, why it matters, what changed or is being decided, who or what source is closest to the work, and which definitions or artifacts should frame the analysis. This is a retrieval and extraction skill: gather enough context to set up the next step, not a final report, root-cause analysis, or broad background scan. Skip it when the prompt already provides the needed context or the task is fully self-contained.

## Workflow

### 1. Identify The Retrieval Target

Establish the analytical topic that needs context and why it matters for the next step. Capture the boundary needed to search and interpret sources, such as the relevant product area, audience, time period, or decision. If the timeframe is missing, use the narrowest reasonable window implied by the task and label it as an assumption.

### 2. Build Search Anchors

Search with concrete identifiers rather than broad topic guesses. Start with the names the user provided or the sources surfaced, then expand with adjacent terms that help recall, such as aliases, owners, teams, dates, source names, related entities, or entities found in earlier results.

The rest: https://github.com/XiaomiMiMo/MiMo-Code/blob/HEAD/packages/cli/src/skill/builtin/.bundle/data-analytics/workflows/gather-business-context/SKILL.md