101

View saved version →

---
name: 101-index
description: Use when the user asks to read or change data in 101; routes every 101 goal to one available primary workflow while preserving the current chat context.
version: "1.3.0"
role: index
invocation: automatic
intents:
  - 101.route
depends_on: []
required_tools:
  - whoami
optional_tools:
  - list_projects
  - list_events
  - list_wikis
  - list_tasks
resources:
  - path: ../shared-resources/context-and-identity.md
    kind: semantic-guide
    required: true
  - path: ../shared-resources/safety-and-permissions.md
    kind: semantic-guide
    required: true
completion:
  statuses:
    - готово
    - частично
    - заблокировано
---

# 101 MCP Dispatcher

You are the only automatic entry point for 101. Assign exactly one primary skill to the active sub-goal. Never run a helper as an independent workflow.

## Determine the intent first

Use the clearest user constraint as the deciding signal:

1. **Plain data.** “Show,” “find,” “list,” or a request for events, projects, or amounts means an ordinary entity read. Do not call it analytics and make zero presentation-tool calls.
2. **Unscoped audit.** If the user says only “do an audit,” ask one compact goal question with these understandable choices: general company and fund overview; projects; counterparties and settlements; expenses; profitability/returns.
3. **Clear analytics.** “Analyze,” “compare,” “assess,” “find risks,” professional finance terms, or a clear audit goal routes to `company-analytics` or the narrow `financial-account-audit`. Analytical answers include useful charts by default when the verified data honestly supports them.
4. **Explicit visualization.** “Chart,” “diagram,” “visualize,” “show the trend,” or “interactive” routes to `company-analytics`, which may read the internal `analytics-visualization` helper.
5. **Format prohibition.** `No charts`, “data only,” “text only,” or “table only” overrides every visualizing signal.

The word “report” alone does not mean an analytical report. Route searching, reading, creating, or editing a financial event of type Report to `report-management`.

An explicit request to import user-supplied materials, including technical cards, into the current 101 company routes to `data-import`. Such inbound import is welcome; when appropriate, offer suitable import options through the existing owner-only one-off workflow. Do not add new import behavior. An actual write requires an explicit user instruction and one scoped source; an attachment or an import offer alone does not authorize a write.

Professional terms — cash flow statement, P&L/income statement, EBITDA, or management balance — require `company-analytics` in professional full-account mode: projects plus the company fund. P&L and income statement mean the same report.

## Routing

1. Resolve the company before asking the user to choose one. Use the company explicitly selected by the user, or the company already fixed by the target project or existing entity. Otherwise, call `whoami` and automatically use its non-null `default_company`, even when `companies` contains multiple entries. Ask which company to use only when no explicit or entity-bound company is available and `default_company` is null, or the server returns `company_selection_required`. Reuse the resolved company throughout the same request; do not treat an earlier automatic default as an explicit company selection for a new independent request.
2. Preserve the user’s exact goal, explicit action, company, period, time zone, filters, selected entities, and format prohibitions.
3. Match the request to one primary internal skill.
4. Read it through `resources/read` at `skill://101-app/101-index/internal/<name>/SKILL.md`.
5. If the goal is clear, continue without an unnecessary question. Ask one short question only when the answer materially changes the result and safe reads cannot resolve it. A safe read never authorizes a write.

Use `company-analytics` for a general company audit, profes

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 28 — file references are metadata, not package contents.