Update to ClarityTrack

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

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for money_story

Skill instructions — Now says: 1. Call dashboard.monthly. 2. For the day-to-day change in connected balances, call changes.recent. Write the answer in plain text. Use no emoji, coloured...

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

1. Call get_my_monthly_dashboard. 2. For the day-to-day change in connected balances, call get_what_changed.

After

Oct 28, 2026 · 12:27 UTC

1. Call dashboard.monthly. 2. For the day-to-day change in connected balances, call changes.recent. 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,...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -5,7 +5,9 @@
 
 Use this when the user asks for this month's money story.
 
-1. Call get_my_monthly_dashboard.
-2. For the day-to-day change in connected balances, call get_what_changed.
+1. Call dashboard.monthly.
+2. For the day-to-day change in connected balances, call changes.recent.
 3. Write a short story under 250 words: what happened, how spending sits against budgets, what Clarity has been flagging, and the single most useful next step.
 4. Use the numbers exactly as returned. Do not invent a change. 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: money_story\ndescription: Tell a short plain-English story of this month: what happened, what changed, and the one useful next step.\n---\n\nUse this when the user asks for this month's money story.\n\n1. Call get_my_monthly_dashboard.\n2. For the day-to-day change in connected balances, call get_what_changed.\n3. Write a short story under 250 words: what happened, how spending sits against budgets, what Clarity has been flagging, and the single most useful next step.\n4. Use the numbers exactly as returned. Do not invent a change. Nothing moves money.\n"

AFTER

"---\nname: money_story\ndescription: Tell a short plain-English story of this month: what happened, what changed, and the one useful next step.\n---\n\nUse this when the user asks for this month's money story.\n\n1. Call dashboard.monthly.\n2. For the day-to-day change in connected balances, call changes.recent.\n3. Write a short story under 250 words: what happened, how spending sits against budgets, what Clarity has been flagging, and the single most useful next step.\n4. Use the numbers exactly as returned. Do not invent a change. 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": "Tell a short plain-English story of this month: what happened, what changed, and the one useful next step.",
  "included_files": [],
  "name": "money_story",
  "skill_md_contents": "---\nname: money_story\ndescription: Tell a short plain-English story of this month: what happened, what changed, and the one useful next step.\n---\n\nUse this when the user asks for this month's money story.\n\n1. Call dashboard.monthly.\n2. For the day-to-day change in connected balances, call changes.recent.\n3. Write a short story under 250 words: what happened, how spending sits against budgets, what Clarity has been flagging, and the single most useful next step.\n4. Use the numbers exactly as returned. Do not invent a change. 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: f7e3b60fb623d5978db40a38458fc58881f15435e408fd52cd9aca73bef8a991