← 101CONTENT HISTORY

Update to 101

Snapshot Nov 14, 2026 · 18:09 UTC · version 2.0.8

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for income-management

Skill instructions — Now says: - get_company_fund 3. `create_income`: `companyGuid`, `amount`, Unix `date` in seconds, and `eventSubtype` are required. Pass the project through canonical...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save 101 and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Nov 9, 2026 · 00:21 UTC

3. `create_income`: `companyGuid`, `amount`, Unix `date` in seconds, and `eventSubtype` are required. Pass the project through canonical `projectGuid`; do not invent optional fields.

After

Nov 14, 2026 · 18:09 UTC

- get_company_fund 3. `create_income`: `companyGuid`, `amount`, Unix `date` in seconds, and `eventSubtype` are required. Pass the project through canonical `projectGuid`; do not invent optional fields. For `company_income` into a chose...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -21,6 +21,7 @@
   - list_projects
   - list_contractors
   - list_bills
+  - get_company_fund
 resources:
   - path: ../shared-resources/context-and-identity.md
     kind: semantic-guide
@@ -47,7 +48,7 @@
 
 1. Determine the company and the target project, contractor, and category when the operation's meaning requires them. Do not choose them by result order.
 2. Before a write, check the current schema, access, and the user's explicit action.
-3. `create_income`: `companyGuid`, `amount`, Unix `date` in seconds, and `eventSubtype` are required. Pass the project through canonical `projectGuid`; do not invent optional fields. Attachments are server-issued identifiers in `fileList`.
+3. `create_income`: `companyGuid`, `amount`, Unix `date` in seconds, and `eventSubtype` are required. Pass the project through canonical `projectGuid`; do not invent optional fields. For `company_income` into a chosen fund, pass `fundGuid` from `get_company_fund` → `funds`; without it, the main fund is used. Attachments are server-issued identifiers in `fileList`.
 4. `edit_income`: first read the event, then pass `guid` and only changed fields. An allowed `null` clears a field; preserve unaffected items before replacing lists. Use `isDeleted` only upon a request to delete.
 5. Current income tools require no additional confirmation; do not add a question on top of an explicit request. If the server requires standard confirmation, perform it. Retain the receipt and reread the event. Establish an unknown outcome before retrying. A series uses individual sequential calls; there is no overall transaction.
 
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: income-management\ndescription: Use for finding, creating, editing, and deleting project income, commission income, and fund income.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n  - income.list\n  - income.create\n  - income.edit\ndepends_on:\n  - entity-resolution\n  - write-preflight\nrequired_tools:\n  - whoami\n  - list_events\n  - get_event\noptional_tools:\n  - create_income\n  - edit_income\n  - list_projects\n  - list_contractors\n  - list_bills\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\n  - path: ../shared-resources/events-and-positions.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/finance-and-balances.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Income\n\nUse `list_events` with filters and pagination, and `get_event` for details. Main subtypes: `project_income` — project income, `commission_income` — commission income, `company_income` — income into the fund.\n\n1. Determine the company and the target project, contractor, and category when the operation's meaning requires them. Do not choose them by result order.\n2. Before a write, check the current schema, access, and the user's explicit action.\n3. `create_income`: `companyGuid`, `amount`, Unix `date` in seconds, and `eventSubtype` are required. Pass the project through canonical `projectGuid`; do not invent optional fields. Attachments are server-issued identifiers in `fileList`.\n4. `edit_income`: first read the event, then pass `guid` and only changed fields. An allowed `null` clears a field; preserve unaffected items before replacing lists. Use `isDeleted` only upon a request to delete.\n5. Current income tools require no additional confirmation; do not add a question on top of an explicit request. If the server requires standard confirmation, perform it. Retain the receipt and reread the event. Establish an unknown outcome before retrying. A series uses individual sequential calls; there is no overall transaction.\n\nDirect income into the fund is financing, not revenue or profit. Income, an expense report, and an internal transfer are different event types. Do not include an event “awaiting confirmation” in confirmed totals or call it a proven bank transaction.\n\nGeneral rules: [context-and-identity](../shared-resources/context-and-identity.md), [safety-and-permissions](../shared-resources/safety-and-permissions.md), [events-and-positions](../shared-resources/events-and-positions.md), [finance-and-balances](../shared-resources/finance-and-balances.md).\nBefore a write, use [entity-resolution](../entity-resolution/SKILL.md), [write-preflight](../write-preflight/SKILL.md).\n"
AFTER
"---\nname: income-management\ndescription: Use for finding, creating, editing, and deleting project income, commission income, and fund income.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n  - income.list\n  - income.create\n  - income.edit\ndepends_on:\n  - entity-resolution\n  - write-preflight\nrequired_tools:\n  - whoami\n  - list_events\n  - get_event\noptional_tools:\n  - create_income\n  - edit_income\n  - list_projects\n  - list_contractors\n  - list_bills\n  - get_company_fund\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\n  - path: ../shared-resources/events-and-positions.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/finance-and-balances.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Income\n\nUse `list_events` with filters and pagination, and `get_event` for details. Main subtypes: `project_income` — project income, `commission_income` — commission income, `company_income` — income into the fund.\n\n1. Determine the company and the target project, contractor, and category when the operation's meaning requires them. Do not choose them by result order.\n2. Before a write, check the current schema, access, and the user's explicit action.\n3. `create_income`: `companyGuid`, `amount`, Unix `date` in seconds, and `eventSubtype` are required. Pass the project through canonical `projectGuid`; do not invent optional fields. For `company_income` into a chosen fund, pass `fundGuid` from `get_company_fund` → `funds`; without it, the main fund is used. Attachments are server-issued identifiers in `fileList`.\n4. `edit_income`: first read the event, then pass `guid` and only changed fields. An allowed `null` clears a field; preserve unaffected items before replacing lists. Use `isDeleted` only upon a request to delete.\n5. Current income tools require no additional confirmation; do not add a question on top of an explicit request. If the server requires standard confirmation, perform it. Retain the receipt and reread the event. Establish an unknown outcome before retrying. A series uses individual sequential calls; there is no overall transaction.\n\nDirect income into the fund is financing, not revenue or profit. Income, an expense report, and an internal transfer are different event types. Do not include an event “awaiting confirmation” in confirmed totals or call it a proven bank transaction.\n\nGeneral rules: [context-and-identity](../shared-resources/context-and-identity.md), [safety-and-permissions](../shared-resources/safety-and-permissions.md), [events-and-positions](../shared-resources/events-and-positions.md), [finance-and-balances](../shared-resources/finance-and-balances.md).\nBefore a write, use [entity-resolution](../entity-resolution/SKILL.md), [write-preflight](../write-preflight/SKILL.md).\n"
Full snapshot data
{
  "description": "Use for finding, creating, editing, and deleting project income, commission income, and fund income.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 43
    }
  ],
  "name": "income-management",
  "skill_md_contents": "---\nname: income-management\ndescription: Use for finding, creating, editing, and deleting project income, commission income, and fund income.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n  - income.list\n  - income.create\n  - income.edit\ndepends_on:\n  - entity-resolution\n  - write-preflight\nrequired_tools:\n  - whoami\n  - list_events\n  - get_event\noptional_tools:\n  - create_income\n  - edit_income\n  - list_projects\n  - list_contractors\n  - list_bills\n  - get_company_fund\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\n  - path: ../shared-resources/events-and-positions.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/finance-and-balances.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Income\n\nUse `list_events` with filters and pagination, and `get_event` for details. Main subtypes: `project_income` — project income, `commission_income` — commission income, `company_income` — income into the fund.\n\n1. Determine the company and the target project, contractor, and category when the operation's meaning requires them. Do not choose them by result order.\n2. Before a write, check the current schema, access, and the user's explicit action.\n3. `create_income`: `companyGuid`, `amount`, Unix `date` in seconds, and `eventSubtype` are required. Pass the project through canonical `projectGuid`; do not invent optional fields. For `company_income` into a chosen fund, pass `fundGuid` from `get_company_fund` → `funds`; without it, the main fund is used. Attachments are server-issued identifiers in `fileList`.\n4. `edit_income`: first read the event, then pass `guid` and only changed fields. An allowed `null` clears a field; preserve unaffected items before replacing lists. Use `isDeleted` only upon a request to delete.\n5. Current income tools require no additional confirmation; do not add a question on top of an explicit request. If the server requires standard confirmation, perform it. Retain the receipt and reread the event. Establish an unknown outcome before retrying. A series uses individual sequential calls; there is no overall transaction.\n\nDirect income into the fund is financing, not revenue or profit. Income, an expense report, and an internal transfer are different event types. Do not include an event “awaiting confirmation” in confirmed totals or call it a proven bank transaction.\n\nGeneral rules: [context-and-identity](../shared-resources/context-and-identity.md), [safety-and-permissions](../shared-resources/safety-and-permissions.md), [events-and-positions](../shared-resources/events-and-positions.md), [finance-and-balances](../shared-resources/finance-and-balances.md).\nBefore a write, use [entity-resolution](../entity-resolution/SKILL.md), [write-preflight](../write-preflight/SKILL.md).\n"
}

SHA-256 of public snapshot: b65d3d4994a4a473e1ce8f1cafee2342b94ccef11663c840f87d811589adc54f