candor-finance
Use Candor for personal finance: organize the user's accounts and spending, remember approved budgets and goals, review investments, investigate possible savings, and keep evidence and follow-up together. Use when a task touches the user's money, financial records, prior decisions, or approved plans. Skill: candor-finance Owner: candor Summary: Use Candor for personal finance: organize the user's accounts and spending, remember approved budgets and goals, review investments, investigate possible savings, and keep evidence and follow-up together. Use when a task touches the user's money, financial records, prior decisions, or approved plans. Tags: latest:0.1.162 Version history: v0.1.162 | 2026-10-03T22:01:52.943Z
Rank
62
Safety
84
Downloads
2.8k
Updated
Oct 9, 2026
Version
0.1.162
Source
CLAWHUB
About
What it does, and when to use it.
Capability contract not published. No trust telemetry is available yet. 2.8K downloads reported by the source. Last updated 10/9/2026.
Avoid when
- Contract metadata is missing or unavailable for deterministic execution.
Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing
Public facts
Every fact links back to the source it came from.
- Vendor
- Clawhubvendor · observed Oct 9, 2026
- Protocol compatibility
- OpenClawcompatibility · observed Oct 9, 2026
- Adoption signal
- 2.8K downloadsadoption · observed Oct 9, 2026
- Latest release
- 0.1.162release · observed Oct 3, 2026
- Handshake status
- UNKNOWNsecurity
Install and run
Setup complexity: low.
clawhub skill install s17favrchcarw6tn9b0qdv74918c7m59:candor-finance- Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
- Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.
Contract: missing
curl -s "https://www.xpersona.co/api/v1/agents/clawhub-candor-candor-finance/snapshot"
Documentation
CLAWHUB
160,000 characters of source documentation, loaded on request.
Extracted files
5 files captured from the source.
SKILL.md
---
name: candor-finance
description: "Use Candor for personal finance: organize the user's accounts and spending, remember approved budgets and goals, review investments, investigate possible savings, and keep evidence and follow-up together. Use when a task touches the user's money, financial records, prior decisions, or approved plans."
compatibility: Requires an authenticated Candor workspace and either the Candor tools included with the installed package or Candor CLI 0.3.143 or newer.
metadata:
author: Candor
version: 0.1.0
candor-skill-version: 2026-10-03
candor-cli: ">=0.3.143 <0.4.0"
candor-introduced-in: 2026-07-23
candor-updated-in: 2026-10-03
openclaw:
homepage: https://candor.money/START.md
requires:
bins:
- candor
homepage: https://candor.money/START.md
---
## Execute recipes through the Candor CLI
This OpenClaw package includes Candor's finance instructions while the public
`candor` CLI provides the tools. Execute the command recipes in this skill
through the local shell. Do not look for Candor MCP tools or hand commands back
to the user. The Candor CLI also maintains a digest-verified copy under
`~/.agents/skills` for its release preflight. OpenClaw resolves a same-named
workspace or shared package first, so these CLI-backed copies are compatible
and deterministic. If setup or the managed copy is incomplete, get started at
[https://candor.money/START.md](https://candor.money/START.md) and use its official
OpenClaw materials before continuing.
ClawHub distributes this skill at no charge under MIT-0. Operating the Candor
service requires a signed-in account and an active subscription; subscription
and payment changes happen only on secure Candor pages.
# Candor Finance
This file is already loaded from the selected Candor package. Use the Candor
tools supplied by the selected package to operate your financial memory for the user.
Candor stores facts, calculations, approved state and history. You interpret the
evidence, recommend what fits, and act within the authority the user gives you.
## Work from the user's goal
1. Open the workspace with `candor open`. Recover relevant context, approved
state, coverage, freshness and unfinished follow-through. Reuse evidence
already returned when it answers the question; inspect deeper records when
it does not. An opening's attention list is not the full scope of a task.
2. Choose and combine the methods and operations needed for this request.
Methods are reusable guidance, not a required sequence or a limit on possible
goals. A focused question does not require a broad review. A user request
takes precedence over default routines, including reporting and scheduling.
3. Establish the evidence behind the answer or change. Match the accounts and
history inspected to the claim; complete relevant pagination. Observed
first/last transactions do not establish source coverage. Missing records
establish uncertainty, not hidden spendi_meta.json
{
"ownerId": "kn7bpfvym7rxs43py15v70pfhn8c7dnz",
"slug": "candor-finance",
"version": "0.1.162",
"publishedAt": 1791064912943
}methods/candor-benefits-fsa-hsa/references/workflows.md
# FSA, HSA, and benefits workflows ## Review plan-year spending and deadlines 1. Confirm the benefit type, employer or administrator, plan year, jurisdiction, and whether the user is asking about eligibility, contribution, spending, or reimbursement. 2. Inspect coverage and observed spending: ```sh candor coverage get --reason "Check benefit-review coverage" --task-key TASK_KEY candor transactions list --since START --until END --limit 100 --reason "Find health-related spending cues" --task-key TASK_KEY candor transactions list --category CATEGORY --since START --until END --limit 100 --reason "Inspect potential benefit expenses" --task-key TASK_KEY candor accounts list --limit 100 --reason "Inspect visible benefit account types" --task-key TASK_KEY ``` Use the exact category returned by Candor and paginate material populations. Verify ambiguous expenses rather than treating a category as tax eligibility. 3. Research current rules. Prefer the user's current plan document and administrator materials for plan-specific terms; use the relevant government authority for current statutory limits or tax rules. Record jurisdiction, plan year, source URL/document, publisher, effective date, retrieval date, and which user facts control applicability. 4. Build a date-specific checklist for contribution, incurrence, substantiation, submission, grace-period, carryover, and forfeiture rules only when the applicable source supports them. Complete when observed spending, current plan terms, user applicability, and deadlines are separated and every conclusion is source-attributable. ## Investigate a reimbursement gap 1. Obtain the receipt, explanation of benefits, claim or submission record, and plan rule needed to establish the expected reimbursement. 2. Record the expected amount or range, currency, payer, destination account, submission date, and expected processing window. 3. Search for a matching credit conservatively: ```sh candor transactions list --since START --until END --limit 100 --reason "Search for the expected benefit reimbursement" --task-key TASK_KEY ``` 4. If the result is not yet due or needs authorized follow-up, create a timed note containing the source references, evidence handles, expected window, caveats, and verification rule: ```sh candor catalog describe notes.create --json candor notes create --file NOTE.json --reason "Track benefit reimbursement follow-up" --task-key TASK_KEY --parent-action ACTION_ID ``` Complete when the reimbursement is matched to posted evidence, shown absent from a sufficiently covered period, or scheduled for a specific recheck. ## Model a contribution scenario 1. Confirm eligibility, coverage dates, contribution sources, employer contributions, and the exact plan/account type from authoritative sources. 2. Research the current applicable limit and special rules at decision time. Do not rely on model memory or a pr
methods/candor-budgeting-cashflow/references/workflows.md
# Budgeting and cash-flow workflows Use exact calendar dates and replace every uppercase placeholder. Keep one stable `task_key` across a continuing investigation and pass the returned action id as `parent_action` when a later operation continues that action. ## Reconstruct a period 1. Establish the requested period, currencies, included accounts, and whether the user wants cash movement or an income-and-expense view. 2. Check coverage before calculating: ```sh candor coverage get --reason "Check coverage for the cash-flow period" --task-key TASK_KEY candor data schema transactions --reason "Inspect transaction fields and filters" --task-key TASK_KEY candor transactions list --since START --until END --reason "Read observed cash flow" --task-key TASK_KEY ``` 3. Drill into material or ambiguous categories with bounded pages: ```sh candor transactions list --category CATEGORY --since START --until END --limit 100 --reason "Verify CATEGORY cash-flow treatment" --task-key TASK_KEY ``` Follow `pagination.next_cursor` until `pagination.has_more` is false for every pageable read before treating the relevant population as covered. 4. Classify inflows, operating outflows, transfers, refunds, debt payments, and one-time items separately. Do not count both sides of an internal transfer. Net a refund only against the expense it actually reverses. 5. Report exact currency-separated totals, coverage gaps, excluded items, and the transaction basis. Do not combine currencies using an unstated rate. Complete when another agent can reproduce every total from the stated period, classification policy, and evidence handles. ## Estimate sustainable capacity 1. Start from a reconstructed period, then compare multiple representative periods when seasonality or irregular income could matter. 2. Inspect current obligations and approved plans: ```sh candor recurring list --limit 100 --reason "Inspect recurring cash obligations" --task-key TASK_KEY candor debts list --reason "Inspect visible debt obligations" --task-key TASK_KEY candor budget context --period PERIOD --reason "Compare the approved budget with observed cash flow" --task-key TASK_KEY candor goals list --limit 100 --reason "Inspect approved goals competing for cash" --task-key TASK_KEY ``` 3. Present at least a baseline and a downside case. State which income, expenses, one-time items, and reserve assumptions change between them. 4. Treat the result as a scenario, not a budget or recommendation. Ask the user which tradeoffs fit their priorities before proposing durable state. Complete when the estimate exposes assumptions, sensitivities, collisions with existing goals, and the amount that remains unallocated in each currency. ## Propose or revise a budget 1. Read the active budget, relevant goal versions, and the actions that changed them. 2. Draft the proposed allocation outside Candor and show before/after amounts, rational
methods/candor-card-rewards/references/workflows.md
# Credit-card rewards workflows ## Inventory existing cards and spend 1. Confirm the product identity of each card without requesting full account numbers. Separate card ownership from user-authorized usage preferences. 2. Inspect visible accounts, coverage, and category totals: ```sh candor coverage get --reason "Check card and transaction coverage" --task-key TASK_KEY candor accounts list --limit 100 --reason "Inventory visible card accounts" --task-key TASK_KEY candor transactions list --since START --until END --limit 100 --reason "Inspect category and merchant spend" --task-key TASK_KEY ``` 3. If the analysis requires assigning spend to a specific card, take that card's exact `id` from `accounts list` and use it as the `source_account_id` transaction filter: ```sh candor transactions list --source-account-id SOURCE_ACCOUNT_ID --since START --until END --limit 100 --reason "Inspect spend assigned to this card" --task-key TASK_KEY ``` Follow `pagination.next_cursor` until `pagination.has_more` is false before treating the period as complete. If the card is not visible or its transaction coverage is insufficient, do not allocate aggregate spend to it; ask for another source or present an aggregate scenario. Complete when card identities, observed spend, currencies, account assignment, and coverage gaps are explicit. ## Evaluate current-card routing 1. Obtain current official issuer terms for each relevant card: earning rules, merchant-category definitions, caps, exclusions, annual fee, credits, redemption constraints, and effective dates. 2. Record publisher, product identity, URL/document, effective date, retrieval date, and user applicability. Treat marketing summaries as secondary to the benefit guide or card agreement. 3. Model only observed eligible spend. Separate: - base and category rewards; - caps or thresholds; - credits the user can realistically use without induced spending; - annual fees; - cash-equivalent value from subjective travel value; and - unmodeled merchant coding or redemption uncertainty. 4. Present a routing plan as a draft behavior choice. Ask before recording any rule or note that reflects the user's values. Complete when the incremental value versus the current course is reproducible and the user can see fees, caps, effort, uncertainty, and behavioral risks. ## Review an annual fee or possible card change 1. Verify the fee amount and renewal date from a current statement or issuer source. 2. Compare verified benefits actually used, realistically usable benefits, and observed rewards with the fee. Do not count a credit at face value when it requires unwanted spending. 3. Before discussing an application, closure, or product change, gather the user's credit, liquidity, upcoming borrowing, account-age, and preference context outside Candor as needed. State what remains unknown. 4. Research current product and credit-
AionUi
Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!
activepieces
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
cherry-studio
AI productivity studio with smart chat, autonomous agents, and 300+ assistants.
CopilotKit
The Frontend for Agents & Generative UI. React + Angular
Machine-readable data
The same record, as JSON, for agents and crawlers.
{
"facts": [
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Clawhub",
"href": "https://clawhub.ai/candor/skills/candor-finance",
"sourceUrl": "https://clawhub.ai/candor/skills/candor-finance",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-09T11:34:01.699Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "OpenClaw",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-candor-candor-finance/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-candor-candor-finance/contract",
"sourceType": "contract",
"confidence": "medium",
"observedAt": "2026-10-09T11:34:01.699Z",
"isPublic": true
},
{
"factKey": "traction",
"category": "adoption",
"label": "Adoption signal",
"value": "2.8K downloads",
"href": "https://clawhub.ai/candor/candor-finance",
"sourceUrl": "https://clawhub.ai/candor/candor-finance",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-09T11:34:01.699Z",
"isPublic": true
},
{
"factKey": "latest_release",
"category": "release",
"label": "Latest release",
"value": "0.1.162",
"href": "https://clawhub.ai/candor/candor-finance",
"sourceUrl": "https://clawhub.ai/candor/candor-finance",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-10-03T22:01:52.943Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-candor-candor-finance/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-candor-candor-finance/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
],
"events": [
{
"eventType": "release",
"title": "Release 0.1.162",
"description": "Sync Candor Finance package 0.1.162 from its verified public mirror.",
"href": "https://clawhub.ai/candor/candor-finance",
"sourceUrl": "https://clawhub.ai/candor/candor-finance",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-10-03T22:01:52.943Z",
"isPublic": true
}
]
}Record generated Oct 9, 2026.
