Query, display, and resolve reconciliation gaps from the TRES Finance MCP connector. Trigger this skill ONLY when the user explicitly requests to view or close reconciliation gaps — for example: "show me the reconciliation gaps", "close the recon gaps", "view gaps for today", "plug the reconciliation gaps for ETH", "fix the gaps for USDC and BTC". Do NOT trigger for general balance queries, transaction history, or ledger browsing. Covers the full workflow: confirming the target date, optionally filtering by asset, fetching gap data, enriching with fiat and on-chain balances, rendering an HTML dashboard where each gap row has copy-prompt buttons (Plug / Auto-fill) — clicking copies a ready-to-paste Claude prompt for that gap. The user pastes it in the chat and Claude executes the action. Ends with a data collect once the user is done.
Query, display, and resolve reconciliation gaps from the TRES Finance MCP connector. Trigger this skill ONLY when the user explicitly requests to view or close reconciliation gaps — for example: "show me the reconciliation gaps", "close the recon gaps", "view gaps for today", "plug the reconciliation gaps for ETH", "fix the gaps for USDC and BTC". Do NOT trigger for general balance queries, transaction history, or ledger browsing. Covers the full workflow: confirming the target date, optionally filtering by asset, fetching gap data, enriching with fiat and on-chain balances, rendering an HTML dashboard where each gap row has copy-prompt buttons (Plug / Auto-fill) — clicking copies a ready-to-paste Claude prompt for that gap. The user pastes it in the chat and Claude executes the action. Ends with a data collect once the user is done.
compatibility
Requires TRES Finance MCP connector
TRES Reconciliation Gaps Skill
End-to-end workflow for surfacing, analyzing, and resolving reconciliation gaps in TRES Finance.
Pre-flight: confirm date and asset scope
Before fetching any data, confirm two things with the user:
1. Target date
The reconciliation queries are scoped to a specific date (the endDate parameter).
If the user explicitly stated a date — use it.
If the user did not mention a date — assume today's date and inform them:
"I'll fetch reconciliation gaps for today (YYYY-MM-DD). Let me know if you want a different date."
Use ISO format YYYY-MM-DD throughout.
2. Asset filter (optional)
If the user (e.g. "for ETH and USDC", "just BTC") — note them. After fetching, filter the results to only those values before displaying.
named specific assets
asset.symbol
If the user did not specify assets — fetch and display all gaps.
Step 1 — Fetch reconciliation gaps
Use the reconciliation query. Always pass the confirmed endDate. Fetch up to 200 at a time.
query GetReconciliationGaps($limit: Int, $offset: Int, $endDate: Date){
reconciliation(limit:$limit, offset:$offset, endDate:$endDate) {
totalCount
results {
id
amount
calculatedBalance
state
status
gap
belongsTo {
id
name
identifier
}
asset {
key
identifier
symbol
platform
}
pendingTransactionsCount
pendingTransactionsTotalAmount
}}}
Step 3 — Display: always render the HTML dashboard
Always generate a standalone .html file as the primary output — do not fall back to an inline widget.
Read references/html-template-notes.md for the full visual spec (fonts, colors, layout, column widths, modal behavior, API call mechanism).
Key requirements for the generated file:
Dark financial dashboard aesthetic (spec in reference file)
Sticky header showing the target date and a refresh timestamp badge
5 summary metric cards: net fiat gap, positive gap count, negative gap count, asset group count, pending tx count
If an asset filter was applied, show a visible filter badge in the toolbar (e.g. Filtered: ETH, USDC)
Search + direction filter + platform filter toolbar
Asset-grouped collapsible sections, sorted by absolute net fiat gap descending
Full column set per row — last column has two copy-prompt buttons: ↳ Plug (blue) and ⟳ Auto-fill (purple)
Clicking either button copies a ready-to-paste prompt to clipboard and shows a toast: "Prompt copied — paste it in the Claude chat to resolve this gap."
No HTTP requests — the HTML is a pure display interface; all mutations happen in Claude after the user pastes the prompt
After generating the file, present it to the user with present_files.
Step 4 — Actions (plug-once and auto-fill)
The user triggers actions by copying a prompt from the HTML dashboard and pasting it into the Claude chat. When Claude receives one of these prompts, execute the corresponding mutation immediately — no further confirmation needed (the user already chose the action in the dashboard).
