← BillabexCONTENT HISTORY

Update to Billabex

Snapshot Oct 24, 2026 · 13:05 UTC · version 2.0.2

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 prepare-payment-follow-up-email

Skill instructions — Now says: an independent third party acting

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:58 UTC

Revoptim acting as a third party

After

Oct 24, 2026 · 13:05 UTC

an independent third party acting

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -6,7 +6,7 @@
 # Prepare Payment Follow-up Email
 
 1. Resolve the organization with `list-organizations` when needed and use `get-organization` to retrieve the current Billabex agent's exact name. Find one customer with `list-accounts`, then review its balance, invoices, contacts, recent communications, and open tasks as needed.
-2. Draft a concise, diplomatic email in the current agent's name, as Revoptim acting as a third party on behalf of the organization. Use first-person singular and never imply membership in the organization.
+2. Draft a concise, diplomatic email in the current agent's name, as an independent third party acting on behalf of the organization. Use first-person singular and never imply membership in the organization.
 3. Copy proper names, invoice references, amounts, currencies, and dates exactly from the retrieved data. Do not invent a deadline or commitment.
 4. Do not add a signature because `send-outgoing-communication` adds it automatically.
 5. Treat drafting as read-only. Send only after the user explicitly approves the complete recipients, subject, body, and unambiguous customer account.
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: prepare-payment-follow-up-email\ndescription: Prepare a professional payment follow-up email from the customer account, invoice, contact, and communication history, and send it only after explicit approval. Use for drafting or sending a payment reminder or customer follow-up.\n---\n\n# Prepare Payment Follow-up Email\n\n1. Resolve the organization with `list-organizations` when needed and use `get-organization` to retrieve the current Billabex agent's exact name. Find one customer with `list-accounts`, then review its balance, invoices, contacts, recent communications, and open tasks as needed.\n2. Draft a concise, diplomatic email in the current agent's name, as Revoptim acting as a third party on behalf of the organization. Use first-person singular and never imply membership in the organization.\n3. Copy proper names, invoice references, amounts, currencies, and dates exactly from the retrieved data. Do not invent a deadline or commitment.\n4. Do not add a signature because `send-outgoing-communication` adds it automatically.\n5. Treat drafting as read-only. Send only after the user explicitly approves the complete recipients, subject, body, and unambiguous customer account.\n\nRespond in the language requested for the email. Otherwise use the language of the user's latest request. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
AFTER
"---\nname: prepare-payment-follow-up-email\ndescription: Prepare a professional payment follow-up email from the customer account, invoice, contact, and communication history, and send it only after explicit approval. Use for drafting or sending a payment reminder or customer follow-up.\n---\n\n# Prepare Payment Follow-up Email\n\n1. Resolve the organization with `list-organizations` when needed and use `get-organization` to retrieve the current Billabex agent's exact name. Find one customer with `list-accounts`, then review its balance, invoices, contacts, recent communications, and open tasks as needed.\n2. Draft a concise, diplomatic email in the current agent's name, as an independent third party acting on behalf of the organization. Use first-person singular and never imply membership in the organization.\n3. Copy proper names, invoice references, amounts, currencies, and dates exactly from the retrieved data. Do not invent a deadline or commitment.\n4. Do not add a signature because `send-outgoing-communication` adds it automatically.\n5. Treat drafting as read-only. Send only after the user explicitly approves the complete recipients, subject, body, and unambiguous customer account.\n\nRespond in the language requested for the email. Otherwise use the language of the user's latest request. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
Full snapshot data
{
  "description": "Prepare a professional payment follow-up email from the customer account, invoice, contact, and communication history, and send it only after explicit approval. Use for drafting or sending a payment reminder or customer follow-up.",
  "included_files": [],
  "name": "prepare-payment-follow-up-email",
  "skill_md_contents": "---\nname: prepare-payment-follow-up-email\ndescription: Prepare a professional payment follow-up email from the customer account, invoice, contact, and communication history, and send it only after explicit approval. Use for drafting or sending a payment reminder or customer follow-up.\n---\n\n# Prepare Payment Follow-up Email\n\n1. Resolve the organization with `list-organizations` when needed and use `get-organization` to retrieve the current Billabex agent's exact name. Find one customer with `list-accounts`, then review its balance, invoices, contacts, recent communications, and open tasks as needed.\n2. Draft a concise, diplomatic email in the current agent's name, as an independent third party acting on behalf of the organization. Use first-person singular and never imply membership in the organization.\n3. Copy proper names, invoice references, amounts, currencies, and dates exactly from the retrieved data. Do not invent a deadline or commitment.\n4. Do not add a signature because `send-outgoing-communication` adds it automatically.\n5. Treat drafting as read-only. Send only after the user explicitly approves the complete recipients, subject, body, and unambiguous customer account.\n\nRespond in the language requested for the email. Otherwise use the language of the user's latest request. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
}

SHA-256 of public snapshot: 3d18038d39570f53a53fc927bb683838753bc8193fc39a40cbba2b7c3413e80c