← BillabexCONTENT HISTORY

Update to Billabex

Snapshot Nov 3, 2026 · 18:30 UTC · version 2.0.3

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for adjust-scheduled-follow-ups

Skill instructions — Now says: `list-communications` with the account and `type` `OutgoingEmail`, and `get-communication` on the matching row, to identify the exact unsent email. 5. Use...

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

Save Billabex and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Sep 30, 2026 · 22:57 UTC

`list-outgoing-communications-by-account` and `get-outgoing-communication` to identify the exact unsent email. 5. Use `update-outgoing-communication` only after explicit approval of the unambiguous email and exact changes. Update multipl...

After

Nov 3, 2026 · 18:30 UTC

`list-communications` with the account and `type` `OutgoingEmail`, and `get-communication` on the matching row, to identify the exact unsent email. 5. Use `update-outgoing-communication` only after explicit approval of the unambiguous em...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -5,11 +5,11 @@
 
 # Adjust Scheduled Follow-ups
 
-1. Resolve the organization if needed, find the customer with `list-accounts`, then use `list-outgoing-communications-by-account` and `get-outgoing-communication` to identify the exact unsent email.
+1. Resolve the organization if needed, find the customer with `list-accounts`, then use `list-communications` with the account and `type` `OutgoingEmail`, and `get-communication` on the matching row, to identify the exact unsent email.
 2. Show the customer, current scheduled date, recipients, subject, and content before proposing a change.
 3. Treat a tone request as an edit to the selected scheduled emails, not as a persistent account preference. Preserve facts, amounts, invoice references, commitments, and the agent's third-party identity.
 4. Preview the exact new date or email content. Do not include a signature because Billabex adds the current agent's signature automatically.
-5. Use `update-outgoing-communication` only after explicit approval of the unambiguous email and exact changes. Update multiple emails one by one only when the user clearly approves the full list.
+5. Use `update-outgoing-communication` only after explicit approval of the unambiguous email and exact changes. Update multiple emails one by one only when the user clearly approves the full list. The update answers with a short confirmation, not the email: to show the saved version, read it again with `get-communication`.
 6. If no future email exists, explain that this workflow cannot create one and do not send an immediate email instead.
 
 Respond in the language of the user's latest request. Copy proper names exactly. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: adjust-scheduled-follow-ups\ndescription: Review and adjust future Billabex payment follow-up emails for selected customer accounts. Use to change a scheduled send date, recipient, subject, language, wording, or tone before an email is sent.\n---\n\n# Adjust Scheduled Follow-ups\n\n1. Resolve the organization if needed, find the customer with `list-accounts`, then use `list-outgoing-communications-by-account` and `get-outgoing-communication` to identify the exact unsent email.\n2. Show the customer, current scheduled date, recipients, subject, and content before proposing a change.\n3. Treat a tone request as an edit to the selected scheduled emails, not as a persistent account preference. Preserve facts, amounts, invoice references, commitments, and the agent's third-party identity.\n4. Preview the exact new date or email content. Do not include a signature because Billabex adds the current agent's signature automatically.\n5. Use `update-outgoing-communication` only after explicit approval of the unambiguous email and exact changes. Update multiple emails one by one only when the user clearly approves the full list.\n6. If no future email exists, explain that this workflow cannot create one and do not send an immediate email instead.\n\nRespond in the language of the user's latest request. Copy proper names exactly. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
AFTER
"---\nname: adjust-scheduled-follow-ups\ndescription: Review and adjust future Billabex payment follow-up emails for selected customer accounts. Use to change a scheduled send date, recipient, subject, language, wording, or tone before an email is sent.\n---\n\n# Adjust Scheduled Follow-ups\n\n1. Resolve the organization if needed, find the customer with `list-accounts`, then use `list-communications` with the account and `type` `OutgoingEmail`, and `get-communication` on the matching row, to identify the exact unsent email.\n2. Show the customer, current scheduled date, recipients, subject, and content before proposing a change.\n3. Treat a tone request as an edit to the selected scheduled emails, not as a persistent account preference. Preserve facts, amounts, invoice references, commitments, and the agent's third-party identity.\n4. Preview the exact new date or email content. Do not include a signature because Billabex adds the current agent's signature automatically.\n5. Use `update-outgoing-communication` only after explicit approval of the unambiguous email and exact changes. Update multiple emails one by one only when the user clearly approves the full list. The update answers with a short confirmation, not the email: to show the saved version, read it again with `get-communication`.\n6. If no future email exists, explain that this workflow cannot create one and do not send an immediate email instead.\n\nRespond in the language of the user's latest request. Copy proper names exactly. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
Full snapshot data
{
  "description": "Review and adjust future Billabex payment follow-up emails for selected customer accounts. Use to change a scheduled send date, recipient, subject, language, wording, or tone before an email is sent.",
  "included_files": [],
  "name": "adjust-scheduled-follow-ups",
  "skill_md_contents": "---\nname: adjust-scheduled-follow-ups\ndescription: Review and adjust future Billabex payment follow-up emails for selected customer accounts. Use to change a scheduled send date, recipient, subject, language, wording, or tone before an email is sent.\n---\n\n# Adjust Scheduled Follow-ups\n\n1. Resolve the organization if needed, find the customer with `list-accounts`, then use `list-communications` with the account and `type` `OutgoingEmail`, and `get-communication` on the matching row, to identify the exact unsent email.\n2. Show the customer, current scheduled date, recipients, subject, and content before proposing a change.\n3. Treat a tone request as an edit to the selected scheduled emails, not as a persistent account preference. Preserve facts, amounts, invoice references, commitments, and the agent's third-party identity.\n4. Preview the exact new date or email content. Do not include a signature because Billabex adds the current agent's signature automatically.\n5. Use `update-outgoing-communication` only after explicit approval of the unambiguous email and exact changes. Update multiple emails one by one only when the user clearly approves the full list. The update answers with a short confirmation, not the email: to show the saved version, read it again with `get-communication`.\n6. If no future email exists, explain that this workflow cannot create one and do not send an immediate email instead.\n\nRespond in the language of the user's latest request. Copy proper names exactly. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
}

SHA-256 of public snapshot: 58b91f912b3e51a0edecd319dea17b313d54dfeecf7767cb414e8d7be8b98c13