Update to 101
Snapshot Nov 11, 2026 · 18:08 UTC · version 2.0.7
Collection source: downloaded plugin package.
Instructions updated for 101-index
Skill instructions — Now says: | View or respond to incoming company invitations, invite an existing user, or add a virtual contractor card |...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Nov 11, 2026 · 00:08 UTC
| Invite an existing user or add a virtual contractor card | [contractor-invitations/SKILL.md](../contractor-invitations/SKILL.md) |
Nov 11, 2026 · 18:08 UTC
| View or respond to incoming company invitations, invite an existing user, or add a virtual contractor card | [contractor-invitations/SKILL.md](../contractor-invitations/SKILL.md) |
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -73,7 +73,7 @@ | 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 or add a virtual contractor card | [contractor-invitations/SKILL.md](../contractor-invitations/SKILL.md) | +| View or respond to incoming company invitations, invite an existing user, or add a virtual contractor card | [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) |
Full technical diff · 1 changed fields
changed /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\nIf the user asks to create a new project and an estimate for it, follow [project creation](../project-management/SKILL.md#project-creation) first. Then pass the verified project and agreed positions and prices to `estimate-management`.\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 or add a virtual contractor card | [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"
"---\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\nIf the user asks to create a new project and an estimate for it, follow [project creation](../project-management/SKILL.md#project-creation) first. Then pass the verified project and agreed positions and prices to `estimate-management`.\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| View or respond to incoming company invitations, invite an existing user, or add a virtual contractor card | [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\nIf the user asks to create a new project and an estimate for it, follow [project creation](../project-management/SKILL.md#project-creation) first. Then pass the verified project and agreed positions and prices to `estimate-management`.\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| View or respond to incoming company invitations, invite an existing user, or add a virtual contractor card | [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: 9448f159f1307585c2fba173f9c160a303c55e7dd69b4a2246bae8e81da182b2