[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718ENJQH8YWN8KKDSHNT583":3,"skill-same:01M718ENJQH8YWN8KKDSHNT583":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":6,"updatedAt":69,"install":70,"resources":83},"01M718ENJQH8YWN8KKDSHNT583","tres-recon-gaps",null,"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 \u002F 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.","anthropics\u002Fclaude-plugins-community","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M718C1RS4JJFM9KNJMTCAYJG",4869,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-recon-gaps\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000040","财务",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"tres recon gaps","gaps","recon","Connector","query","done","browsing","workflow","show me","when","auto","MCP","only","fiat","fix","chain","balances","show","ready","reconciliation","2026-11-10 10:12:30",false,"---\nname: tres-recon-gaps\ndescription: >\n  Query, display, and resolve reconciliation gaps from the TRES Finance MCP connector.\n  Trigger this skill ONLY when the user explicitly requests to view or close reconciliation\n  gaps — for example: \"show me the reconciliation gaps\", \"close the recon gaps\", \"view gaps\n  for today\", \"plug the reconciliation gaps for ETH\", \"fix the gaps for USDC and BTC\".\n  Do NOT trigger for general balance queries, transaction history, or ledger browsing.\n  Covers the full workflow: confirming the target date, optionally filtering by asset,\n  fetching gap data, enriching with fiat and on-chain balances, rendering an HTML dashboard\n  where each gap row has copy-prompt buttons (Plug \u002F Auto-fill) — clicking copies a\n  ready-to-paste Claude prompt for that gap. The user pastes it in the chat and Claude\n  executes the action. Ends with a data collect once the user is done.\ncompatibility: \"Requires TRES Finance MCP connector\"\n---\n\n# TRES Reconciliation Gaps Skill\n\nEnd-to-end workflow for surfacing, analyzing, and resolving reconciliation gaps in TRES Finance.\n\n---\n\n## Pre-flight: confirm date and asset scope\n\n**Before fetching any data**, confirm two things with the user:\n\n### 1. Target date\n\nThe reconciliation queries are scoped to a specific date (the `endDate` parameter).\n\n- If the user **explicitly stated a date** — use it.\n- If the user **did not mention a date** — assume today's date and inform them:\n  > \"I'll fetch reconciliation gaps for today (YYYY-MM-DD). Let me know if you want a different date.\"\n\nUse ISO format `YYYY-MM-DD` throughout.\n\n### 2. Asset filter (optional)\n\n- 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.\n- If the user **did not specify assets** — fetch and display all gaps.\n\n---\n\n## Step 1 — Fetch reconciliation gaps\n\nUse the `reconciliation` query. Always pass the confirmed `endDate`. Fetch up to 200 at a time.\n\n```graphql\nquery GetReconciliationGaps($limit: Int, $offset: Int, $endDate: Date) {\n  reconciliation(limit: $limit, offset: $offset, endDate: $endDate) {\n    totalCount\n    results {\n      id\n      amount\n      calculatedBalance\n      state\n      status\n      gap\n      belongsTo {\n        id\n        name\n        identifier\n      }\n      asset {\n        key\n        identifier\n        symbol\n        platform\n      }\n      pendingTransactionsCount\n      pendingTransactionsTotalAmount\n    }\n  }\n}\n```\n\nVariables: `{\"limit\": 200, \"offset\": 0, \"endDate\": \"\u003Cconfirmed-date>\"}`\n\n> Note: `gap` = `calculatedBalance − historicalBalance`. Positive means the ledger has *more* than on-chain; negative means the ledger has *less*.\n\nIf the user requested specific assets, filter the results now: keep only rows where `asset.symbol` matches the requested symbols (case-insensitive).\n\n---\n\n## Step 2 — Enrich with fiat values and on-chain balances\n\nTake all IDs from the (filtered) Step 1 results and query `assetBalance`:\n\n```graphql\nquery GetAssetBalancesWithFiat($ids: [String], $limit: Int, $currency: String) {\n  assetBalance(id_In: $ids, limit: $limit, currency: $currency, excludeUnderDelegation: true) {\n    totalCount\n    results {\n      id\n      calculatedBalance\n      historicalBalance\n      reconciliation\n      fiatValue {\n        value\n        unitPrice\n        fiatCurrency\n      }\n      belongsTo {\n        id\n        name\n        identifier\n      }\n      asset {\n        key\n        symbol\n        platform\n        identifier\n      }\n    }\n  }\n}\n```\n\nVariables: `{\"currency\": \"usd\", \"ids\": [\"\u003Cid1>\", \"\u003Cid2>\", ...], \"limit\": 200}`\n\n**Important**: `id_In` expects `[String]`, not `[ID]`.\n\nCompute for each row:\n```\nfiatGap = reconciliation (token gap) × fiatValue.unitPrice\n```\n\n---\n\n## Step 3 — Display: always render the HTML dashboard\n\n**Always** generate a standalone `.html` file as the primary output — do not fall back to an inline widget.\n\nRead `references\u002Fhtml-template-notes.md` for the full visual spec (fonts, colors, layout, column widths, modal behavior, API call mechanism).\n\nKey requirements for the generated file:\n- Dark financial dashboard aesthetic (spec in reference file)\n- Sticky header showing the **target date** and a refresh timestamp badge\n- 5 summary metric cards: net fiat gap, positive gap count, negative gap count, asset group count, pending tx count\n- If an **asset filter** was applied, show a visible filter badge in the toolbar (e.g. `Filtered: ETH, USDC`)\n- Search + direction filter + platform filter toolbar\n- Asset-grouped collapsible sections, sorted by absolute net fiat gap descending\n- Full column set per row — last column has two copy-prompt buttons: **↳ Plug** (blue) and **⟳ Auto-fill** (purple)\n- 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.\"\n- **No HTTP requests** — the HTML is a pure display interface; all mutations happen in Claude after the user pastes the prompt\n\nAfter generating the file, present it to the user with `present_files`.\n\n---\n\n## Step 4 — Actions (plug-once and auto-fill)\n\nThe 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).\n\n### One-time plug (`createPlug`)\n\n```graphql\nmutation CreatePlug(\n  $hash: String!\n  $platform: Platform!\n  $timestamp: DateTime!\n  $belongsToId: ID!\n  $assetId: ID!\n  $assetIdentifier: String!\n  $amount: Float!\n  $direction: Direction!\n  $thirdPartyIdentifier: String!\n) {\n  createPlug(\n    hash: $hash\n    platform: $platform\n    timestamp: $timestamp\n    belongsToId: $belongsToId\n    assetId: $assetId\n    assetIdentifier: $assetIdentifier\n    amount: $amount\n    direction: $direction\n    thirdPartyIdentifier: $thirdPartyIdentifier\n  ) {\n    transaction { id identifier platform timestamp }\n  }\n}\n```\n\n**Variable mapping:**\n| Field | Value |\n|---|---|\n| `hash` | `plug_\u003CassetId>_\u003CwalletId>_\u003Ctimestamp_ms>` |\n| `platform` | `asset.platform` |\n| `timestamp` | `new Date().toISOString()` |\n| `belongsToId` | `belongsTo.id` |\n| `assetId` | `asset.key` |\n| `assetIdentifier` | `asset.identifier` (use `\"native\"` for native assets like ETH\u002FAVAX) |\n| `amount` | `Math.abs(gap)` |\n| `direction` | `gap > 0 ? \"INFLOW\" : \"OUTFLOW\"` |\n| `thirdPartyIdentifier` | `belongsTo.identifier` (wallet address) |\n\n### Auto gap-fill rule (`createReconciliationGapFillRule`)\n\n```graphql\nmutation CreateGapFillRule(\n  $name: String!\n  $assetId: String!\n  $internalAccountId: Int!\n  $interval: Interval!\n  $startDate: Date!\n  $endDate: Date!\n) {\n  createReconciliationGapFillRule(\n    name: $name\n    assetId: $assetId\n    internalAccountId: $internalAccountId\n    interval: $interval\n    startDate: $startDate\n    endDate: $endDate\n  ) {\n    success\n    message\n    ruleId\n  }\n}\n```\n\n**Variable mapping:**\n| Field | Value |\n|---|---|\n| `name` | User-editable rule name (pre-filled: `Auto gap-fill · \u003Casset> · \u003Cwallet>`) |\n| `assetId` | `asset.key` |\n| `internalAccountId` | `parseInt(belongsTo.id)` — must be `Int!` |\n| `interval` | `DAILY` \u002F `WEEKLY` \u002F `MONTHLY` |\n| `startDate` | ISO date string, e.g. `\"2026-04-07\"` |\n| `endDate` | ISO date string (default: 2 years from today) |\n\n---\n\n## Step 5 — Run data collect after plugs are done\n\nOnce the user indicates they are **finished adding plugs** (e.g. \"done\", \"that's all\", \"looks good\"), run a data collect to sync the updated state.\n\nUse the `triggerDataCollect` mutation (or equivalent — introspect with `get_schema_summary` if needed):\n\n```graphql\nmutation TriggerDataCollect {\n  triggerDataCollect {\n    success\n    message\n  }\n}\n```\n\nAfter it completes, inform the user:\n> \"Data collect triggered — TRES will now sync the latest on-chain balances. The reconciliation gaps should update shortly.\"\n\n---\n\n## Grouping and sorting logic\n\n**Default grouping: by asset symbol**\n- Group all rows sharing the same `asset.symbol` into one group\n- Net fiat gap shown per group header\n- Sort groups by absolute net fiat gap descending\n- Sort rows within each group by absolute fiat gap descending\n\n**Alternative: group by wallet** (if user requests it)\n- Group by `belongsTo.identifier`\n- Same sorting logic\n\nAlways order by **fiat gap**, not token gap.\n\n---\n\n## Number formatting conventions\n\n```js\n\u002F\u002F Fiat values\n≥ $1M  → \"$X.XXXM\"\n≥ $1K  → \"$X.XXK\"\n\u003C $1K  → \"$X.XX\"\n\n\u002F\u002F Token quantities\n≥ 1B   → \"X.XXXB\"\n≥ 1M   → \"X.XXXM\"\n≥ 1K   → \"X.XXXK\"\n\u003C 1K   → up to 6 significant figures, trim trailing zeros\n\n\u002F\u002F Signs\nPositive gaps: \"+\" prefix\nNegative gaps: \"−\" (minus sign, not hyphen)\nNo sign:       absolute values (on-chain bal, calculated bal)\n```\n\n---\n\n## Common edge cases\n\n| Situation | Handling |\n|---|---|\n| `unitPrice = 0` | Show \"—\" for fiat gap; token gap still displays |\n| `historicalBalance` is negative | Display as-is; flag visually if extreme |\n| `pendingTransactionsCount > 0` | Show amber warning badge — pending txs may reduce the gap once confirmed |\n| Very large token gaps with tiny fiat value | Still show; sort by fiat means they appear near bottom |\n| `gap` field timeouts on large datasets | Use `assetBalance.reconciliation` field instead (same value, more reliable) |\n| Asset filter yields zero rows | Inform the user: \"No gaps found for [assets] on [date]\" |\n\n---\n\n## Key schema facts (verified)\n\n- `reconciliation` query — has `endDate` parameter; returns `gap` and basic balance fields\n- `assetBalance` query — returns `historicalBalance`, `reconciliation` (= gap), and `fiatValue { value, unitPrice }`; **prefer for enriched data**\n- `assetBalance(id_In: [String])` — note `[String]` not `[ID]`\n- `createPlug` — `belongsToId` is `ID!`, `assetId` is `ID!` (pass the asset key string)\n- `createReconciliationGapFillRule` — `internalAccountId` is `Int!`; `assetId` is `String!`; `interval` is `Interval!` enum\n- Platform enum values: `ETHEREUM`, `BASE`, `ARBITRUM`, `OPTIMISM`, `POLYGON`, `AVAX`, `AVALANCHE_P_CHAIN`, `MANTRA`, etc.\n","# TRES Reconciliation Gaps Skill\n\nEnd-to-end workflow for surfacing, analyzing, and resolving reconciliation gaps in TRES Finance.\n\n---\n\n## Pre-flight: confirm date and asset scope\n\n**Before fetching any data**, confirm two things with the user:\n\n### 1. Target date\n\nThe reconciliation queries are scoped to a specific date (the `endDate` parameter).\n\n- If the user **explicitly stated a date** — use it.\n- If the user **did not mention a date** — assume today's date and inform them:\n  > \"I'll fetch reconciliation gaps for today (YYYY-MM-DD). Let me know if you want a different date.\"\n\nUse ISO format `YYYY-MM-DD` throughout.\n\n### 2. Asset filter (optional)\n\n- 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.\n- If the user **did not specify assets** — fetch and display all gaps.\n\n---\n\n## Step 1 — Fetch reconciliation gaps\n\nUse the `reconciliation` query. Always pass the confirmed `endDate`. Fetch up to 200 at a time.\n\n```graphql\nquery GetReconciliationGaps($limit: Int, $offset: Int, $endDate: Date) {\n  reconciliation(limit: $limit, offset: $offset, endDate: $endDate) {\n    totalCount\n    results {\n      id\n      amount\n      calculatedBalance\n      state\n      status\n      gap\n      belongsTo {\n        id\n        name\n        identifier\n      }\n      asset {\n        key\n        identifier\n        symbol\n        platform\n      }\n      pendingTransactionsCount\n      pendingTransactionsTotalAmount\n    }\n  }\n}\n```\n\nVariables: `{\"limit\": 200, \"offset\": 0, \"endDate\": \"\u003Cconfirmed-date>\"}`\n\n> Note: `gap` = `calculatedBalance − historicalBalance`. Positive means the ledger has *more* than on-chain; negative means the ledger has *less*.\n\nIf the user requested specific assets, filter the results now: keep only rows where `asset.symbol` matches the requested symbols (case-insensitive).\n\n---\n\n## Step 2 — Enrich with fiat values and on-chain balances\n\nTake all IDs from the (filtered) Step 1 results and query `assetBalance`:\n\n```graphql\nquery GetAssetBalancesWithFiat($ids: [String], $limit: Int, $currency: String) {\n  assetBalance(id_In: $ids, limit: $limit, currency: $currency, excludeUnderDelegation: true) {\n    totalCount\n    results {\n      id\n      calculatedBalance\n      historicalBalance\n      reconciliation\n      fiatValue {\n        value\n        unitPrice\n        fiatCurrency\n      }\n      belongsTo {\n        id\n        name\n        identifier\n      }\n      asset {\n        key\n        symbol\n        platform\n        identifier\n      }\n    }\n  }\n}\n```\n\nVariables: `{\"currency\": \"usd\", \"ids\": [\"\u003Cid1>\", \"\u003Cid2>\", ...], \"limit\": 200}`\n\n**Important**: `id_In` expects `[String]`, not `[ID]`.\n\nCompute for each row:\n```\nfiatGap = reconciliation (token gap) × fiatValue.unitPrice\n```\n\n---\n\n## Step 3 — Display: always render the HTML dashboard\n\n**Always** generate a standalone `.html` file as the primary output — do not fall back to an inline widget.\n\nRead `references\u002Fhtml-template-notes.md` for the full visual spec (fonts, colors, layout, column widths, modal behavior, API call mechanism).\n\nKey requirements for the generated file:\n- Dark financial dashboard aesthetic (spec in reference file)\n- Sticky header showing the **target date** and a refresh timestamp badge\n- 5 summary metric cards: net fiat gap, positive gap count, negative gap count, asset group count, pending tx count\n- If an **asset filter** was applied, show a visible filter badge in the toolbar (e.g. `Filtered: ETH, USDC`)\n- Search + direction filter + platform filter toolbar\n- Asset-grouped collapsible sections, sorted by absolute net fiat gap descending\n- Full column set per row — last column has two copy-prompt buttons: **↳ Plug** (blue) and **⟳ Auto-fill** (purple)\n- 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.\"\n- **No HTTP requests** — the HTML is a pure display interface; all mutations happen in Claude after the user pastes the prompt\n\nAfter generating the file, present it to the user with `present_files`.\n\n---\n\n## Step 4 — Actions (plug-once and auto-fill)\n\nThe 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).\n\n### One-time plug (`createPlug`)\n\n```graphql\nmutation CreatePlug(\n  $hash: String!\n  $platform: Platform!\n  $timestamp: DateTime!\n  $belongsToId: ID!\n  $assetId: ID!\n  $assetIdentifier: String!\n  $amount: Float!\n  $direction: Direction!\n  $thirdPartyIdentifier: String!\n) {\n  createPlug(\n    hash: $hash\n    platform: $platform\n    timestamp: $timestamp\n    belongsToId: $belongsToId\n    assetId: $assetId\n    assetIdentifier: $assetIdentifier\n    amount: $amount\n    direction: $direction\n    thirdPartyIdentifier: $thirdPartyIdentifier\n  ) {\n    transaction { id identifier platform timestamp }\n  }\n}\n```\n\n**Variable mapping:**\n| Field | Value |\n|---|---|\n| `hash` | `plug_\u003CassetId>_\u003CwalletId>_\u003Ctimestamp_ms>` |\n| `platform` | `asset.platform` |\n| `timestamp` | `new Date().toISOString()` |\n| `belongsToId` | `belongsTo.id` |\n| `assetId` | `asset.key` |\n| `assetIdentifier` | `asset.identifier` (use `\"native\"` for native assets like ETH\u002FAVAX) |\n| `amount` | `Math.abs(gap)` |\n| `direction` | `gap > 0 ? \"INFLOW\" : \"OUTFLOW\"` |\n| `thirdPartyIdentifier` | `belongsTo.identifier` (wallet address) |\n\n### Auto gap-fill rule (`createReconciliationGapFillRule`)\n\n```graphql\nmutation CreateGapFillRule(\n  $name: String!\n  $assetId: String!\n  $internalAccountId: Int!\n  $interval: Interval!\n  $startDate: Date!\n  $endDate: Date!\n) {\n  createReconciliationGapFillRule(\n    name: $name\n    assetId: $assetId\n    internalAccountId: $internalAccountId\n    interval: $interval\n    startDate: $startDate\n    endDate: $endDate\n  ) {\n    success\n    message\n    ruleId\n  }\n}\n```\n\n**Variable mapping:**\n| Field | Value |\n|---|---|\n| `name` | User-editable rule name (pre-filled: `Auto gap-fill · \u003Casset> · \u003Cwallet>`) |\n| `assetId` | `asset.key` |\n| `internalAccountId` | `parseInt(belongsTo.id)` — must be `Int!` |\n| `interval` | `DAILY` \u002F `WEEKLY` \u002F `MONTHLY` |\n| `startDate` | ISO date string, e.g. `\"2026-04-07\"` |\n| `endDate` | ISO date string (default: 2 years from today) |\n\n---\n\n## Step 5 — Run data collect after plugs are done\n\nOnce the user indicates they are **finished adding plugs** (e.g. \"done\", \"that's all\", \"looks good\"), run a data collect to sync the updated state.\n\nUse the `triggerDataCollect` mutation (or equivalent — introspect with `get_schema_summary` if needed):\n\n```graphql\nmutation TriggerDataCollect {\n  triggerDataCollect {\n    success\n    message\n  }\n}\n```\n\nAfter it completes, inform the user:\n> \"Data collect triggered — TRES will now sync the latest on-chain balances. The reconciliation gaps should update shortly.\"\n\n---\n\n## Grouping and sorting logic\n\n**Default grouping: by asset symbol**\n- Group all rows sharing the same `asset.symbol` into one group\n- Net fiat gap shown per group header\n- Sort groups by absolute net fiat gap descending\n- Sort rows within each group by absolute fiat gap descending\n\n**Alternative: group by wallet** (if user requests it)\n- Group by `belongsTo.identifier`\n- Same sorting logic\n\nAlways order by **fiat gap**, not token gap.\n\n---\n\n## Number formatting conventions\n\n```js\n\u002F\u002F Fiat values\n≥ $1M  → \"$X.XXXM\"\n≥ $1K  → \"$X.XXK\"\n\u003C $1K  → \"$X.XX\"\n\n\u002F\u002F Token quantities\n≥ 1B   → \"X.XXXB\"\n≥ 1M   → \"X.XXXM\"\n≥ 1K   → \"X.XXXK\"\n\u003C 1K   → up to 6 significant figures, trim trailing zeros\n\n\u002F\u002F Signs\nPositive gaps: \"+\" prefix\nNegative gaps: \"−\" (minus sign, not hyphen)\nNo sign:       absolute values (on-chain bal, calculated bal)\n```\n\n---\n\n## Common edge cases\n\n| Situation | Handling |\n|---|---|\n| `unitPrice = 0` | Show \"—\" for fiat gap; token gap still displays |\n| `historicalBalance` is negative | Display as-is; flag visually if extreme |\n| `pendingTransactionsCount > 0` | Show amber warning badge — pending txs may reduce the gap once confirmed |\n| Very large token gaps with tiny fiat value | Still show; sort by fiat means they appear near bottom |\n| `gap` field timeouts on large datasets | Use `assetBalance.reconciliation` field instead (same value, more reliable) |\n| Asset filter yields zero rows | Inform the user: \"No gaps found for [assets] on [date]\" |\n\n---\n\n## Key schema facts (verified)\n\n- `reconciliation` query — has `endDate` parameter; returns `gap` and basic balance fields\n- `assetBalance` query — returns `historicalBalance`, `reconciliation` (= gap), and `fiatValue { value, unitPrice }`; **prefer for enriched data**\n- `assetBalance(id_In: [String])` — note `[String]` not `[ID]`\n- `createPlug` — `belongsToId` is `ID!`, `assetId` is `ID!` (pass the asset key string)\n- `createReconciliationGapFillRule` — `internalAccountId` is `Int!`; `assetId` is `String!`; `interval` is `Interval!` enum\n- Platform enum values: `ETHEREUM`, `BASE`, `ARBITRUM`, `OPTIMISM`, `POLYGON`, `AVAX`, `AVALANCHE_P_CHAIN`, `MANTRA`, etc.\n",{"name":5,"description":60,"compatibility":61},"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 \u002F 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.\n","Requires TRES Finance MCP connector","main","163301d1904c0a994539f5226ce0fcd65b8652bf","tres-finance-plugin\u002Fskills\u002Ftres-recon-gaps",357,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-11 15:47:52",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add anthropics\u002Fclaude-plugins-community --skill tres-recon-gaps",{"tool":76,"command":77},"bunx","bunx skills add anthropics\u002Fclaude-plugins-community --skill tres-recon-gaps",{"tool":79,"command":80},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-plugins-community --skill tres-recon-gaps","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-recon-gaps\u002FSKILL.md",true,[84],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fhtml-template-notes.md","REFERENCE","参考文档",4209,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-recon-gaps\u002Freferences\u002Fhtml-template-notes.md",[91,121,143,165,189,212],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":55},"01M718G9QZ4B2DJVEB3MAW5ZB1","tres-wallets-upload","Upload and onboard multiple on-chain wallets or exchange accounts into Tres Finance. Use this skill whenever the user wants to add wallets, onboard wallets, import wallets, upload wallet addresses, ingest wallets, or connect exchanges into Tres — whether from a file (CSV\u002FExcel) or by typing them manually. This skill guides Claude through the full flow: wallet type selection → input collection → validation → preview with editable HTML table → exchange credential collection (if exchange) → user confirmation → batch creation via the TRES MCP API. Always trigger this skill for wallet onboarding, wallet data ingestion, or any request to \"add wallets to Tres\".","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-wallets-upload\u002FSKILL.md",[97,100,101],{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[103,104,105,106,107,108,50,109,110,111,46,112,113,114,115,116,117,118,119,120],"wallets","tres wallets upload","upload","typing","ingestion","Wallet","creation","xlsx","selection","confirmation","connect","collection","preview","api","batch","guides","on-chain","request",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":55},"01M718G5RD9064Z574RQ4SEY38","tres-upload-tx-header-validation","The exact column header names required by the TRES Finance bulk transaction CSV upload. Use whenever building, fixing, or validating the header row of a TRES manual transaction or sub-transaction upload CSV — especially after an upload fails with \"Missing required column(s): ...\". Trigger phrases include: 'fix my CSV headers', 'bulk transaction upload failed', 'missing required columns', 'validate TRES upload CSV', 'transaction CSV template headers'. This skill is ONLY about the header naming convention; it does not cover row values or upload workflow. Do NOT trigger for contacts import CSV (use tres-import-contacts), wallet upload CSV (use tres-wallets-upload), or general CSV parsing unrelated to bulk TX upload headers.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-upload-tx-header-validation\u002FSKILL.md",[],[128,105,129,130,131,132,108,133,134,135,136,49,137,138,47,139,42,140,141,142],"tres upload tx header validation","validation","bulk","do","import","parsing","for","manual","trigger","missing","general","use","csv","contacts","with",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":55},"01M718G1F3DBWTX5H9RWPHHB4F","tres-tx-story","Analyze a blockchain transaction by its hash using TRES Finance MCP and generate a visual flow diagram showing all asset movements, followed by a plain-language explanation of what happened. Use this skill whenever the user provides a transaction hash and asks to \"analyze\", \"explain\", \"visualize\", \"diagram\", \"show me what happened in\", or \"tell the story of\" a transaction. Also trigger when the user pastes a tx hash (long hex string starting with 0x) and asks anything about it. Always use this skill for transaction hash analysis — do not attempt to answer from memory alone.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-tx-story\u002FSKILL.md",[149],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[151,152,52,153,154,46,44,43,155,156,157,158,159,160,161,162,163,131,164,134],"tres tx story","Story","memory","hex","analysis","analyze","me","diagram","generate","flow","asset","blockchain","STRING","visualize",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":55},"01M718FW5ST9J56WY4TJ5G5A7X","tres-settings-management","Manage Organization Settings and Platform Settings via the TRES MCP GraphQL API. Use when users ask about org settings, platform settings, configuration, feature flags, enable\u002Fdisable platforms, balance diff, commit strategy, cost basis, ERP, pricing, sync boundaries, or any setting read\u002Fwrite operation. Trigger phrases include \"get settings\", \"show settings\", \"update settings\", \"change settings\", \"enable platform\", \"disable platform\", \"balance diff\", \"commit strategy\", \"cost basis strategy\", \"set min sync date\", \"configure\", \"turn on\", \"turn off\".","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-settings-management\u002FSKILL.md",[171],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[173,174,175,176,52,177,46,44,178,179,180,116,181,182,183,184,185,186,187,188],"tres settings management","settings","management","SET","get","configure","ask","commit","change","organization","update","read","write","sync","mcp graphql","flags",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":197,"publishedAt":55},"01M718FND35X9DPTNR7JTX2YX8","tres-rollup-rules","Analyze an organization's sub-transaction patterns in TRES Finance, identify groups of repetitive transactions, and propose data-driven rollup rules that consolidate them into one aggregated entry per interval (daily or monthly) for cleaner ERP integration. Also lists and deletes rollup rules. Trigger this skill whenever the user asks about rollup rules, transaction aggregation, consolidating transactions, reducing transaction noise, rolling up gas fees, rolling up staking rewards, rolling up micro-transactions, or collapsing many small ledger entries into fewer summary entries. Also trigger on \"create a rollup rule\", \"suggest rollup rules\", \"what should I roll up\", \"show my rollup rules\", \"delete a rollup rule\", \"aggregate transactions\", \"too many transactions\", \"reduce transaction count\", \"roll up fees\", \"daily rollup\", \"monthly rollup\". If a wallet has too many transactions, high-frequency activity, or noisy ledger entries, proactively suggest rollup rules. For computing the EXACT impact of a single already-specified rule or reviewing submitted\u002Fpending rules, use the tres-rollup-review skill instead.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-rollup-rules\u002FSKILL.md",[195,196],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[198,199,200,52,201,108,202,46,203,204,38,205,206,156,207,208,209,210,182,211],"tres rollup rules","Rules","rollup","gas","up","impact","reduce","review","consolidate","create","transactions","delete","data-driven","activity",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":220,"publishedAt":55},"01M718FFX3KV2JRFVS2RCM719D","tres-rollup-review","Compute the EXACT sub-transaction impact of a rollup rule in TRES Finance — every filter applied — and flag genuine problems (zero matches, overlap, config mistakes) before the rule is created. Two modes. Mode A: a pre-create quality gate invoked by the tres-rollup-rules skill to vet proposed candidate rules. Mode B: standalone review of a rule someone submitted or of existing PENDING rules. Trigger this skill when the user says \"review this rollup rule\", \"what would this rollup rule actually match\", \"preview the rollup impact\", \"how many transactions would this rule catch\", \"is this rollup rule valid\", \"validate my rollup rule\", \"check my pending rollup rules\", or \"review the rollup requests\". Do NOT use this to design or propose new rollups — that is tres-rollup-rules. This skill only measures impact and flags issues; it never executes mutations.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-rollup-review\u002FSKILL.md",[218,219],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[205,221,200,222,223,224,225,226,47,227,46,203,44,115,228,38,229,230,207,231],"tres rollup review","standalone","never","mode","issues","design","new","candidate","filter","valid","catch"]