← 101CONTENT HISTORY

Update to 101

Snapshot Nov 9, 2026 · 00:21 UTC · version 2.0.5

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for 101-index

Full description — Now says: Use for requests about 101 data and features when the action and primary workflow need to be identified.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save 101 and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Nov 7, 2026 · 18:09 UTC

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.

After

Nov 9, 2026 · 00:21 UTC

Use for requests about 101 data and features when the action and primary workflow need to be identified.

Skill instructions

Before

Nov 7, 2026 · 18:09 UTC

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.4.0" # 101 MCP Dispatcher You are the only automatic entry point for 101. As...

After

Nov 9, 2026 · 00:21 UTC

for requests about 101 data and features when the action and primary workflow need to be identified. version: "1.5.0" - get_current_screen - open_app_screen - resolve_screen_offer - show_result # 101 Dispatcher A sub-goal has one...

Supporting files

Before

Nov 7, 2026 · 18:09 UTC

[{"relative_path":"internal/analytics-visualization/SKILL.md","size_in_bytes":3696},{"relative_path":"internal/company-analytics/SKILL.md","size_in_bytes":8866},{"relative_path":"internal/crm-management/SKILL.md","size_in_bytes":4639},{"...

After

Nov 9, 2026 · 00:21 UTC

[]

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,7 +1,7 @@
 ---
 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.4.0"
+description: Use for requests about 101 data and features when the action and primary workflow need to be identified.
+version: "1.5.0"
 role: index
 invocation: automatic
 intents:
@@ -14,6 +14,10 @@
   - list_events
   - list_wikis
   - list_tasks
+  - get_current_screen
+  - open_app_screen
+  - resolve_screen_offer
+  - show_result
 resources:
   - path: ../shared-resources/context-and-identity.md
     kind: semantic-guide
@@ -28,52 +32,58 @@
     - заблокировано
 ---
 
-# 101 MCP Dispatcher
+# 101 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.
+A sub-goal has one owner. Route a domain operation to one primary workflow from the table. Handle simple reads without a separate workflow and navigation here using available commands and `entity-resolution`; a helper does not become the goal owner. Execute compound requests sequentially.
 
-## Determine the intent first
+## Context
 
-Use the clearest user constraint as the deciding signal:
+Begin the first request with the standard `whoami` in MCP. Use its result to determine the available companies.
 
-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.
+1. Identify the action, object, constraints and response format. If different meanings lead to different workflows, first ask a short clarifying question under the [shared rule](../shared-resources/context-and-identity.md). Preserve the company, project, period, time zone, filters and decisions already made.
+2. If the operation requires a company: explicit selection or the target entity's company → non-null `whoami.default_company` → a question to the user. Multiple companies with a non-null `default_company` do not require a question. Ask for a company on `company_selection_required`. When the absence of companies is confirmed, continue the original goal through company creation or waiting for an invitation under the shared rule; route creation to `company-creation`. `default_company=null` alone does not mean that there are no companies.
+3. Resolve the company again for an independent new request; preserve it within a request until the context changes.
+4. Select the workflow from the table. Load only an actually available instruction through `resources/read`; the published internal workflow address is `skill://101-app/101-index/internal/<name>/SKILL.md`. If a workflow is unavailable, state the gap; do not invent a missing command.
+5. Pass the goal, explicit action, verified entities and clarification answers. The domain workflow clarifies only remaining material parameters and prepares the write; it does not repeat resolved questions.
 
-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`.
+## Action and Result Format
 
-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.
+- **Reading:** a list, search or specific amount. Obtain data with the relevant commands. To show records, use `show_result` when the command is available and `structuredContent.presentation.token` was returned; otherwise reply in available text. Reading does not itself require analytics or a chart.
+- **App screen:** handle an explicit request to open a 101 screen through `open_app_screen` with `mode=immediate`. Take the target from verified data and the screen from the current tool schema. Only `navigationStatus=opened` confirms success. For an object card, resolve an offered transition (`mode=offer`) through `resolve_screen_offer` after the user's answer. Offer lists in words and open them after agreement: the current `mode=offer` for a list may open it immediately. Obtain current-screen context through `get_current_screen` when the request needs it.
+- **Analytics:** comparison, trend, assessment or audit. Charts are allowed with verified data. “Text only,” “table only” and “no charts” constrain the result format.
+- **Changes to business records:** explicit creation, modification or deletion. Follow server permissions and standard confirmation; reading, a recommendation and an attachment do not themselves authorize business-data changes. Personal memory and uploads have their own rules.
 
-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.
+Handle an independent request to upload a supplied file here through `file-handling`: you remain the goal owner. An upload does not require association with a Wiki page, event or company; the shared rule for continuing the goal still applies. Place it somewhere only for a separate placement goal.
 
-## Routing
+Route a Gantt request to the native 101 plan: ordinary tasks to `task-management`, estimate positions to `estimate-management`, and expense-report positions to `report-management`. Do not offer a separate diagram in chat instead of this path.
 
-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.
+## Owners of Domain Requests
 
-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.
+| Goal | Instruction |
+| --- | --- |
+| Create a company | [company-creation/SKILL.md](../company-creation/SKILL.md) |
+| Read, create or change projects and expense categories | [project-management/SKILL.md](../project-management/SKILL.md) |
+| Tasks, comments and bulk actions | [task-management/SKILL.md](../task-management/SKILL.md) |
+| CRM pipelines, stages, deals and distribution | [crm-management/SKILL.md](../crm-management/SKILL.md) |
+| Wiki, blocks, publication and permissions | [wiki-management/SKILL.md](../wiki-management/SKILL.md) |
+| Estimates and positions | [estimate-management/SKILL.md](../estimate-management/SKILL.md) |
+| Expense events of type “Report” | [report-management/SKILL.md](../report-management/SKILL.md) |
+| Income, including commission and company-fund income | [income-management/SKILL.md](../income-management/SKILL.md) |
+| Transfers and settlements | [settlements-and-transfers/SKILL.md](../settlements-and-transfers/SKILL.md) |
+| Price lists, categories, positions and prices | [price-list-management/SKILL.md](../price-list-management/SKILL.md) |
+| Invite an existing user | [contractor-invitations/SKILL.md](../contractor-invitations/SKILL.md) |
+| One-off import of an external source | [data-import/SKILL.md](../data-import/SKILL.md) |
+| A standard PDF/XLSX document | [document-generation/SKILL.md](../document-generation/SKILL.md) |
+| Durable personal memory: remember/forget | [user-memory-management/SKILL.md](../user-memory-management/SKILL.md) |
+| App features and company procedures | [product-support/SKILL.md](../product-support/SKILL.md) |
+| General audit, analytics, cash flow statement, P&L/income statement, EBITDA | [company-analytics/SKILL.md](../company-analytics/SKILL.md) |
+| A narrow financial risk or quick text check | [financial-account-audit/SKILL.md](../financial-account-audit/SKILL.md) |
+| One displayed amount, `financial_kpi_context_data_v1` | [financial-kpi-explanation/SKILL.md](../financial-kpi-explanation/SKILL.md) |
 
-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.
+The word “report” alone does not authorize an expense creation. A general audit and a document for an event are different goals. “Interactive” does not mean analytics when the user requests a task card.
 
-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.
+Only “do an audit” → “Check the whole company, one project or a specific issue?” Pass the known goal and decision about the optional technical check to `company-analytics` without asking again. A narrow check does not require it. Load analytics presentation instructions (`analytics-visualization`) only when the format needs them.
 
-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`.
+After the main result, you may offer an import once to the owner if the complete event list has already been obtained and contains fewer than 50 events. Do not load the list for the offer; do not repeat a known refusal.
 
-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.
-
-For a new project with an estimate, follow project-management first. Resolve and verify the customer assignment, then pass the verified project and agreed positions and prices to estimate-management.
-
-## 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.
+Follow the shared `safety-and-permissions.md` policy, including the external data-migration boundary. Finish with a status from frontmatter, the verified result and material limitations. Show GUIDs only on explicit request.
Full technical diff · 3 changed fields

changed /description

BEFORE
"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."
AFTER
"Use for requests about 101 data and features when the action and primary workflow need to be identified."

changed /included_files

BEFORE
[
  {
    "relative_path": "internal/analytics-visualization/SKILL.md",
    "size_in_bytes": 3696
  },
  {
    "relative_path": "internal/company-analytics/SKILL.md",
    "size_in_bytes": 8866
  },
  {
    "relative_path": "internal/crm-management/SKILL.md",
    "size_in_bytes": 4639
  },
  {
    "relative_path": "internal/data-import/SKILL.md",
    "size_in_bytes": 4653
  },
  {
    "relative_path": "internal/entity-resolution/SKILL.md",
    "size_in_bytes": 2154
  },
  {
    "relative_path": "internal/estimate-management/SKILL.md",
    "size_in_bytes": 3490
  },
  {
    "relative_path": "internal/event-positions/SKILL.md",
    "size_in_bytes": 2258
  },
  {
    "relative_path": "internal/file-handling/SKILL.md",
    "size_in_bytes": 4190
  },
  {
    "relative_path": "internal/financial-account-audit/SKILL.md",
    "size_in_bytes": 6926
  },
  {
    "relative_path": "internal/project-management/SKILL.md",
    "size_in_bytes": 3713
  },
  {
    "relative_path": "internal/report-management/SKILL.md",
    "size_in_bytes": 3574
  },
  {
    "relative_path": "internal/settlements-and-transfers/SKILL.md",
    "size_in_bytes": 4183
  },
  {
    "relative_path": "internal/wiki-management/SKILL.md",
    "size_in_bytes": 3954
  },
  {
    "relative_path": "internal/write-preflight/SKILL.md",
    "size_in_bytes": 3186
  },
  {
    "relative_path": "resources/analytics-visualization/references/artifact-payload-example.json",
    "size_in_bytes": 2676
  },
  {
    "relative_path": "resources/analytics-visualization/references/chart-design.md",
    "size_in_bytes": 7549
  },
  {
    "relative_path": "resources/analytics-visualization/references/chart-payload-example.json",
    "size_in_bytes": 1378
  },
  {
    "relative_path": "resources/analytics-visualization/references/chart-token-snapshot-1.0.154.json",
    "size_in_bytes": 1815
  },
  {
    "relative_path": "resources/crm-management/references/crm-orchestration.md",
    "size_in_bytes": 11013
  },
  {
    "relative_path": "resources/shared-resources/context-and-identity.md",
    "size_in_bytes": 2006
  },
  {
    "relative_path": "resources/shared-resources/data-import-rules.md",
    "size_in_bytes": 6315
  },
  {
    "relative_path": "resources/shared-resources/events-and-positions.md",
    "size_in_bytes": 5199
  },
  {
    "relative_path": "resources/shared-resources/finance-and-balances.md",
    "size_in_bytes": 1931
  },
  {
    "relative_path": "resources/shared-resources/financial-risks-and-project-controls.md",
    "size_in_bytes": 2614
  },
  {
    "relative_path": "resources/shared-resources/management-reporting-and-balances.md",
    "size_in_bytes": 5719
  },
  {
    "relative_path": "resources/shared-resources/safety-and-permissions.md",
    "size_in_bytes": 1876
  },
  {
    "relative_path": "resources/shared-resources/technical-integrity-audit.md",
    "size_in_bytes": 2787
  },
  {
    "relative_path": "resources/shared-resources/wiki-content-and-files.md",
    "size_in_bytes": 1877
  }
]
AFTER
[]

changed /skill_md_contents

BEFORE
"---\nname: 101-index\ndescription: 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.\nversion: \"1.4.0\"\nrole: index\ninvocation: automatic\nintents:\n  - 101.route\ndepends_on: []\nrequired_tools:\n  - whoami\noptional_tools:\n  - list_projects\n  - list_events\n  - list_wikis\n  - list_tasks\nresources:\n  - path: ../shared-resources/context-and-identity.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/safety-and-permissions.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# 101 MCP Dispatcher\n\nYou 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.\n\n## Determine the intent first\n\nUse the clearest user constraint as the deciding signal:\n\n1. **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.\n2. **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.\n3. **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.\n4. **Explicit visualization.** “Chart,” “diagram,” “visualize,” “show the trend,” or “interactive” routes to `company-analytics`, which may read the internal `analytics-visualization` helper.\n5. **Format prohibition.** `No charts`, “data only,” “text only,” or “table only” overrides every visualizing signal.\n\nThe word “report” alone does not mean an analytical report. Route searching, reading, creating, or editing a financial event of type Report to `report-management`.\n\nAn 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.\n\nProfessional 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.\n\n## Routing\n\n1. 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.\n2. Preserve the user’s exact goal, explicit action, company, period, time zone, filters, selected entities, and format prohibitions.\n3. Match the request to one primary internal skill.\n4. Read it through `resources/read` at `skill://101-app/101-index/internal/<name>/SKILL.md`.\n5. 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.\n\nUse `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.\n\nPass 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.\n\nDo 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.\n\nRoute 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`.\n\nWhen 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.\n\nAll 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.\n\nFor a new project with an estimate, follow project-management first. Resolve and verify the customer assignment, then pass the verified project and agreed positions and prices to estimate-management.\n\n## Compound requests and writes\n\nSplit 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.\n\n## Completion\n\nReturn 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.\n"
AFTER
"---\nname: 101-index\ndescription: Use for requests about 101 data and features when the action and primary workflow need to be identified.\nversion: \"1.5.0\"\nrole: index\ninvocation: automatic\nintents:\n  - 101.route\ndepends_on: []\nrequired_tools:\n  - whoami\noptional_tools:\n  - list_projects\n  - list_events\n  - list_wikis\n  - list_tasks\n  - get_current_screen\n  - open_app_screen\n  - resolve_screen_offer\n  - show_result\nresources:\n  - path: ../shared-resources/context-and-identity.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/safety-and-permissions.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# 101 Dispatcher\n\nA sub-goal has one owner. Route a domain operation to one primary workflow from the table. Handle simple reads without a separate workflow and navigation here using available commands and `entity-resolution`; a helper does not become the goal owner. Execute compound requests sequentially.\n\n## Context\n\nBegin the first request with the standard `whoami` in MCP. Use its result to determine the available companies.\n\n1. Identify the action, object, constraints and response format. If different meanings lead to different workflows, first ask a short clarifying question under the [shared rule](../shared-resources/context-and-identity.md). Preserve the company, project, period, time zone, filters and decisions already made.\n2. If the operation requires a company: explicit selection or the target entity's company → non-null `whoami.default_company` → a question to the user. Multiple companies with a non-null `default_company` do not require a question. Ask for a company on `company_selection_required`. When the absence of companies is confirmed, continue the original goal through company creation or waiting for an invitation under the shared rule; route creation to `company-creation`. `default_company=null` alone does not mean that there are no companies.\n3. Resolve the company again for an independent new request; preserve it within a request until the context changes.\n4. Select the workflow from the table. Load only an actually available instruction through `resources/read`; the published internal workflow address is `skill://101-app/101-index/internal/<name>/SKILL.md`. If a workflow is unavailable, state the gap; do not invent a missing command.\n5. Pass the goal, explicit action, verified entities and clarification answers. The domain workflow clarifies only remaining material parameters and prepares the write; it does not repeat resolved questions.\n\n## Action and Result Format\n\n- **Reading:** a list, search or specific amount. Obtain data with the relevant commands. To show records, use `show_result` when the command is available and `structuredContent.presentation.token` was returned; otherwise reply in available text. Reading does not itself require analytics or a chart.\n- **App screen:** handle an explicit request to open a 101 screen through `open_app_screen` with `mode=immediate`. Take the target from verified data and the screen from the current tool schema. Only `navigationStatus=opened` confirms success. For an object card, resolve an offered transition (`mode=offer`) through `resolve_screen_offer` after the user's answer. Offer lists in words and open them after agreement: the current `mode=offer` for a list may open it immediately. Obtain current-screen context through `get_current_screen` when the request needs it.\n- **Analytics:** comparison, trend, assessment or audit. Charts are allowed with verified data. “Text only,” “table only” and “no charts” constrain the result format.\n- **Changes to business records:** explicit creation, modification or deletion. Follow server permissions and standard confirmation; reading, a recommendation and an attachment do not themselves authorize business-data changes. Personal memory and uploads have their own rules.\n\nHandle an independent request to upload a supplied file here through `file-handling`: you remain the goal owner. An upload does not require association with a Wiki page, event or company; the shared rule for continuing the goal still applies. Place it somewhere only for a separate placement goal.\n\nRoute a Gantt request to the native 101 plan: ordinary tasks to `task-management`, estimate positions to `estimate-management`, and expense-report positions to `report-management`. Do not offer a separate diagram in chat instead of this path.\n\n## Owners of Domain Requests\n\n| Goal | Instruction |\n| --- | --- |\n| Create a company | [company-creation/SKILL.md](../company-creation/SKILL.md) |\n| Read, create or change projects and expense categories | [project-management/SKILL.md](../project-management/SKILL.md) |\n| Tasks, comments and bulk actions | [task-management/SKILL.md](../task-management/SKILL.md) |\n| CRM pipelines, stages, deals and distribution | [crm-management/SKILL.md](../crm-management/SKILL.md) |\n| Wiki, blocks, publication and permissions | [wiki-management/SKILL.md](../wiki-management/SKILL.md) |\n| Estimates and positions | [estimate-management/SKILL.md](../estimate-management/SKILL.md) |\n| Expense events of type “Report” | [report-management/SKILL.md](../report-management/SKILL.md) |\n| Income, including commission and company-fund income | [income-management/SKILL.md](../income-management/SKILL.md) |\n| Transfers and settlements | [settlements-and-transfers/SKILL.md](../settlements-and-transfers/SKILL.md) |\n| Price lists, categories, positions and prices | [price-list-management/SKILL.md](../price-list-management/SKILL.md) |\n| Invite an existing user | [contractor-invitations/SKILL.md](../contractor-invitations/SKILL.md) |\n| One-off import of an external source | [data-import/SKILL.md](../data-import/SKILL.md) |\n| A standard PDF/XLSX document | [document-generation/SKILL.md](../document-generation/SKILL.md) |\n| Durable personal memory: remember/forget | [user-memory-management/SKILL.md](../user-memory-management/SKILL.md) |\n| App features and company procedures | [product-support/SKILL.md](../product-support/SKILL.md) |\n| General audit, analytics, cash flow statement, P&L/income statement, EBITDA | [company-analytics/SKILL.md](../company-analytics/SKILL.md) |\n| A narrow financial risk or quick text check | [financial-account-audit/SKILL.md](../financial-account-audit/SKILL.md) |\n| One displayed amount, `financial_kpi_context_data_v1` | [financial-kpi-explanation/SKILL.md](../financial-kpi-explanation/SKILL.md) |\n\nThe word “report” alone does not authorize an expense creation. A general audit and a document for an event are different goals. “Interactive” does not mean analytics when the user requests a task card.\n\nOnly “do an audit” → “Check the whole company, one project or a specific issue?” Pass the known goal and decision about the optional technical check to `company-analytics` without asking again. A narrow check does not require it. Load analytics presentation instructions (`analytics-visualization`) only when the format needs them.\n\nAfter the main result, you may offer an import once to the owner if the complete event list has already been obtained and contains fewer than 50 events. Do not load the list for the offer; do not repeat a known refusal.\n\nFollow the shared `safety-and-permissions.md` policy, including the external data-migration boundary. Finish with a status from frontmatter, the verified result and material limitations. Show GUIDs only on explicit request.\n"
Full snapshot data
{
  "description": "Use for requests about 101 data and features when the action and primary workflow need to be identified.",
  "included_files": [],
  "name": "101-index",
  "skill_md_contents": "---\nname: 101-index\ndescription: Use for requests about 101 data and features when the action and primary workflow need to be identified.\nversion: \"1.5.0\"\nrole: index\ninvocation: automatic\nintents:\n  - 101.route\ndepends_on: []\nrequired_tools:\n  - whoami\noptional_tools:\n  - list_projects\n  - list_events\n  - list_wikis\n  - list_tasks\n  - get_current_screen\n  - open_app_screen\n  - resolve_screen_offer\n  - show_result\nresources:\n  - path: ../shared-resources/context-and-identity.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/safety-and-permissions.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# 101 Dispatcher\n\nA sub-goal has one owner. Route a domain operation to one primary workflow from the table. Handle simple reads without a separate workflow and navigation here using available commands and `entity-resolution`; a helper does not become the goal owner. Execute compound requests sequentially.\n\n## Context\n\nBegin the first request with the standard `whoami` in MCP. Use its result to determine the available companies.\n\n1. Identify the action, object, constraints and response format. If different meanings lead to different workflows, first ask a short clarifying question under the [shared rule](../shared-resources/context-and-identity.md). Preserve the company, project, period, time zone, filters and decisions already made.\n2. If the operation requires a company: explicit selection or the target entity's company → non-null `whoami.default_company` → a question to the user. Multiple companies with a non-null `default_company` do not require a question. Ask for a company on `company_selection_required`. When the absence of companies is confirmed, continue the original goal through company creation or waiting for an invitation under the shared rule; route creation to `company-creation`. `default_company=null` alone does not mean that there are no companies.\n3. Resolve the company again for an independent new request; preserve it within a request until the context changes.\n4. Select the workflow from the table. Load only an actually available instruction through `resources/read`; the published internal workflow address is `skill://101-app/101-index/internal/<name>/SKILL.md`. If a workflow is unavailable, state the gap; do not invent a missing command.\n5. Pass the goal, explicit action, verified entities and clarification answers. The domain workflow clarifies only remaining material parameters and prepares the write; it does not repeat resolved questions.\n\n## Action and Result Format\n\n- **Reading:** a list, search or specific amount. Obtain data with the relevant commands. To show records, use `show_result` when the command is available and `structuredContent.presentation.token` was returned; otherwise reply in available text. Reading does not itself require analytics or a chart.\n- **App screen:** handle an explicit request to open a 101 screen through `open_app_screen` with `mode=immediate`. Take the target from verified data and the screen from the current tool schema. Only `navigationStatus=opened` confirms success. For an object card, resolve an offered transition (`mode=offer`) through `resolve_screen_offer` after the user's answer. Offer lists in words and open them after agreement: the current `mode=offer` for a list may open it immediately. Obtain current-screen context through `get_current_screen` when the request needs it.\n- **Analytics:** comparison, trend, assessment or audit. Charts are allowed with verified data. “Text only,” “table only” and “no charts” constrain the result format.\n- **Changes to business records:** explicit creation, modification or deletion. Follow server permissions and standard confirmation; reading, a recommendation and an attachment do not themselves authorize business-data changes. Personal memory and uploads have their own rules.\n\nHandle an independent request to upload a supplied file here through `file-handling`: you remain the goal owner. An upload does not require association with a Wiki page, event or company; the shared rule for continuing the goal still applies. Place it somewhere only for a separate placement goal.\n\nRoute a Gantt request to the native 101 plan: ordinary tasks to `task-management`, estimate positions to `estimate-management`, and expense-report positions to `report-management`. Do not offer a separate diagram in chat instead of this path.\n\n## Owners of Domain Requests\n\n| Goal | Instruction |\n| --- | --- |\n| Create a company | [company-creation/SKILL.md](../company-creation/SKILL.md) |\n| Read, create or change projects and expense categories | [project-management/SKILL.md](../project-management/SKILL.md) |\n| Tasks, comments and bulk actions | [task-management/SKILL.md](../task-management/SKILL.md) |\n| CRM pipelines, stages, deals and distribution | [crm-management/SKILL.md](../crm-management/SKILL.md) |\n| Wiki, blocks, publication and permissions | [wiki-management/SKILL.md](../wiki-management/SKILL.md) |\n| Estimates and positions | [estimate-management/SKILL.md](../estimate-management/SKILL.md) |\n| Expense events of type “Report” | [report-management/SKILL.md](../report-management/SKILL.md) |\n| Income, including commission and company-fund income | [income-management/SKILL.md](../income-management/SKILL.md) |\n| Transfers and settlements | [settlements-and-transfers/SKILL.md](../settlements-and-transfers/SKILL.md) |\n| Price lists, categories, positions and prices | [price-list-management/SKILL.md](../price-list-management/SKILL.md) |\n| Invite an existing user | [contractor-invitations/SKILL.md](../contractor-invitations/SKILL.md) |\n| One-off import of an external source | [data-import/SKILL.md](../data-import/SKILL.md) |\n| A standard PDF/XLSX document | [document-generation/SKILL.md](../document-generation/SKILL.md) |\n| Durable personal memory: remember/forget | [user-memory-management/SKILL.md](../user-memory-management/SKILL.md) |\n| App features and company procedures | [product-support/SKILL.md](../product-support/SKILL.md) |\n| General audit, analytics, cash flow statement, P&L/income statement, EBITDA | [company-analytics/SKILL.md](../company-analytics/SKILL.md) |\n| A narrow financial risk or quick text check | [financial-account-audit/SKILL.md](../financial-account-audit/SKILL.md) |\n| One displayed amount, `financial_kpi_context_data_v1` | [financial-kpi-explanation/SKILL.md](../financial-kpi-explanation/SKILL.md) |\n\nThe word “report” alone does not authorize an expense creation. A general audit and a document for an event are different goals. “Interactive” does not mean analytics when the user requests a task card.\n\nOnly “do an audit” → “Check the whole company, one project or a specific issue?” Pass the known goal and decision about the optional technical check to `company-analytics` without asking again. A narrow check does not require it. Load analytics presentation instructions (`analytics-visualization`) only when the format needs them.\n\nAfter the main result, you may offer an import once to the owner if the complete event list has already been obtained and contains fewer than 50 events. Do not load the list for the offer; do not repeat a known refusal.\n\nFollow the shared `safety-and-permissions.md` policy, including the external data-migration boundary. Finish with a status from frontmatter, the verified result and material limitations. Show GUIDs only on explicit request.\n"
}

SHA-256 of public snapshot: b11b42d1974a0e6157384ba166bb20d0ca64a506b71d3479333bb06888c7b848