← ClarityTrackCONTENT HISTORY

Update to ClarityTrack

Snapshot Oct 28, 2026 · 12:27 UTC · version 8.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for spending_by_category

Skill instructions — Now says: spending.by_category. Pass since and until only when the user gives those dates, as YYYY-MM-DD. 3. For whether this month is ahead of the plan, call...

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

Save ClarityTrack and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 25, 2026 · 00:04 UTC

get_my_spending_by_category. Pass since and until only when the user gives those dates, as YYYY-MM-DD. 3. For whether this month is ahead of the plan, call get_my_spending_pace instead.

After

Oct 28, 2026 · 12:27 UTC

spending.by_category. Pass since and until only when the user gives those dates, as YYYY-MM-DD. 3. For whether this month is ahead of the plan, call spending.pace instead. Write the answer in plain text. Use no emoji, coloured dots, chec...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -5,7 +5,9 @@
 
 Use this when the user asks where their money went by category. This is category totals, not the spending pace card.
 
-1. Call get_my_spending_by_category. Pass since and until only when the user gives those dates, as YYYY-MM-DD.
+1. Call spending.by_category. Pass since and until only when the user gives those dates, as YYYY-MM-DD.
 2. Present spending by category, largest first.
-3. For whether this month is ahead of the plan, call get_my_spending_pace instead.
+3. For whether this month is ahead of the plan, call spending.pace instead.
 4. Use the numbers exactly as returned. Nothing moves money.
+
+Write the answer in plain text. Use no emoji, coloured dots, check marks or other symbols, and no em or en dashes. Say a status in words, such as ahead, on track or behind.
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: spending_by_category\ndescription: Chart spending by category for a date window, largest first.\n---\n\nUse this when the user asks where their money went by category. This is category totals, not the spending pace card.\n\n1. Call get_my_spending_by_category. Pass since and until only when the user gives those dates, as YYYY-MM-DD.\n2. Present spending by category, largest first.\n3. For whether this month is ahead of the plan, call get_my_spending_pace instead.\n4. Use the numbers exactly as returned. Nothing moves money.\n"
AFTER
"---\nname: spending_by_category\ndescription: Chart spending by category for a date window, largest first.\n---\n\nUse this when the user asks where their money went by category. This is category totals, not the spending pace card.\n\n1. Call spending.by_category. Pass since and until only when the user gives those dates, as YYYY-MM-DD.\n2. Present spending by category, largest first.\n3. For whether this month is ahead of the plan, call spending.pace instead.\n4. Use the numbers exactly as returned. Nothing moves money.\n\nWrite the answer in plain text. Use no emoji, coloured dots, check marks or other symbols, and no em or en dashes. Say a status in words, such as ahead, on track or behind.\n"
Full snapshot data
{
  "description": "Chart spending by category for a date window, largest first.",
  "included_files": [],
  "name": "spending_by_category",
  "skill_md_contents": "---\nname: spending_by_category\ndescription: Chart spending by category for a date window, largest first.\n---\n\nUse this when the user asks where their money went by category. This is category totals, not the spending pace card.\n\n1. Call spending.by_category. Pass since and until only when the user gives those dates, as YYYY-MM-DD.\n2. Present spending by category, largest first.\n3. For whether this month is ahead of the plan, call spending.pace instead.\n4. Use the numbers exactly as returned. Nothing moves money.\n\nWrite the answer in plain text. Use no emoji, coloured dots, check marks or other symbols, and no em or en dashes. Say a status in words, such as ahead, on track or behind.\n"
}

SHA-256 of public snapshot: 3d8be35449162cb40145e00b63b9ebf0455401d70365a3e29ed547b2b6ce83f8