{"id":99108,"plugin_id":"plugin_asdk_app_6aea7d3759488191b45a1559b87e9827","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T18:16:43.717Z","digest":"17b44e3b3e74fab7d173145a227bee74761c8ab3d38c376de6b3fda3ce1b57ae","against":null,"payload":{"description":"Correct explicitly identified Futoroku financial records or delete confirmed targets while checking identities, current revisions and reimbursement effects.","included_files":[{"relative_path":"references/mcp-safety.md","size_in_bytes":4224}],"name":"correct-record","skill_md_contents":"---\nname: correct-record\ndescription: Correct explicitly identified Futoroku financial records or delete confirmed targets while checking identities, current revisions and reimbursement effects.\n---\n\nRead [the shared MCP contract](references/mcp-safety.md). Resolve the approved Space, find candidates with `search_transactions`, then use `get_transaction_record` to read each exact target. Ask the user to select when candidates are ambiguous. A statement, receipt suggestion or search match does not independently authorize an edit.\n\nFor an authorized edit, use `update_transaction_record` with `update.transaction_id`, the freshly returned `expected_updated_at` and only requested fields in `update.changes`. Omission preserves a field; blank tag/remark clears it, and explicit null can have a distinct effect. Do not send a whole record as a patch. Transaction type cannot change; income/expense currency cannot change through this edit. Transfer account/currency changes must satisfy the exact received-leg rules. Never work around validation by deleting and recreating a record without a separate request.\n\nFor 1–100 explicitly reviewed records, `update_transaction_records` performs an atomic batch. Keep an individual current revision per item. Changes must satisfy reimbursement constraints in request order; review their consequences instead of quietly removing linked income. Do not fan out writes after an atomic failure.\n\nBefore permanent deletion, show the exact IDs, dates, amounts and consequences and obtain explicit confirmation for those records. Then re-read their identities/revisions and call `delete_transaction_records` with each `transaction_id`, `client_uuid`, `expected_updated_at`, `confirmed: true`, explicit `space_id` and a retained UUID `request_id`. Linked reimbursements can block expense deletion; discuss the separate requested action. Never delete a suspected duplicate merely because it looks similar.\n\nTo link an existing received income, review both records and timestamps, obtain confirmation, then use `link_received_reimbursement`. To remove a received reimbursement use the tool's reviewed identities, timestamps and confirmation; explain that it deletes the linked income and changes reports. Do not record expected future money as received.\n\nOn `stale_revision`, stale identity or a changed relationship, re-read, present the changed state and obtain renewed review before constructing a new operation with a new UUID. On an uncertain acknowledgement, keep the original UUID, Space and exact arguments; do not change the request or switch Spaces. Report only confirmed outcomes and include the resulting record ID or deleted IDs.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}