Update to 101
Snapshot Nov 11, 2026 · 00:08 UTC · version 2.0.6
Collection source: downloaded plugin package.
Instructions updated for estimate-management
Skill instructions — Now says: - If `create_estimate` returns `9120`, tell the user that the project has no customer assigned. Keep the positions and prices. Offer to [assign a...
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 9, 2026 · 00:21 UTC
No removed lines (ordering may have changed)
Nov 11, 2026 · 00:08 UTC
- 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...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -53,6 +53,7 @@ ## Writing - 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. - Pass attachments as server identifiers from supported uploads; a local path is not an event attachment.
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.0.0\"\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## Writing\n\n- Creation: prepare positions through `event-positions`, check arguments through `write-preflight`, and call `create_estimate`.\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.0.0\"\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## Writing\n\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.0.0\"\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## Writing\n\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: 124579e02366ff544e3b015d782f76ab596eb9fbf1611a6a5c009d93c97a68e6