hashgraph-online/awesome-codex-plugins / plugins/candorsystems/candor-finance/skills/candor-find-money
candor-find-money
VerifiedFinds money the person is losing or is owed, gets it back with their okay, and has Candor watch the records until it lands. Use when they ask "am I overpaying?", spot a double charge, a fee, a refund or reimbursement that never came, a charge after cancelling, a bill that went up, a subscription they forgot, a free trial about to bill, or a paycheck that is late, short, or missing. For which charges repeat or how they are categorized, use candor-sort-transactions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.5 KB |
| references/getting-it-back.md | markdown | 3.1 KB |
| references/impacts.md | markdown | 2.5 KB |
| references/income-checks.md | markdown | 2.2 KB |
| references/sweep-and-test.md | markdown | 3.5 KB |
references/sweep-and-test.md
View on GitHub> The calls below are Candor MCP tool calls. Replace placeholders such as `TRANSACTION_ID` with values from earlier responses; where an `input` names an operation instead of showing an object, `candor_schema` lists its fields.
# Sweep and test
Use when the person asks you to find money rather than naming a charge.
## Set the window
```text
candor_get({
"operation": "coverage.get",
"reason": "Check which accounts and months the sweep can see"
})
```
Sweep the months coverage supports, usually the last 3 to 12. The first and
last transaction you see are not the coverage boundary. Name the accounts and
months you could not see in the answer.
## Read every page
```text
candor_get({
"operation": "transactions.list",
"reason": "Read the sweep window",
"args": {
"since": "START",
"until": "END",
"limit": 100
}
})
```
Follow each `next_actions` continuation and keep only counts and the few
candidates you need next as pages arrive (if you can run code, save the
pages and analyze them there). A page total covers that page only.
## Patterns and comparators
| Pattern | Looks like | Comparator that makes it real |
| --- | --- | --- |
| Duplicate | Same merchant, same amount, same or next day | The merchant's other periods show one charge; no refund followed |
| Repeat fee | Overdraft, late, foreign, ATM, maintenance fees | Earlier occurrences, and the account terms that set the fee |
| Missing credit | A large or unusual debit with no later inflow | A similar past debit that did get a refund or reimbursement |
| Charge after cancel | A recurring payee posting after a known end date | The cancellation date from a confirmation or a note |
| Price increase | A series with `price_changed_at` set | The postings before and after, at the same cadence |
| Forgotten service | A subscription-shaped series the person does not mention | Ask; do not decide it is unwanted |
| Trial converting | A small authorization, then a first full charge | The trial terms from the signup confirmation |
Subscription-shaped means `direction` outflow with `cashflow_role` expense.
Transfers, debt payments, and refunds are not subscriptions however regular
they look. Text and category are signals, never proof.
## Testing one candidate
```text
candor_get({
"operation": "transactions.get",
"reason": "Read the exact candidate",
"args": {
"transaction_id": "TRANSACTION_ID"
}
})
candor_get({
"operation": "transactions.list",
"reason": "Compare the merchant's other charges",
"args": {
"merchant": "MERCHANT",
"since": "START",
"until": "END",
"limit": 100
}
})
candor_get({
"operation": "recurring.get",
"reason": "Read the series behind a recurring candidate",
"args": {
"recurring_item_id": "RECURRING_ITEM_ID"
}
})
candor_get({
"operation": "transactions.list",
"reason": "Read every posting of the series",
"args": {
"recurring_item_id": "RECURRING_ITEM_ID"
}
})
```
For each candidate, compare posted versus pending, date, amount, currency,
account, description, and any refund or reversal. Classify it as supported,
explained (say why), or not enough evidence. Keep only supported ones for
the person.
A series keeps only its newest postings (`last_paid_at`, `last_amount`); the
series read above returns every posting under each name the bank used. Check
amounts against `price_levels`: another plan from the same payee can appear.
## Ranking
Lead with money already lost and recoverable, then ongoing costs (a yearly
figure only when the cadence is real), then deadlines like a trial ending.
Three solid findings beat ten maybes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |