← BriefcaseCONTENT HISTORY

Update to Briefcase

Snapshot Oct 3, 2026 · 12:02 UTC · version 1.3.0

Collection source: downloaded plugin package.

WHAT CHANGED · RULE-BASED ANALYSIS

Instructions updated for document-submission

Instruction wording changed from “office"). The response gives three routes:” to “office").”. 3 additional added or edited lines are in the evidence.

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

Skill instructions

Before

office"). The response gives three routes: - an archive as duplicate or not-a-transaction, with the reason;

After

office"). When the user attached the file in the conversation and your host passes attachments to tools (ChatGPT does), pass it as `file`. Briefcase downloads it itself and `next_step` says the file is already in Briefcase: go straight t...

Compare saved observations

Download comparison JSON
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: document-submission\ndescription: Submit a bill, receipt, bank statement or supplier statement to a Briefcase client, choosing between direct upload, a browser upload link and the client's forwarding email, then track processing to the resulting transaction. Use when the user shares a document or asks to upload, send or file something into Briefcase.\n---\n\n# Submitting documents to Briefcase\n\n## Choose the client\n\nResolve the client with `briefcase_list_clients` and confirm it with the user when the name is ambiguous. Ask for a business or property only when the client has more than one (`briefcase_get_reference_data` with `kind: businesses` or `properties`).\n\n## Prepare the upload\n\nCall `briefcase_create_document_upload` with the file name, MIME type, size if known, and the user's note (for example \"Pay from the deposit account\" or \"Split 60/40 with the Manchester office\"). The response gives three routes:\n\n1. **You can transfer the file.** `PUT` the original bytes to `upload_url` with the returned headers, then call `briefcase_submit_document` with the `upload_id` and a fresh `idempotency_key`.\n2. **You cannot transfer the file.** Give the user `browser_upload_url`. They open it, sign in, check the client and note, choose the file and press Upload. The link expires after one hour and only accepts the prepared file type.\n3. **Email.** Give the user `forwarding_email` and tell them to put the note in the email body.\n\nNever fabricate file contents and never submit a file the user did not provide.\n\n## Track processing\n\n`briefcase_submit_document` returns an operation. Poll `briefcase_get_operation` no more than once every few seconds until it reaches a final state, then report:\n\n- the transaction, bank statement or supplier statement that was created, with its status;\n- an archive as duplicate or not-a-transaction, with the reason;\n- a failure, with the message, and suggest re-uploading a clearer copy.\n\nOn Autopilot clients a submitted document may publish automatically. Say so before submitting when `briefcase_get_client` shows Autopilot is on.\n\n## Retries and refusals\n\nRetry a failed `briefcase_submit_document` with the same `idempotency_key`; Briefcase will not create a second candidate. A `FORBIDDEN` result means the user cannot upload for this client or assistant changes are paused. `VALIDATION_ERROR` on file type or size means the document must go through the app or email instead.\n"
AFTER
"---\nname: document-submission\ndescription: Submit a bill, receipt, bank statement or supplier statement to a Briefcase client, choosing between direct upload, a browser upload link and the client's forwarding email, then track processing to the resulting transaction. Use when the user shares a document or asks to upload, send or file something into Briefcase.\n---\n\n# Submitting documents to Briefcase\n\n## Choose the client\n\nResolve the client with `briefcase_list_clients` and confirm it with the user when the name is ambiguous. Ask for a business or property only when the client has more than one (`briefcase_get_reference_data` with `kind: businesses` or `properties`).\n\n## Prepare the upload\n\nCall `briefcase_create_document_upload` with the file name, MIME type, size if known, and the user's note (for example \"Pay from the deposit account\" or \"Split 60/40 with the Manchester office\").\n\nWhen the user attached the file in the conversation and your host passes attachments to tools (ChatGPT does), pass it as `file`. Briefcase downloads it itself and `next_step` says the file is already in Briefcase: go straight to `briefcase_submit_document` with the `upload_id` and a fresh `idempotency_key`.\n\nOtherwise the response gives three routes:\n\n1. **You can transfer the file.** `PUT` the original bytes to `upload_url` with the returned headers, then call `briefcase_submit_document` with the `upload_id` and a fresh `idempotency_key`.\n2. **You cannot transfer the file.** Give the user `browser_upload_url`. They open it, sign in, check the client and note, choose the file and press Upload. The link expires after one hour and only accepts the prepared file type.\n3. **Email.** Give the user `forwarding_email` and tell them to put the note in the email body.\n\nNever fabricate file contents and never submit a file the user did not provide.\n\n## Track processing\n\n`briefcase_submit_document` returns an operation. Poll `briefcase_get_operation` no more than once every few seconds until it reaches a final state, then report:\n\n- the transaction, bank statement or supplier statement that was created, with its status;\n- an archive as duplicate or not-a-transaction, with the reason. A created transaction marked `archived: true` was archived by duplicate detection; `briefcase_get_transaction` shows status `ARCHIVED` and a `POSSIBLE_DUPLICATE` warning naming the original;\n- a failure, with the message, and suggest re-uploading a clearer copy.\n\nOn Autopilot clients a submitted document may publish automatically. Say so before submitting when `briefcase_get_client` shows Autopilot is on.\n\n## Retries and refusals\n\nRetry a failed `briefcase_submit_document` with the same `idempotency_key`; Briefcase will not create a second candidate. A `FORBIDDEN` result means the user cannot upload for this client or assistant changes are paused. `VALIDATION_ERROR` on file type or size means the document must go through the app or email instead.\n"

SKILL.md line diff

--- before
+++ after
@@ -11,7 +11,11 @@
 
 ## Prepare the upload
 
-Call `briefcase_create_document_upload` with the file name, MIME type, size if known, and the user's note (for example "Pay from the deposit account" or "Split 60/40 with the Manchester office"). The response gives three routes:
+Call `briefcase_create_document_upload` with the file name, MIME type, size if known, and the user's note (for example "Pay from the deposit account" or "Split 60/40 with the Manchester office").
+
+When the user attached the file in the conversation and your host passes attachments to tools (ChatGPT does), pass it as `file`. Briefcase downloads it itself and `next_step` says the file is already in Briefcase: go straight to `briefcase_submit_document` with the `upload_id` and a fresh `idempotency_key`.
+
+Otherwise the response gives three routes:
 
 1. **You can transfer the file.** `PUT` the original bytes to `upload_url` with the returned headers, then call `briefcase_submit_document` with the `upload_id` and a fresh `idempotency_key`.
 2. **You cannot transfer the file.** Give the user `browser_upload_url`. They open it, sign in, check the client and note, choose the file and press Upload. The link expires after one hour and only accepts the prepared file type.
@@ -24,7 +28,7 @@
 `briefcase_submit_document` returns an operation. Poll `briefcase_get_operation` no more than once every few seconds until it reaches a final state, then report:
 
 - the transaction, bank statement or supplier statement that was created, with its status;
-- an archive as duplicate or not-a-transaction, with the reason;
+- an archive as duplicate or not-a-transaction, with the reason. A created transaction marked `archived: true` was archived by duplicate detection; `briefcase_get_transaction` shows status `ARCHIVED` and a `POSSIBLE_DUPLICATE` warning naming the original;
 - a failure, with the message, and suggest re-uploading a clearer copy.
 
 On Autopilot clients a submitted document may publish automatically. Say so before submitting when `briefcase_get_client` shows Autopilot is on.
Full snapshot data
{
  "description": "Submit a bill, receipt, bank statement or supplier statement to a Briefcase client, choosing between direct upload, a browser upload link and the client's forwarding email, then track processing to the resulting transaction. Use when the user shares a document or asks to upload, send or file something into Briefcase.",
  "included_files": [],
  "name": "document-submission",
  "skill_md_contents": "---\nname: document-submission\ndescription: Submit a bill, receipt, bank statement or supplier statement to a Briefcase client, choosing between direct upload, a browser upload link and the client's forwarding email, then track processing to the resulting transaction. Use when the user shares a document or asks to upload, send or file something into Briefcase.\n---\n\n# Submitting documents to Briefcase\n\n## Choose the client\n\nResolve the client with `briefcase_list_clients` and confirm it with the user when the name is ambiguous. Ask for a business or property only when the client has more than one (`briefcase_get_reference_data` with `kind: businesses` or `properties`).\n\n## Prepare the upload\n\nCall `briefcase_create_document_upload` with the file name, MIME type, size if known, and the user's note (for example \"Pay from the deposit account\" or \"Split 60/40 with the Manchester office\").\n\nWhen the user attached the file in the conversation and your host passes attachments to tools (ChatGPT does), pass it as `file`. Briefcase downloads it itself and `next_step` says the file is already in Briefcase: go straight to `briefcase_submit_document` with the `upload_id` and a fresh `idempotency_key`.\n\nOtherwise the response gives three routes:\n\n1. **You can transfer the file.** `PUT` the original bytes to `upload_url` with the returned headers, then call `briefcase_submit_document` with the `upload_id` and a fresh `idempotency_key`.\n2. **You cannot transfer the file.** Give the user `browser_upload_url`. They open it, sign in, check the client and note, choose the file and press Upload. The link expires after one hour and only accepts the prepared file type.\n3. **Email.** Give the user `forwarding_email` and tell them to put the note in the email body.\n\nNever fabricate file contents and never submit a file the user did not provide.\n\n## Track processing\n\n`briefcase_submit_document` returns an operation. Poll `briefcase_get_operation` no more than once every few seconds until it reaches a final state, then report:\n\n- the transaction, bank statement or supplier statement that was created, with its status;\n- an archive as duplicate or not-a-transaction, with the reason. A created transaction marked `archived: true` was archived by duplicate detection; `briefcase_get_transaction` shows status `ARCHIVED` and a `POSSIBLE_DUPLICATE` warning naming the original;\n- a failure, with the message, and suggest re-uploading a clearer copy.\n\nOn Autopilot clients a submitted document may publish automatically. Say so before submitting when `briefcase_get_client` shows Autopilot is on.\n\n## Retries and refusals\n\nRetry a failed `briefcase_submit_document` with the same `idempotency_key`; Briefcase will not create a second candidate. A `FORBIDDEN` result means the user cannot upload for this client or assistant changes are paused. `VALIDATION_ERROR` on file type or size means the document must go through the app or email instead.\n"
}

SHA-256 of public snapshot: 7169ee57f0379078af3f7a5afecc9519b8eb4351beba4cd3dd31b5af7d19aab9