← 101CONTENT HISTORY

Update to 101

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

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save 101 and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when an internal 101 request requires finding, reading, creating, or editing one or more expense reports 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": "report-management",
  "skill_md_contents": "---\nname: report-management\ndescription: Use when an internal 101 request requires finding, reading, creating, or editing one or more expense reports through the existing event API, including sourced or manual positions and their dates.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n  - reports.list\n  - reports.read\n  - reports.create\n  - reports.edit\ndepends_on:\n  - entity-resolution\n  - write-preflight\n  - event-positions\nrequired_tools:\n  - whoami\n  - list_events\n  - get_event\n  - create_expense\n  - edit_expense\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# Expense Report Management\n\nManage financial events of type Report through the original event contract. An analytical report belongs to `company-analytics`; the word report alone does not authorize creating an expense or drawing a chart.\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_expense`.\n- Editing: read `get_event`, prepare the complete resulting positions list, and call `edit_expense` 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: 0755bc7dd893035b6e54918f9c4afb01fad132dc4b05a5f13f5fd7ea238114b0