Update to 101
Snapshot Nov 14, 2026 · 18:09 UTC · version 2.0.8
Collection source: downloaded plugin package.
Instructions updated for settlements-and-transfers
Skill instructions — Now says: With several funds, determine the fund from `funds` in `get_company_fund`. Project balances come from `list_contractor_project_balances`; fund balances come...
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
Project balances come from `list_contractor_project_balances`; fund balances come from `get_company_fund` and `list_company_fund_members`. If you use `list_project_members`, always pair it with `get_project_fund_settlements` for the same...
Nov 14, 2026 · 18:09 UTC
With several funds, determine the fund from `funds` in `get_company_fund`. Project balances come from `list_contractor_project_balances`; fund balances come from `get_company_fund` and `list_company_fund_members`. If you use `list_projec...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -53,7 +53,7 @@ ## Calculation -1. Resolve the company, participant, and scope through `entity-resolution`: a project or the company fund. Clarify an ambiguous scope; do not require a project for a fund transfer. Project balances come from `list_contractor_project_balances`; fund balances come from `get_company_fund` and `list_company_fund_members`. If you use `list_project_members`, always pair it with `get_project_fund_settlements` for the same project; signs and partial data are covered in `../shared-resources/finance-and-balances.md`. +1. Resolve the company, participant, and scope through `entity-resolution`: a project or the company fund. Clarify an ambiguous scope; do not require a project for a fund transfer. With several funds, determine the fund from `funds` in `get_company_fund`. Project balances come from `list_contractor_project_balances`; fund balances come from `get_company_fund` and `list_company_fund_members`. If you use `list_project_members`, always pair it with `get_project_fund_settlements` for the same project; signs and partial data are covered in `../shared-resources/finance-and-balances.md`. 2. Close a negative own balance with an own-funds transfer and a negative accountable balance with an accountable-funds transfer. If both are negative, show two rows in one plan. 3. A positive accountable balance can cover a negative own balance through a participant's self-transfer. Explain this part; do not create a self-transfer on someone else's behalf. Recommend an external transfer only for the remainder. 4. A project cash shortage does not by itself prohibit a payment. Show the resulting deficit, obtain consent to that plan, and recommend an inflow from the customer. There is no system command to request money. @@ -62,6 +62,7 @@ - Apply `write-preflight`. Pass the exact subtype from the creation form, the amount, participants, and a Unix date in seconds. - `create_payment_record`: specify the project only through `projectShare`; for one project, use a 100% share. There is no separate project field. Attachments are server identifiers in `fileList`. +- A transfer between funds uses subtype `company_fund_transfer`: `fundGuid` is the source (empty means the main fund), `targetFundGuid` is a different receiving fund, and `senderGuid` is the person holding the money; no `projectShare`. - `edit_payment_record`: first read `get_event`; pass `guid` and only changed fields. An explicit `null` clears a permitted field; preserve complete share and attachment lists when replacing them. Delete through `isDeleted` only on an explicit request. - Execute related transfers sequentially after an understandable plan and standard confirmation. Preserve each row's result; an unknown outcome or denial stops the remainder. Recover according to `../shared-resources/events-and-positions.md`.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: settlements-and-transfers\ndescription: Use when the user asks to settle with a person, pay a debt, transfer money, or close a balance on a project.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n - settlements.calculate\n - transfers.create\n - transfers.edit\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - whoami\n - list_projects\n - list_contractors\n - list_contractor_project_balances\n - create_payment_record\noptional_tools:\n - edit_payment_record\n - get_company_fund\n - list_company_fund_members\n - search_users\n - list_project_members\n - get_project_fund_settlements\n - get_event\n - list_events\n - get_project_summary\nresources:\n - path: ../shared-resources/context-and-identity.md\n kind: semantic-guide\n required: true\n - path: ../shared-resources/finance-and-balances.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\ncompletion:\n statuses:\n - готово\n - частично\n - заблокировано\n---\n\n# Settlements and Transfers\n\nCarry out an explicit request to settle, create, or edit a transfer. A general audit belongs to analytics.\n\n## Calculation\n\n1. Resolve the company, participant, and scope through `entity-resolution`: a project or the company fund. Clarify an ambiguous scope; do not require a project for a fund transfer. Project balances come from `list_contractor_project_balances`; fund balances come from `get_company_fund` and `list_company_fund_members`. If you use `list_project_members`, always pair it with `get_project_fund_settlements` for the same project; signs and partial data are covered in `../shared-resources/finance-and-balances.md`.\n2. Close a negative own balance with an own-funds transfer and a negative accountable balance with an accountable-funds transfer. If both are negative, show two rows in one plan.\n3. A positive accountable balance can cover a negative own balance through a participant's self-transfer. Explain this part; do not create a self-transfer on someone else's behalf. Recommend an external transfer only for the remainder.\n4. A project cash shortage does not by itself prohibit a payment. Show the resulting deficit, obtain consent to that plan, and recommend an inflow from the customer. There is no system command to request money.\n\n## Writing\n\n- Apply `write-preflight`. Pass the exact subtype from the creation form, the amount, participants, and a Unix date in seconds.\n- `create_payment_record`: specify the project only through `projectShare`; for one project, use a 100% share. There is no separate project field. Attachments are server identifiers in `fileList`.\n- `edit_payment_record`: first read `get_event`; pass `guid` and only changed fields. An explicit `null` clears a permitted field; preserve complete share and attachment lists when replacing them. Delete through `isDeleted` only on an explicit request.\n- Execute related transfers sequentially after an understandable plan and standard confirmation. Preserve each row's result; an unknown outcome or denial stops the remainder. Recover according to `../shared-resources/events-and-positions.md`.\n\nAfter a write, check `get_event` and fresh balances. `not_verified` means awaiting confirmation; the event does not prove a bank payment or debt closure. Return created, edited, and unfinished items with reasons.\n"
"---\nname: settlements-and-transfers\ndescription: Use when the user asks to settle with a person, pay a debt, transfer money, or close a balance on a project.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n - settlements.calculate\n - transfers.create\n - transfers.edit\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - whoami\n - list_projects\n - list_contractors\n - list_contractor_project_balances\n - create_payment_record\noptional_tools:\n - edit_payment_record\n - get_company_fund\n - list_company_fund_members\n - search_users\n - list_project_members\n - get_project_fund_settlements\n - get_event\n - list_events\n - get_project_summary\nresources:\n - path: ../shared-resources/context-and-identity.md\n kind: semantic-guide\n required: true\n - path: ../shared-resources/finance-and-balances.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\ncompletion:\n statuses:\n - готово\n - частично\n - заблокировано\n---\n\n# Settlements and Transfers\n\nCarry out an explicit request to settle, create, or edit a transfer. A general audit belongs to analytics.\n\n## Calculation\n\n1. Resolve the company, participant, and scope through `entity-resolution`: a project or the company fund. Clarify an ambiguous scope; do not require a project for a fund transfer. With several funds, determine the fund from `funds` in `get_company_fund`. Project balances come from `list_contractor_project_balances`; fund balances come from `get_company_fund` and `list_company_fund_members`. If you use `list_project_members`, always pair it with `get_project_fund_settlements` for the same project; signs and partial data are covered in `../shared-resources/finance-and-balances.md`.\n2. Close a negative own balance with an own-funds transfer and a negative accountable balance with an accountable-funds transfer. If both are negative, show two rows in one plan.\n3. A positive accountable balance can cover a negative own balance through a participant's self-transfer. Explain this part; do not create a self-transfer on someone else's behalf. Recommend an external transfer only for the remainder.\n4. A project cash shortage does not by itself prohibit a payment. Show the resulting deficit, obtain consent to that plan, and recommend an inflow from the customer. There is no system command to request money.\n\n## Writing\n\n- Apply `write-preflight`. Pass the exact subtype from the creation form, the amount, participants, and a Unix date in seconds.\n- `create_payment_record`: specify the project only through `projectShare`; for one project, use a 100% share. There is no separate project field. Attachments are server identifiers in `fileList`.\n- A transfer between funds uses subtype `company_fund_transfer`: `fundGuid` is the source (empty means the main fund), `targetFundGuid` is a different receiving fund, and `senderGuid` is the person holding the money; no `projectShare`.\n- `edit_payment_record`: first read `get_event`; pass `guid` and only changed fields. An explicit `null` clears a permitted field; preserve complete share and attachment lists when replacing them. Delete through `isDeleted` only on an explicit request.\n- Execute related transfers sequentially after an understandable plan and standard confirmation. Preserve each row's result; an unknown outcome or denial stops the remainder. Recover according to `../shared-resources/events-and-positions.md`.\n\nAfter a write, check `get_event` and fresh balances. `not_verified` means awaiting confirmation; the event does not prove a bank payment or debt closure. Return created, edited, and unfinished items with reasons.\n"
Full snapshot data
{
"description": "Use when the user asks to settle with a person, pay a debt, transfer money, or close a balance on a project.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 43
}
],
"name": "settlements-and-transfers",
"skill_md_contents": "---\nname: settlements-and-transfers\ndescription: Use when the user asks to settle with a person, pay a debt, transfer money, or close a balance on a project.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n - settlements.calculate\n - transfers.create\n - transfers.edit\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - whoami\n - list_projects\n - list_contractors\n - list_contractor_project_balances\n - create_payment_record\noptional_tools:\n - edit_payment_record\n - get_company_fund\n - list_company_fund_members\n - search_users\n - list_project_members\n - get_project_fund_settlements\n - get_event\n - list_events\n - get_project_summary\nresources:\n - path: ../shared-resources/context-and-identity.md\n kind: semantic-guide\n required: true\n - path: ../shared-resources/finance-and-balances.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\ncompletion:\n statuses:\n - готово\n - частично\n - заблокировано\n---\n\n# Settlements and Transfers\n\nCarry out an explicit request to settle, create, or edit a transfer. A general audit belongs to analytics.\n\n## Calculation\n\n1. Resolve the company, participant, and scope through `entity-resolution`: a project or the company fund. Clarify an ambiguous scope; do not require a project for a fund transfer. With several funds, determine the fund from `funds` in `get_company_fund`. Project balances come from `list_contractor_project_balances`; fund balances come from `get_company_fund` and `list_company_fund_members`. If you use `list_project_members`, always pair it with `get_project_fund_settlements` for the same project; signs and partial data are covered in `../shared-resources/finance-and-balances.md`.\n2. Close a negative own balance with an own-funds transfer and a negative accountable balance with an accountable-funds transfer. If both are negative, show two rows in one plan.\n3. A positive accountable balance can cover a negative own balance through a participant's self-transfer. Explain this part; do not create a self-transfer on someone else's behalf. Recommend an external transfer only for the remainder.\n4. A project cash shortage does not by itself prohibit a payment. Show the resulting deficit, obtain consent to that plan, and recommend an inflow from the customer. There is no system command to request money.\n\n## Writing\n\n- Apply `write-preflight`. Pass the exact subtype from the creation form, the amount, participants, and a Unix date in seconds.\n- `create_payment_record`: specify the project only through `projectShare`; for one project, use a 100% share. There is no separate project field. Attachments are server identifiers in `fileList`.\n- A transfer between funds uses subtype `company_fund_transfer`: `fundGuid` is the source (empty means the main fund), `targetFundGuid` is a different receiving fund, and `senderGuid` is the person holding the money; no `projectShare`.\n- `edit_payment_record`: first read `get_event`; pass `guid` and only changed fields. An explicit `null` clears a permitted field; preserve complete share and attachment lists when replacing them. Delete through `isDeleted` only on an explicit request.\n- Execute related transfers sequentially after an understandable plan and standard confirmation. Preserve each row's result; an unknown outcome or denial stops the remainder. Recover according to `../shared-resources/events-and-positions.md`.\n\nAfter a write, check `get_event` and fresh balances. `not_verified` means awaiting confirmation; the event does not prove a bank payment or debt closure. Return created, edited, and unfinished items with reasons.\n"
}SHA-256 of public snapshot: b7a047423916957fc8480f19e8dff45ec9d6a1f669d97f18c6b3272ab2cb8ab1