tres-recon-gaps

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 named specific assets (e.g. "for ETH and USDC", "just BTC") — note them. After fetching, filter the results to only those asset.symbol values before displaying.
• 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
    }
  }
}

Variables: {"limit": 200, "offset": 0, "endDate": "<confirmed-date>"}

Note: gap = calculatedBalance − historicalBalance. Positive means the ledger has more than on-chain; negative means the ledger has less.

If the user requested specific assets, filter the results now: keep only rows where asset.symbol matches the requested symbols (case-insensitive).

---

Step 2 — Enrich with fiat values and on-chain balances

Take all IDs from the (filtered) Step 1 results and query assetBalance: