Update to 101
Snapshot Nov 16, 2026 · 00:09 UTC · version 2.0.12
Collection source: downloaded plugin package.
Instructions updated for estimate-management
Skill instructions — Now says: version: "1.1.3" - When scheduling or rescheduling, you must [check the plan and estimate...
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 15, 2026 · 18:08 UTC
version: "1.1.2"
Nov 16, 2026 · 00:09 UTC
version: "1.1.3" - When scheduling or rescheduling, you must [check the plan and estimate boundaries](../shared-resources/events-and-positions.md#scheduling-positions-on-creation) before writing and verify the saved dates afterward.
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,7 +1,7 @@ --- name: estimate-management description: Use when an internal 101 request requires finding, reading, creating, or editing one or more estimates through the existing event API, including sourced or manual positions and their dates. -version: "1.1.2" +version: "1.1.3" role: primary invocation: internal intents: @@ -62,6 +62,7 @@ - Immediately before each `create_estimate` call, check the structure of the entire calculation. If it contains several independent sections or stages and the structure has not yet been agreed, you must ask “Create one combined estimate or several separate estimates?” and wait for the user's choice. Saving that calculation before the user answers is prohibited. A single project or expense category does not imply agreement to one combined estimate. - If the user has already chosen the structure, do not ask again. Create the estimate or estimates according to that choice, without omitting or duplicating positions. +- When scheduling or rescheduling, you must [check the plan and estimate boundaries](../shared-resources/events-and-positions.md#scheduling-positions-on-creation) before writing and verify the saved dates afterward. - Creation: prepare positions through `event-positions`, check arguments through `write-preflight`, and call `create_estimate`. - If `create_estimate` returns `9120`, tell the user that the project has no customer assigned. Keep the positions and prices. Offer to [assign a customer](../project-management/SKILL.md#project-and-expense-category-edits), then continue the estimate in the same project once the customer is assigned. - Editing: read `get_event`, prepare the complete resulting positions list, and call `edit_estimate` after a fresh check. Preserve neighboring rows, sources, `startDate`, and `endDate`. A conflict between the original and current state stops the write.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: estimate-management\ndescription: Use when an internal 101 request requires finding, reading, creating, or editing one or more estimates through the existing event API, including sourced or manual positions and their dates.\nversion: \"1.1.2\"\nrole: primary\ninvocation: internal\nintents:\n - estimates.list\n - estimates.read\n - estimates.create\n - estimates.edit\ndepends_on:\n - entity-resolution\n - write-preflight\n - event-positions\nrequired_tools:\n - whoami\n - list_events\n - get_event\n - create_estimate\n - edit_estimate\noptional_tools:\n - list_projects\n - list_bills\n - list_contractors\n - upload_files\n - show_result\nresources:\n - path: ../shared-resources/context-and-identity.md\n kind: semantic-guide\n required: true\n - path: ../shared-resources/events-and-positions.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# Estimate Management\n\nManage financial events of type Estimate through the original event contract.\n\n## Reading\n\nResolve the company, project, and participants through `entity-resolution`. For a list, use `list_events` with the required type, filters, and pagination; for details, use `get_event`. Never present the first page as the complete set. Display records through an available `show_result` using the issued token; this is not analytics.\n\n## Structure of a new calculation\n\n- Preserve the user's chosen format. A homogeneous calculation needs only one estimate. If it contains independent blocks by purpose, stage, or timing and no format has been chosen, briefly offer one estimate or a split into several.\n- For a project, read all its categories through `list_bills` with `project_guid` and pagination and match them to the meaning of the blocks. If none fit, propose only the missing categories and create them after agreement through [project management](../project-management/SKILL.md#project-and-expense-category-edits). Several estimates may share one category.\n- When splitting, give each block its own estimate, one available category (`billGuid`), and set of positions. Preserve the calculation's total scope and amount without counting positions twice.\n- Ask for scheduling consent and the overall period once for the entire calculation, following `../shared-resources/events-and-positions.md`. Within that period, schedule positions according to their dependencies and align them with the relevant stages. Each estimate spans the earliest start through the latest end of its own positions. Independent estimates may overlap, and an ongoing estimate spans the full period only through its own positions. Preserve supplied position dates.\n- Before creation, show a compact plan of estimates with categories, periods, contents, and amounts. Once the structure is chosen and categories are ready, create estimates using the sequence rules below.\n\n## Writing\n\n- Immediately before each `create_estimate` call, check the structure of the entire calculation. If it contains several independent sections or stages and the structure has not yet been agreed, you must ask “Create one combined estimate or several separate estimates?” and wait for the user's choice. Saving that calculation before the user answers is prohibited. A single project or expense category does not imply agreement to one combined estimate.\n- If the user has already chosen the structure, do not ask again. Create the estimate or estimates according to that choice, without omitting or duplicating positions.\n- Creation: prepare positions through `event-positions`, check arguments through `write-preflight`, and call `create_estimate`.\n- If `create_estimate` returns `9120`, tell the user that the project has no customer assigned. Keep the positions and prices. Offer to [assign a customer](../project-management/SKILL.md#project-and-expense-category-edits), then continue the estimate in the same project once the customer is assigned.\n- Editing: read `get_event`, prepare the complete resulting positions list, and call `edit_estimate` after a fresh check. Preserve neighboring rows, sources, `startDate`, and `endDate`. A conflict between the original and current state stops the write.\n- Pass attachments as server identifiers from supported uploads; a local path is not an event attachment.\n\n## A sequence\n\nCheck the entire queue before the first creation: required data, entities, and exact arguments for every event. Resolve any known error before starting. Then make individual calls with a check before each; there is no batch format.\n\nPreserve receipts. A local data error permits continuing with independent items; loss of permissions, a system error, or an unknown outcome stops the remainder. Never repeat a confirmed creation. Recover and verify results according to `../shared-resources/events-and-positions.md`.\n\nReturn created, not created, and not started events with reasons; never call an awaiting-confirmation state a completed settlement.\n"
"---\nname: estimate-management\ndescription: Use when an internal 101 request requires finding, reading, creating, or editing one or more estimates through the existing event API, including sourced or manual positions and their dates.\nversion: \"1.1.3\"\nrole: primary\ninvocation: internal\nintents:\n - estimates.list\n - estimates.read\n - estimates.create\n - estimates.edit\ndepends_on:\n - entity-resolution\n - write-preflight\n - event-positions\nrequired_tools:\n - whoami\n - list_events\n - get_event\n - create_estimate\n - edit_estimate\noptional_tools:\n - list_projects\n - list_bills\n - list_contractors\n - upload_files\n - show_result\nresources:\n - path: ../shared-resources/context-and-identity.md\n kind: semantic-guide\n required: true\n - path: ../shared-resources/events-and-positions.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# Estimate Management\n\nManage financial events of type Estimate through the original event contract.\n\n## Reading\n\nResolve the company, project, and participants through `entity-resolution`. For a list, use `list_events` with the required type, filters, and pagination; for details, use `get_event`. Never present the first page as the complete set. Display records through an available `show_result` using the issued token; this is not analytics.\n\n## Structure of a new calculation\n\n- Preserve the user's chosen format. A homogeneous calculation needs only one estimate. If it contains independent blocks by purpose, stage, or timing and no format has been chosen, briefly offer one estimate or a split into several.\n- For a project, read all its categories through `list_bills` with `project_guid` and pagination and match them to the meaning of the blocks. If none fit, propose only the missing categories and create them after agreement through [project management](../project-management/SKILL.md#project-and-expense-category-edits). Several estimates may share one category.\n- When splitting, give each block its own estimate, one available category (`billGuid`), and set of positions. Preserve the calculation's total scope and amount without counting positions twice.\n- Ask for scheduling consent and the overall period once for the entire calculation, following `../shared-resources/events-and-positions.md`. Within that period, schedule positions according to their dependencies and align them with the relevant stages. Each estimate spans the earliest start through the latest end of its own positions. Independent estimates may overlap, and an ongoing estimate spans the full period only through its own positions. Preserve supplied position dates.\n- Before creation, show a compact plan of estimates with categories, periods, contents, and amounts. Once the structure is chosen and categories are ready, create estimates using the sequence rules below.\n\n## Writing\n\n- Immediately before each `create_estimate` call, check the structure of the entire calculation. If it contains several independent sections or stages and the structure has not yet been agreed, you must ask “Create one combined estimate or several separate estimates?” and wait for the user's choice. Saving that calculation before the user answers is prohibited. A single project or expense category does not imply agreement to one combined estimate.\n- If the user has already chosen the structure, do not ask again. Create the estimate or estimates according to that choice, without omitting or duplicating positions.\n- When scheduling or rescheduling, you must [check the plan and estimate boundaries](../shared-resources/events-and-positions.md#scheduling-positions-on-creation) before writing and verify the saved dates afterward.\n- Creation: prepare positions through `event-positions`, check arguments through `write-preflight`, and call `create_estimate`.\n- If `create_estimate` returns `9120`, tell the user that the project has no customer assigned. Keep the positions and prices. Offer to [assign a customer](../project-management/SKILL.md#project-and-expense-category-edits), then continue the estimate in the same project once the customer is assigned.\n- Editing: read `get_event`, prepare the complete resulting positions list, and call `edit_estimate` after a fresh check. Preserve neighboring rows, sources, `startDate`, and `endDate`. A conflict between the original and current state stops the write.\n- Pass attachments as server identifiers from supported uploads; a local path is not an event attachment.\n\n## A sequence\n\nCheck the entire queue before the first creation: required data, entities, and exact arguments for every event. Resolve any known error before starting. Then make individual calls with a check before each; there is no batch format.\n\nPreserve receipts. A local data error permits continuing with independent items; loss of permissions, a system error, or an unknown outcome stops the remainder. Never repeat a confirmed creation. Recover and verify results according to `../shared-resources/events-and-positions.md`.\n\nReturn created, not created, and not started events with reasons; never call an awaiting-confirmation state a completed settlement.\n"
Full snapshot data
{
"description": "Use when an internal 101 request requires finding, reading, creating, or editing one or more estimates through the existing event API, including sourced or manual positions and their dates.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 43
}
],
"name": "estimate-management",
"skill_md_contents": "---\nname: estimate-management\ndescription: Use when an internal 101 request requires finding, reading, creating, or editing one or more estimates through the existing event API, including sourced or manual positions and their dates.\nversion: \"1.1.3\"\nrole: primary\ninvocation: internal\nintents:\n - estimates.list\n - estimates.read\n - estimates.create\n - estimates.edit\ndepends_on:\n - entity-resolution\n - write-preflight\n - event-positions\nrequired_tools:\n - whoami\n - list_events\n - get_event\n - create_estimate\n - edit_estimate\noptional_tools:\n - list_projects\n - list_bills\n - list_contractors\n - upload_files\n - show_result\nresources:\n - path: ../shared-resources/context-and-identity.md\n kind: semantic-guide\n required: true\n - path: ../shared-resources/events-and-positions.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# Estimate Management\n\nManage financial events of type Estimate through the original event contract.\n\n## Reading\n\nResolve the company, project, and participants through `entity-resolution`. For a list, use `list_events` with the required type, filters, and pagination; for details, use `get_event`. Never present the first page as the complete set. Display records through an available `show_result` using the issued token; this is not analytics.\n\n## Structure of a new calculation\n\n- Preserve the user's chosen format. A homogeneous calculation needs only one estimate. If it contains independent blocks by purpose, stage, or timing and no format has been chosen, briefly offer one estimate or a split into several.\n- For a project, read all its categories through `list_bills` with `project_guid` and pagination and match them to the meaning of the blocks. If none fit, propose only the missing categories and create them after agreement through [project management](../project-management/SKILL.md#project-and-expense-category-edits). Several estimates may share one category.\n- When splitting, give each block its own estimate, one available category (`billGuid`), and set of positions. Preserve the calculation's total scope and amount without counting positions twice.\n- Ask for scheduling consent and the overall period once for the entire calculation, following `../shared-resources/events-and-positions.md`. Within that period, schedule positions according to their dependencies and align them with the relevant stages. Each estimate spans the earliest start through the latest end of its own positions. Independent estimates may overlap, and an ongoing estimate spans the full period only through its own positions. Preserve supplied position dates.\n- Before creation, show a compact plan of estimates with categories, periods, contents, and amounts. Once the structure is chosen and categories are ready, create estimates using the sequence rules below.\n\n## Writing\n\n- Immediately before each `create_estimate` call, check the structure of the entire calculation. If it contains several independent sections or stages and the structure has not yet been agreed, you must ask “Create one combined estimate or several separate estimates?” and wait for the user's choice. Saving that calculation before the user answers is prohibited. A single project or expense category does not imply agreement to one combined estimate.\n- If the user has already chosen the structure, do not ask again. Create the estimate or estimates according to that choice, without omitting or duplicating positions.\n- When scheduling or rescheduling, you must [check the plan and estimate boundaries](../shared-resources/events-and-positions.md#scheduling-positions-on-creation) before writing and verify the saved dates afterward.\n- Creation: prepare positions through `event-positions`, check arguments through `write-preflight`, and call `create_estimate`.\n- If `create_estimate` returns `9120`, tell the user that the project has no customer assigned. Keep the positions and prices. Offer to [assign a customer](../project-management/SKILL.md#project-and-expense-category-edits), then continue the estimate in the same project once the customer is assigned.\n- Editing: read `get_event`, prepare the complete resulting positions list, and call `edit_estimate` after a fresh check. Preserve neighboring rows, sources, `startDate`, and `endDate`. A conflict between the original and current state stops the write.\n- Pass attachments as server identifiers from supported uploads; a local path is not an event attachment.\n\n## A sequence\n\nCheck the entire queue before the first creation: required data, entities, and exact arguments for every event. Resolve any known error before starting. Then make individual calls with a check before each; there is no batch format.\n\nPreserve receipts. A local data error permits continuing with independent items; loss of permissions, a system error, or an unknown outcome stops the remainder. Never repeat a confirmed creation. Recover and verify results according to `../shared-resources/events-and-positions.md`.\n\nReturn created, not created, and not started events with reasons; never call an awaiting-confirmation state a completed settlement.\n"
}SHA-256 of public snapshot: 579039b6557ee83c28c87b8ce731d6b73bbce9bba7fe8b3ca1f0b7490059a604