Skill instructions
budget_check679 Bytes
View saved version →
---
name: budget_check
description: Compare this month's spending against budgets and flag anything over or near its cap.
---
Use this when the user asks how spending sits against their budgets.
1. Call budgets.list and summary.financial.
2. Compare month-to-date spending against each budget cap. Flag anything over budget or above 80 percent of its cap.
3. If has_budgets is false, say no budgets are set yet. Do not invent budget numbers.
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.
daily_snapshot643 Bytes
View saved version →
---
name: daily_snapshot
description: Show what changed across connected accounts since the previous daily snapshot.
---
Use this when the user asks what changed since yesterday or wants the daily snapshot.
1. Call changes.recent.
2. Summarize the connected net worth change and the account changes the tool returned.
3. If there is no snapshot yet, say so in the tool's own words. Do not invent a change.
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.
duplicate_charges609 Bytes
View saved version →
---
name: duplicate_charges
description: List open charges that look like the same charge on two accounts.
---
Use this when the user asks whether the same charge shows on two accounts.
1. Call spending.duplicates.
2. List any open duplicate charges with the merchant and the amount.
3. If the list is empty, say there are no open duplicate charges.
4. Do not mark one intentional. That happens in ClarityTrack. 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.
insight_trend592 Bytes
View saved version →
---
name: insight_trend
description: Review what Clarity has been flagging in recent insights and whether the picture is improving or worsening.
---
Use this when the user asks what Clarity has been flagging.
1. Call insights.list with limit 5.
2. Summarize the insights, newest first, and whether the picture is improving or worsening.
3. Do not invent an insight that the tool did not return. 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.
money_story725 Bytes
View saved version →
---
name: money_story
description: Tell a short plain-English story of this month: what happened, what changed, and the one useful next step.
---
Use this when the user asks for this month's money story.
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.
monthly_money_dashboard696 Bytes
View saved version →
---
name: monthly_money_dashboard
description: Build a one-page dashboard of this month's money: net worth, spending by category, budget status, and what Clarity has been flagging.
---
Use this when the user asks to see their month or wants the dashboard.
1. Call dashboard.monthly.
2. Start with what Clarity itself has been flagging, then present the summary cards, spending by category, and budget status.
3. Mention the data coverage and freshness notes.
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.
owner_money1.1 KB
View saved version →
---
name: owner_money
description: Business cash on hand, what is committed, what is left, and owner's pay. Personal cash is not included.
---
Use this when the user asks about business cash or what they paid themselves from the business. This is not a monthly profit figure.
1. Call business.coverage.
2. For each business context, say cash on hand, what is committed in the window, and what is left, using the tool's own figures.
3. When ownerPay is present, also say what they paid themselves, money they put into the business, and the pay pattern, using the tool's labels and figures. Call a draw pay. Do not call it income or salary. Do not invent a tax figure or a monthly profit.
4. If ownerPay is absent, do not invent pay.
5. If items is empty, say there is no business cash figure because no business account is tagged or the read did not complete. Do not turn an empty list into zero. Personal cash is not in this tool. 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.
plan_check673 Bytes
View saved version →
---
name: plan_check
description: Score payoff and savings goals as ahead, on track, or behind, and say how fresh the balances are.
---
Use this when the user asks how they are doing against their plan, or wants a goal scoreboard.
1. Call plan.scoreboard.
2. Tell the user where each payoff or savings goal stands, in the card's own words, and say how fresh the balances are.
3. If a goal is not scored, say that. Do not invent a pace.
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.
setup877 Bytes
View saved version →
---
name: setup
description: Connect ClarityTrack, then offer the home questions.
---
The user's own request outranks these steps.
1. If ClarityTrack is not connected, ask the user to connect it. Do not invent balances, goals, or charges.
2. Once it is connected, offer these questions: how am I doing against my plan, what changed since yesterday, is this month's spending ahead of my plan, do I have the same charge on two accounts, did that charge stop, and how is the business cash.
3. Use the numbers the tools return. Do not recompute totals from raw transactions when a tool provides calculated values.
4. Nothing moves money. Do not mark a duplicate intentional. That happens in ClarityTrack.
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.
spending_by_category691 Bytes
View saved version →
---
name: spending_by_category
description: Chart spending by category for a date window, largest first.
---
Use this when the user asks where their money went by category. This is category totals, not the spending pace card.
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 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.
spending_pace667 Bytes
View saved version →
---
name: spending_pace
description: Say whether this month's spending is ahead of the plan, with last month beside it.
---
Use this when the user asks if this month is ahead of the plan. This is the pace card, not category totals.
1. Call spending.pace. If the user names a month, pass it as YYYY-MM. Otherwise omit month.
2. Say whether this month is ahead of the plan, behind it, or even with it, using the tool's own verdict.
3. 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.
subscription_follow_through948 Bytes
View saved version →
---
name: subscription_follow_through
description: Whether a cancelled subscription's charge actually stopped, or a charge posted after the cancellation.
---
Use this when the user asks whether a cancelled subscription's charge stopped.
1. Call subscriptions.follow_through. Do not use subscription.status. That tool is the ClarityTrack plan tier.
2. Say the charge stopped only when a request status is confirmed_stopped.
3. charge_detected means a charge posted after the request. committed means it is still waiting. A missing charge before the next bill date is not a stop.
4. chargedAfterCancellation means a charge posted after the stream was marked cancelled.
5. If there is no cancelled stream and no request, say there is nothing to confirm. 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.
