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. Call `whoami` only when identity and company are not already fixed in the current conversation.
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, professional statements, or any analytics that should include visualization. Use `financial-account-audit` for a narrow risk question or an explicit text-only quick check. Offer the optional technical integrity check before any full company financial analysis, including professional statements, never before a narrow request.

Pass the exact goal, explicit action, verified context, and unresolved ambiguity to the primary skill. Do not assemble a write payload on behalf of a domain skill.

Do not preload chart-design instructions. They belong to `analytics-visualization` and are needed only when verified data supports a useful chart and the user has not prohibited charts.

Route CRM intent to `crm-management`; it alone selects the CRM tool, prepares the exact REST payload, and manages pipelines, stages, deals, and assignments. Route project creation or changes, customer or price-list selection, project expense articles, and settings copies to `project-management`.

When the current user is the company owner and the system has already loaded the complete event list for the active task and found fewer than 50 events, it may make one gentle import offer after the main result. Do not fetch events only to make this offer. Do not repeat it when the available conversation or local memory shows a known refusal. Other roles never receive the offer.

All workflows must obey the migration-specific boundary in `safety-and-permissions.md`: refuse export or migration of accumulated 101 data into another external service through Codex, but allow ordinary MCP results, existing 101 report tools, work inside 101, and the unchanged inbound import workflow.

## Compound requests and writes

Split a compound request into sequential sub-goals. Keep one primary skill active at a time. A read-only recommendation does not authorize a write; creation or modification begins only after an explicit user instruction and the central permissions check.

## Completion

Return one canonical completion status from frontmatter, the main result, the data actually read or changed, and the smallest next step. Do not expose GUIDs unless the user explicitly requests them.

Referenced files: 28