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 prepare-daily-receivables-brief

Skill instructions — Now says: `list-communications` (filtered on that date range, incoming and outgoing at once),

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

Save Billabex and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Sep 30, 2026 · 22:58 UTC

`list-incoming-communications`, `list-outgoing-communications`,

After

Nov 3, 2026 · 18:30 UTC

`list-communications` (filtered on that date range, incoming and outgoing at once),

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -6,7 +6,7 @@
 # Prepare Daily Receivables Brief
 
 1. Resolve the organization with `list-organizations` only when the context does not identify it.
-2. Read the last 24 hours with `list-incoming-communications`, `list-outgoing-communications`, `list-invoices`, `list-account-tasks`, and `list-customer-balances` as needed.
+2. Read the last 24 hours with `list-communications` (filtered on that date range, incoming and outgoing at once), `list-invoices`, `list-account-tasks`, and `list-customer-balances` as needed.
 3. Summarize payments received, newly overdue invoices, customer replies, future emails already scheduled by Billabex, and tasks created because the agent needs user input.
 4. Rank today's actions by urgency, financial exposure, and what is blocking the autonomous payment follow-up.

Full technical diff · 1 changed fields

changed `/skill_md_contents`

BEFORE

"---\nname: prepare-daily-receivables-brief\ndescription: Prepare a daily customer receivables brief covering changes from the last 24 hours, open tasks, payments, newly overdue invoices, and today's priorities. Use for daily brief, morning review, or changes since yesterday.\n---\n\n# Prepare Daily Receivables Brief\n\n1. Resolve the organization with `list-organizations` only when the context does not identify it.\n2. Read the last 24 hours with `list-incoming-communications`, `list-outgoing-communications`, `list-invoices`, `list-account-tasks`, and `list-customer-balances` as needed.\n3. Summarize payments received, newly overdue invoices, customer replies, future emails already scheduled by Billabex, and tasks created because the agent needs user input.\n4. Rank today's actions by urgency, financial exposure, and what is blocking the autonomous payment follow-up.\n\nKeep this workflow read-only. Call a write tool only after the user explicitly requests that exact action and the target is unambiguous.\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: prepare-daily-receivables-brief\ndescription: Prepare a daily customer receivables brief covering changes from the last 24 hours, open tasks, payments, newly overdue invoices, and today's priorities. Use for daily brief, morning review, or changes since yesterday.\n---\n\n# Prepare Daily Receivables Brief\n\n1. Resolve the organization with `list-organizations` only when the context does not identify it.\n2. Read the last 24 hours with `list-communications` (filtered on that date range, incoming and outgoing at once), `list-invoices`, `list-account-tasks`, and `list-customer-balances` as needed.\n3. Summarize payments received, newly overdue invoices, customer replies, future emails already scheduled by Billabex, and tasks created because the agent needs user input.\n4. Rank today's actions by urgency, financial exposure, and what is blocking the autonomous payment follow-up.\n\nKeep this workflow read-only. Call a write tool only after the user explicitly requests that exact action and the target is unambiguous.\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": "Prepare a daily customer receivables brief covering changes from the last 24 hours, open tasks, payments, newly overdue invoices, and today's priorities. Use for daily brief, morning review, or changes since yesterday.",
"included_files": [],
"name": "prepare-daily-receivables-brief",
"skill_md_contents": "---\nname: prepare-daily-receivables-brief\ndescription: Prepare a daily customer receivables brief covering changes from the last 24 hours, open tasks, payments, newly overdue invoices, and today's priorities. Use for daily brief, morning review, or changes since yesterday.\n---\n\n# Prepare Daily Receivables Brief\n\n1. Resolve the organization with `list-organizations` only when the context does not identify it.\n2. Read the last 24 hours with `list-communications` (filtered on that date range, incoming and outgoing at once), `list-invoices`, `list-account-tasks`, and `list-customer-balances` as needed.\n3. Summarize payments received, newly overdue invoices, customer replies, future emails already scheduled by Billabex, and tasks created because the agent needs user input.\n4. Rank today's actions by urgency, financial exposure, and what is blocking the autonomous payment follow-up.\n\nKeep this workflow read-only. Call a write tool only after the user explicitly requests that exact action and the target is unambiguous.\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: d06d1d69295456592f00e61017d1a8cf4b10c4032b6fbc41394a1e7f74e2b137