Update to 101
Snapshot Nov 15, 2026 · 18:08 UTC · version 2.0.11
Collection source: downloaded plugin package.
Instructions updated for event-positions
Skill instructions — Now says: - Preserve supplied `startDate` and `endDate`. On creation, follow the [position scheduling...
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
- Take `startDate` and `endDate` from the explicit request or existing position. Never replace an allowed `null` with the event date, project date, or today.
Nov 15, 2026 · 18:08 UTC
- Preserve supplied `startDate` and `endDate`. On creation, follow the [position scheduling rules](../shared-resources/events-and-positions.md#scheduling-positions-on-creation). Never replace an allowed `null` with the event date, projec...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -37,7 +37,7 @@ - Price list: select it through `list_price_lists` and read `get_price_list` with `price_list_id`. Take categories and positions from the full detail; there are no separate commands to find them. - Estimate: use `list_project_estimate_positions` and preserve source references. - Manual entry: obtain the explicit name, unit, quantity, price, and required fields; never invent a price-list reference. -- Take `startDate` and `endDate` from the explicit request or existing position. Never replace an allowed `null` with the event date, project date, or today. +- Preserve supplied `startDate` and `endDate`. On creation, follow the [position scheduling rules](../shared-resources/events-and-positions.md#scheduling-positions-on-creation). Never replace an allowed `null` with the event date, project date, or today. For creation, assemble the list according to the command schema. For editing, read `get_event`, change only the target fields in the complete fresh list, and preserve the other rows, sources, and dates.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: event-positions\ndescription: Use when an internal report or estimate workflow must resolve positions from a price list, an estimate, or manual entry and preserve their startDate and endDate through the existing event API.\nversion: \"1.0.0\"\nrole: helper\ninvocation: internal\nintents:\n - events.positions.prepare\n - events.positions.edit\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - get_event\n - list_project_estimate_positions\noptional_tools:\n - list_price_lists\n - get_price_list\nresources:\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# Event Positions\n\nPrepare positions for `report-management` and `estimate-management`; do not create the event yourself.\n\n- Price list: select it through `list_price_lists` and read `get_price_list` with `price_list_id`. Take categories and positions from the full detail; there are no separate commands to find them.\n- Estimate: use `list_project_estimate_positions` and preserve source references.\n- Manual entry: obtain the explicit name, unit, quantity, price, and required fields; never invent a price-list reference.\n- Take `startDate` and `endDate` from the explicit request or existing position. Never replace an allowed `null` with the event date, project date, or today.\n\nFor creation, assemble the list according to the command schema. For editing, read `get_event`, change only the target fields in the complete fresh list, and preserve the other rows, sources, and dates.\n\nBefore an edit, pass the list to `write-preflight`. A change to the target position or list membership after the original read is a conflict: stop, do not merge automatically, and do not send one row instead of the complete list.\n"
"---\nname: event-positions\ndescription: Use when an internal report or estimate workflow must resolve positions from a price list, an estimate, or manual entry and preserve their startDate and endDate through the existing event API.\nversion: \"1.0.0\"\nrole: helper\ninvocation: internal\nintents:\n - events.positions.prepare\n - events.positions.edit\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - get_event\n - list_project_estimate_positions\noptional_tools:\n - list_price_lists\n - get_price_list\nresources:\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# Event Positions\n\nPrepare positions for `report-management` and `estimate-management`; do not create the event yourself.\n\n- Price list: select it through `list_price_lists` and read `get_price_list` with `price_list_id`. Take categories and positions from the full detail; there are no separate commands to find them.\n- Estimate: use `list_project_estimate_positions` and preserve source references.\n- Manual entry: obtain the explicit name, unit, quantity, price, and required fields; never invent a price-list reference.\n- Preserve supplied `startDate` and `endDate`. On creation, follow the [position scheduling rules](../shared-resources/events-and-positions.md#scheduling-positions-on-creation). Never replace an allowed `null` with the event date, project date, or today.\n\nFor creation, assemble the list according to the command schema. For editing, read `get_event`, change only the target fields in the complete fresh list, and preserve the other rows, sources, and dates.\n\nBefore an edit, pass the list to `write-preflight`. A change to the target position or list membership after the original read is a conflict: stop, do not merge automatically, and do not send one row instead of the complete list.\n"
Full snapshot data
{
"description": "Use when an internal report or estimate workflow must resolve positions from a price list, an estimate, or manual entry and preserve their startDate and endDate through the existing event API.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 43
}
],
"name": "event-positions",
"skill_md_contents": "---\nname: event-positions\ndescription: Use when an internal report or estimate workflow must resolve positions from a price list, an estimate, or manual entry and preserve their startDate and endDate through the existing event API.\nversion: \"1.0.0\"\nrole: helper\ninvocation: internal\nintents:\n - events.positions.prepare\n - events.positions.edit\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - get_event\n - list_project_estimate_positions\noptional_tools:\n - list_price_lists\n - get_price_list\nresources:\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# Event Positions\n\nPrepare positions for `report-management` and `estimate-management`; do not create the event yourself.\n\n- Price list: select it through `list_price_lists` and read `get_price_list` with `price_list_id`. Take categories and positions from the full detail; there are no separate commands to find them.\n- Estimate: use `list_project_estimate_positions` and preserve source references.\n- Manual entry: obtain the explicit name, unit, quantity, price, and required fields; never invent a price-list reference.\n- Preserve supplied `startDate` and `endDate`. On creation, follow the [position scheduling rules](../shared-resources/events-and-positions.md#scheduling-positions-on-creation). Never replace an allowed `null` with the event date, project date, or today.\n\nFor creation, assemble the list according to the command schema. For editing, read `get_event`, change only the target fields in the complete fresh list, and preserve the other rows, sources, and dates.\n\nBefore an edit, pass the list to `write-preflight`. A change to the target position or list membership after the original read is a conflict: stop, do not merge automatically, and do not send one row instead of the complete list.\n"
}SHA-256 of public snapshot: 57c7de42980981ca9e8f3886a49ed30daa852818c2d87402f4711a94d80e969d