[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718D0AYKA7PEE2DA4E8YT70":3,"skill-same:01M718D0AYKA7PEE2DA4E8YT70":71},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M718D0AYKA7PEE2DA4E8YT70","tres-asset-balance-validation",null,"Validate wallet balances in TRES Finance against DeBank and generate a discrepancy report. Use this skill whenever the user asks to validate, verify, cross-check, or audit their TRES balances against on-chain data or DeBank. Also trigger when the user asks if their balances are correct or wants to see discrepancies. Only EVM-compatible wallets are supported.","anthropics\u002Fclaude-plugins-community","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M718C1RS4JJFM9KNJMTCAYJG",4856,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-asset-balance-validation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"balance","validation","tres asset balance validation","asset","verify","evm","check","use","correct","trigger","wallets","data","audit","generate","on-chain","when","only","chain","balances","Wallet","2026-11-10 10:12:30",false,"---\nname: tres-asset-balance-validation\ndescription: >\n  Validate wallet balances in TRES Finance against DeBank and generate a discrepancy\n  report. Use this skill whenever the user asks to validate, verify, cross-check, or\n  audit their TRES balances against on-chain data or DeBank. Also trigger when the\n  user asks if their balances are correct or wants to see discrepancies. Only\n  EVM-compatible wallets are supported.\n---\n\n# Tres Finance — Asset Balance Validation\n\n## Overview\n\nThis skill validates wallet balances in **Tres Finance** against **DeBank**, providing a clear discrepancy report as both an interactive HTML file and a PDF. It compares per-asset token amounts (including DeFi position underlying tokens) for each EVM wallet and flags matches, minor differences, major discrepancies, missing assets, untracked tokens, and unmatched positions.\n\n> **Scope:** Only EVM-compatible wallets are supported (DeBank limitation). Exchange accounts, non-EVM chains, and empty wallets are skipped.\n\n---\n\n## When to Use\n\nTrigger this skill whenever a user asks to:\n\n- Validate or verify their TRES balances\n- Cross-check or audit wallets against external on-chain data\n- Compare TRES data to DeBank\n- Check if their balances are correct\n\n**Example phrases:**\n- *\"Validate my balances\"*\n- *\"Check my wallets against DeBank\"*\n- *\"Are my TRES balances correct?\"*\n- *\"Show me any discrepancies between TRES and on-chain data\"*\n\n---\n\n## Prerequisites\n\n| Requirement | Details |\n|---|---|\n| TRES Finance access | Must be authenticated via `get_viewer` |\n| DeBank API key | Free key available at [cloud.debank.com](https:\u002F\u002Fcloud.debank.com) |\n| EVM wallets | At least one `0x...` wallet tracked in TRES |\n\n---\n\n## Process Overview\n\n### Step 1 — Authenticate with TRES\nCall `get_viewer` to confirm the organization name.\n\n### Step 2 — Fetch wallets and balances from TRES\n\n**IMPORTANT — Timeout handling:** The `internalAccount` query with both `balances` and `positions` will timeout for large orgs. Split into two separate queries:\n\n**Query 1: Wallets + Balances only (no positions)**\n\n```graphql\nquery {\n  internalAccount {\n    results {\n      id\n      name\n      identifier\n      isExchange\n      platforms\n      balances {\n        amount\n        asset {\n          symbol\n          contract { identifier }\n        }\n        fiatValue { value unitPrice fiatCurrency }\n      }\n    }\n  }\n}\n```\n\n> **Note:** The `amount` field is returned as a **string**, not a number. Always `float()` it before arithmetic.\n\n**Wallet classification:**\n\n| Type | Condition | Validated? |\n|---|---|---|\n| EVM | `0x...` address + EVM platform + `isExchange: false` | ✅ Yes |\n| Exchange | `isExchange: true` | ❌ No |\n| Non-EVM | Bitcoin, Tezos, Tron, etc. | ❌ No |\n| Empty | No asset balances | ❌ No |\n\n**Supported EVM platforms:** Ethereum, Arbitrum, Optimism, Polygon, Base, Avalanche, Binance, Gnosis Chain, zkSync, Fantom, Celo, Berachain, Linea, Scroll, Sonic, HyperEVM.\n\n### Step 3 — Fetch DeFi positions from TRES\n\n**Do NOT use the `positions` sub-field on `internalAccount`** — it returns all historical snapshots (can be 3000+ entries per wallet) and will timeout or exceed token limits.\n\nInstead, use the dedicated `getStatelessWalletsPositions` query which returns **current** positions only:\n\n```graphql\nquery {\n  getStatelessWalletsPositions(\n    walletIdentifiers: [\"0x...\"],\n    platform: ETHEREUM,\n    application: \"aave-v3\"\n  ) {\n    walletIdentifier\n    displayName\n    positionType\n    platform\n    children {\n      symbol\n      amount\n      assetIdentifier\n      fiatValue\n    }\n    fiatValue\n    id\n  }\n}\n```\n\n**Required parameters:**\n- `walletIdentifiers`: array of wallet addresses\n- `platform`: must be an enum value like `ETHEREUM`, `POLYGON`, `ARBITRUM`, etc.\n\n**Optional but recommended:**\n- `application`: filter by protocol (e.g. `\"aave-v3\"`, `\"verse\"`, `\"lido\"`, `\"merkl\"`, `\"uniswap-v4\"`, `\"sablier\"`, `\"ethena\"`, `\"stakewise\"`, `\"quickswap\"`, `\"steer\"`, `\"yieldnest\"`, `\"morphoblue\"`)\n\n**IMPORTANT:** Without the `application` filter, the query returns empty results. Always specify the application.\n\n**Batching strategy:**\n1. First, fetch DeBank `all_complex_protocol_list` for each wallet to discover which protocols have positions\n2. Map DeBank protocol names to TRES application names (lowercase, hyphenated)\n3. Use GraphQL aliases to batch multiple wallet+platform+application combos into a single query:\n\n```graphql\nquery {\n  a1: getStatelessWalletsPositions(walletIdentifiers: [\"0x...\"], platform: ETHEREUM, application: \"aave-v3\") {\n    walletIdentifier displayName positionType platform id\n    children { symbol amount assetIdentifier fiatValue }\n  }\n  a2: getStatelessWalletsPositions(walletIdentifiers: [\"0x...\"], platform: ETHEREUM, application: \"verse\") {\n    walletIdentifier displayName positionType platform id\n    children { symbol amount assetIdentifier fiatValue }\n  }\n}\n```\n\nKeep each batched query to ~6 aliases max to avoid timeouts.\n\n### Step 4 — Retrieve DeBank API key\n\nRead `DEBANK_API_KEY` from plugin user config — do **not** ask the user to paste it in chat.\nIf the key is absent or empty, stop and display:\n\n> \"DEBANK_API_KEY is not configured. Please add it via the plugin settings (obtain your key at https:\u002F\u002Fcloud.debank.com).\"\n\n### Step 5 — Fetch DeBank data via bash\n\nFor each EVM wallet, fetch **two** endpoints:\n\n1. **Token balances:** `all_token_list` — covers all chains without requiring a `chain_id`\n2. **DeFi protocol positions:** `all_complex_protocol_list` — returns LP, staking, lending positions with underlying token amounts\n\nUse `--data-urlencode` with `-G` so the wallet address is never shell-interpolated into the URL string:\n\n```bash\n# Token balances\ncurl -s -G \\\n  -H \"AccessKey: ${user_config.DEBANK_API_KEY}\" \\\n  --data-urlencode \"id=$WALLET_ADDR\" \\\n  \"https:\u002F\u002Fpro-openapi.debank.com\u002Fv1\u002Fuser\u002Fall_token_list\"\n\n# DeFi positions\ncurl -s -G \\\n  -H \"AccessKey: ${user_config.DEBANK_API_KEY}\" \\\n  --data-urlencode \"id=$WALLET_ADDR\" \\\n  \"https:\u002F\u002Fpro-openapi.debank.com\u002Fv1\u002Fuser\u002Fall_complex_protocol_list\"\n```\n\n**Fiat-value filter:** Discard any token where `price \u003C 0.01` — these are excluded from all matching, display, and reporting.\n\n**Rate limiting:** Add a 0.3s delay between wallet requests to avoid 429 errors.\n\n### Step 6 — Match regular assets\n\nMatching must be **chain-aware**. DeBank's `all_token_list` returns a `chain` field per\ntoken (e.g. `\"eth\"`, `\"arb\"`, `\"bsc\"`). TRES balances are tied to a specific platform\nvia the wallet's `platforms` array or the balance's context. Always prefer a per-chain\nmatch before falling back to cross-chain aggregation.\n\n**Chain ID mapping** (DeBank `chain` → TRES platform):\n\n| DeBank `chain` | TRES platform |\n|---|---|\n| `eth` | ETHEREUM |\n| `arb` | ARBITRUM |\n| `op` | OPTIMISM |\n| `matic` | POLYGON |\n| `base` | BASE |\n| `bsc` | BNB (Binance) |\n| `avax` | AVALANCHE |\n| `ftm` | FANTOM |\n| `xdai` | GNOSIS |\n| `era` | ZKSYNC |\n| `celo` | CELO |\n| `linea` | LINEA |\n| `scrl` | SCROLL |\n| `mnt` | MOONBEAM |\n\n**Matching order (most specific first):**\n\n1. **Contract + chain match (best):** `asset.contract.identifier` (lowercase) vs DeBank\n   token `id` (lowercase), on the same chain. This is the most precise match.\n2. **Symbol + chain match:** For native tokens (no contract), match by `asset.symbol`\n   (case-insensitive) AND DeBank `chain` matching the TRES platform for that balance row.\n   This correctly handles the common case where a wallet holds ETH on both Ethereum and\n   Arbitrum — each TRES balance row matches its corresponding DeBank per-chain entry.\n3. **Symbol-only match (last resort):** If a TRES native token balance cannot be matched\n   to any specific DeBank chain entry, fall back to symbol-only matching. This handles\n   edge cases where TRES or DeBank uses a different chain label.\n\n### Step 7 — Match DeFi position underlying tokens\n\nThis is a critical step that compares DeFi position underlying tokens between TRES and DeBank.\n\n#### 7a. Filter out position NFT rows\n\nRemove position NFT tokens from the regular comparison (e.g. `UNI-V3-POS`, `RCL`, `SAB-LOCKUP`, `SLP`, `STEER`, `UNI-V4-POS`). These are replaced by the underlying token rows from positions.\n\n#### 7b. Process TRES positions\n\nFrom `getStatelessWalletsPositions` results, for each position:\n1. Aggregate `children` by symbol — a position may have multiple entries for the same token (e.g. supply + unclaimed rewards in QuickSwap or Uniswap V4), so sum the amounts\n2. Use `displayName` to identify the protocol and token composition\n\n```python\n# Example: aggregate children for a position\ndef aggregate_children(children):\n    agg = {}\n    for c in children:\n        sym = c['symbol']\n        amt = float(c['amount']) if isinstance(c['amount'], str) else c['amount']\n        if sym not in agg:\n            agg[sym] = {'amount': 0, 'assetIdentifier': c.get('assetIdentifier', '')}\n        agg[sym]['amount'] += amt\n    return agg\n```\n\n#### 7c. Process DeBank positions\n\nFrom `all_complex_protocol_list`, for each protocol's `portfolio_item_list`:\n1. Extract `asset_token_list` for supply tokens and `reward_token_list` for rewards\n2. Use protocol `name` and item `name` (e.g. \"Lending\", \"Liquidity Pool\") as the position label\n\n#### 7d. Compare position tokens\n\nMatch DeBank protocol positions to TRES positions by:\n1. Protocol name match (case-insensitive, first word)\n2. Token symbol overlap between children\n\nFor each matched position token:\n- **If TRES data exists:** Compare amounts, compute delta %, assign match\u002Fminor\u002Fmajor status\n- **If no TRES data:** Assign `position` status (purple badge)\n\n### Step 8 — Build and render the report\n\nCreate **two outputs**:\n1. **Interactive HTML file** — Dark-themed, with filter buttons, collapsible wallet cards, dedicated DeFi Positions section per wallet\n2. **PDF report** — Landscape A4, all wallet tables expanded, using reportlab\n\nSave both to the outputs directory.\n\n---\n\n## Report Layout — CRITICAL\n\n### DeFi Positions must be visually separated\n\nEach wallet card in the report MUST have **two distinct sections**:\n\n1. **DeFi Positions section** (top, purple-themed) — A dedicated box with purple border and dark purple background (`#1a1033` bg, `#7c3aed` border) showing all position-related rows. This section appears BEFORE the regular token table.\n\n2. **Regular tokens table** (below) — Standard token balance comparison rows.\n\n### Position asset indicator\n\nEvery position asset row MUST have a **purple dot indicator** (CSS circle, 8px, `#a855f7`) next to the asset name. This ensures positions are instantly recognizable:\n\n```html\n\u003Cspan style=\"display:inline-block;width:8px;height:8px;background:#a855f7;border-radius:50%;margin-right:6px;vertical-align:middle;\">\u003C\u002Fspan>\n```\n\n> **Do NOT use emojis or inline SVGs** — they may not render in all viewers. Use pure CSS shapes only.\n\n### Position rows show dual badges\n\nPosition rows that have a TRES match show TWO badges:\n- A `POSITION` badge (purple)\n- A match-status badge (`MATCH`\u002F`MINOR`\u002F`MAJOR`)\n\n### Auto-expand wallets with positions\n\nWallet cards that contain DeFi positions should be auto-expanded (`\u003Cdetails open>`) so positions are immediately visible.\n\n---\n\n## Number Formatting Rules\n\n### Token amounts\n- Max **3 decimal places** for all amounts\n- Amounts ≥ 1,000: use comma separator with 3 decimals (e.g., `846,492.356`)\n- Amounts \u003C 1,000: use 3 decimals (e.g., `0.386`)\n- Very small amounts (\u003C 0.000001): use scientific notation (e.g., `3.54e-07`)\n- Null\u002Fmissing: show em dash `—`\n\n```javascript\nfunction formatAmount(n) {\n  if (n === null || n === undefined) return '\\u2014';\n  if (Math.abs(n) \u003C 0.000001) return n.toExponential(2);\n  if (Math.abs(n) >= 1000) return n.toLocaleString('en-US', {minimumFractionDigits: 2, maximumFractionDigits: 3});\n  return n.toFixed(3);\n}\n```\n\n### Fiat values\n- Shown in **parentheses** next to every token amount: `846,492.356 ($17,562.21)`\n- Shown in **parentheses** next to every delta %: `5.33% ($81.21)`\n- Format: `($X,XXX.XX)` — always 2 decimal places, comma-separated thousands\n- Null\u002Fmissing: omit entirely (no empty parentheses)\n\n### Fiat value computation — CRITICAL\n\n**Use a single price source** (DeBank's token price) to compute fiat values for **both** the TRES and DeBank columns. This ensures:\n- When amounts match, the fiat delta is $0 (not inflated by pricing source differences)\n- The fiat delta next to delta % represents the actual USD value of the amount discrepancy\n\n```python\n# For regular tokens:\nprice = debank_token['price']  # single source\ntres_fiat = tres_amount * price\ndebank_fiat = debank_amount * price\ndelta_fiat = abs(tres_amount - debank_amount) * price\n\n# For position tokens — same principle:\nprice = debank_asset_token['price']\ntres_fiat = tres_aggregated_amount * price\ndebank_fiat = debank_amount * price\ndelta_fiat = abs(tres_aggregated_amount - debank_amount) * price\n```\n\n**Do NOT** use TRES `fiatValue` for the TRES column and DeBank price for the DeBank column — this creates misleading fiat deltas when TRES and DeBank use different token prices.\n\n---\n\n## Native Token Matching (Multi-Chain Wallets)\n\nNative tokens (ETH, BNB, etc.) often appear on multiple chains in TRES for a single\nwallet (e.g., ETH on Ethereum + ETH on Arbitrum). DeBank's `all_token_list` returns\n**separate per-chain entries** with a `chain` field — it does NOT aggregate them.\n\n**Rule: match per-chain first, aggregate only as a last resort.**\n\n1. **Per-chain match (default):** For each TRES native token balance, use the balance's\n   platform context to find the corresponding DeBank entry by symbol + chain. For example,\n   a wallet with 0.00956 ETH on Ethereum and 0.001168 ETH on Arbitrum should produce two\n   separate comparison rows — one matched to DeBank's `chain: \"eth\"` entry and one to\n   `chain: \"arb\"`.\n\n2. **Aggregation fallback (rare):** Only aggregate TRES balances across chains when\n   DeBank returns fewer entries than TRES for the same symbol. This can happen if DeBank\n   merges certain bridged token balances. When aggregating, add a note like\n   `\"Aggregated: ETH (eth) + ETH (arb)\"`.\n\n**Why this matters:** Blindly aggregating before comparing creates false discrepancies.\nIf Ethereum ETH matches perfectly but Arbitrum ETH has a gap, aggregation masks the\nEthereum match and produces a single misleading delta. Per-chain matching preserves\ngranularity and makes it easy to identify exactly which chain is out of sync.\n\n---\n\n## Status Badges\n\n| Badge | Color | Hex | Meaning |\n|---|---|---|---|\n| **Match** | Green | `#22c55e` | Delta \u003C 1% |\n| **Minor** | Orange | `#f59e0b` | Delta 1–10% |\n| **Major** | Red | `#ef4444` | Delta > 10% |\n| **Missing** | Grey | `#6b7280` | Asset in TRES but not found in DeBank |\n| **Untracked** | Blue | `#3b82f6` | Asset in DeBank but not tracked in TRES |\n| **Position** | Purple | `#a855f7` | DeFi position token (with or without TRES data) |\n\n---\n\n## Report Sections\n\nThe rendered report (both HTML and PDF) includes:\n\n1. **Summary cards** — Wallets checked, assets compared, matched, minor, major, missing, untracked, positions, and match rate %\n2. **Filter bar** (HTML only) — Buttons to filter by status: All, Match, Minor, Major, Missing, Untracked, Position\n3. **Per-wallet card** containing:\n   - **DeFi Positions box** (purple-themed, at top) — Position assets with purple dot indicator, protocol label, dual status badges\n   - **Regular tokens table** — Each asset with symbol, chain, TRES amount (+ fiat), DeBank amount (+ fiat), delta % (+ fiat delta), status badge\n4. **Skipped wallets** — List of wallets not validated and the reason why\n5. **Notes & Caveats** — Sync lag, DeFi positions explanation, native token aggregation, price filter, missing\u002Funtracked explanations\n\n---\n\n## Important Caveats\n\n- **Sync lag:** TRES balances reflect the last sync time. Recent on-chain activity may show as a discrepancy.\n- **DeFi positions:** Underlying tokens from LP, staking, and lending positions are shown as individual rows in a dedicated purple section. Both TRES and DeBank amounts are compared where TRES position data is available. Active LP positions will naturally show some discrepancy because TRES and DeBank snapshot at different times.\n- **Native token matching:** ETH, BNB, etc. are matched per-chain first (using DeBank's `chain` field mapped to TRES platforms). Multi-chain balances are only aggregated as a fallback when DeBank returns fewer entries than TRES for the same symbol.\n- **Multi-chain coverage:** DeBank `all_token_list` covers all chains; tokens on chains not configured in TRES appear as \"Untracked.\"\n- **Price filter:** Tokens with `price \u003C $0.01` (zero-price, null, or micro-cap) are excluded from all reports.\n- **Missing in DeBank:** Typically spam\u002Fairdrop tokens (HEX, ASCZBR, etc.) that DeBank filters out.\n- **Untracked in TRES:** Tokens on chains not configured in TRES, or small dust amounts.\n\n---\n\n## Error Handling\n\n| Situation | Response |\n|---|---|\n| DeBank `401` error | Display \"Invalid API key\" in artifact |\n| DeBank `429` error | Display \"Rate limited — reload in 60s\" |\n| Empty token list for non-empty wallet | Flag wallet as suspicious |\n| Non-EVM wallet | Skip and list in \"Skipped wallets\" section |\n| `internalAccount` positions timeout | Use `getStatelessWalletsPositions` per wallet\u002Fplatform\u002Fapplication instead |\n| `getStatelessWalletsPositions` returns empty | Ensure `application` parameter is provided; without it the query returns empty |\n| Position ID not extractable | Skip that position (don't crash) |\n| `amount` field is string not number | Always cast with `float()` before arithmetic |\n\n---\n\n## Next Steps (after report renders)\n\n- **Re-run** — Rebuild the report with fresh data at any time\n- **Drill down** — For any Major discrepancy, inspect the specific asset across platforms in TRES to identify which chain is out of sync\n- **Position discrepancies** — Minor discrepancies on active LP positions are expected due to different snapshot times between TRES and DeBank\n","# Tres Finance — Asset Balance Validation\n\n## Overview\n\nThis skill validates wallet balances in **Tres Finance** against **DeBank**, providing a clear discrepancy report as both an interactive HTML file and a PDF. It compares per-asset token amounts (including DeFi position underlying tokens) for each EVM wallet and flags matches, minor differences, major discrepancies, missing assets, untracked tokens, and unmatched positions.\n\n> **Scope:** Only EVM-compatible wallets are supported (DeBank limitation). Exchange accounts, non-EVM chains, and empty wallets are skipped.\n\n---\n\n## When to Use\n\nTrigger this skill whenever a user asks to:\n\n- Validate or verify their TRES balances\n- Cross-check or audit wallets against external on-chain data\n- Compare TRES data to DeBank\n- Check if their balances are correct\n\n**Example phrases:**\n- *\"Validate my balances\"*\n- *\"Check my wallets against DeBank\"*\n- *\"Are my TRES balances correct?\"*\n- *\"Show me any discrepancies between TRES and on-chain data\"*\n\n---\n\n## Prerequisites\n\n| Requirement | Details |\n|---|---|\n| TRES Finance access | Must be authenticated via `get_viewer` |\n| DeBank API key | Free key available at [cloud.debank.com](https:\u002F\u002Fcloud.debank.com) |\n| EVM wallets | At least one `0x...` wallet tracked in TRES |\n\n---\n\n## Process Overview\n\n### Step 1 — Authenticate with TRES\nCall `get_viewer` to confirm the organization name.\n\n### Step 2 — Fetch wallets and balances from TRES\n\n**IMPORTANT — Timeout handling:** The `internalAccount` query with both `balances` and `positions` will timeout for large orgs. Split into two separate queries:\n\n**Query 1: Wallets + Balances only (no positions)**\n\n```graphql\nquery {\n  internalAccount {\n    results {\n      id\n      name\n      identifier\n      isExchange\n      platforms\n      balances {\n        amount\n        asset {\n          symbol\n          contract { identifier }\n        }\n        fiatValue { value unitPrice fiatCurrency }\n      }\n    }\n  }\n}\n```\n\n> **Note:** The `amount` field is returned as a **string**, not a number. Always `float()` it before arithmetic.\n\n**Wallet classification:**\n\n| Type | Condition | Validated? |\n|---|---|---|\n| EVM | `0x...` address + EVM platform + `isExchange: false` | ✅ Yes |\n| Exchange | `isExchange: true` | ❌ No |\n| Non-EVM | Bitcoin, Tezos, Tron, etc. | ❌ No |\n| Empty | No asset balances | ❌ No |\n\n**Supported EVM platforms:** Ethereum, Arbitrum, Optimism, Polygon, Base, Avalanche, Binance, Gnosis Chain, zkSync, Fantom, Celo, Berachain, Linea, Scroll, Sonic, HyperEVM.\n\n### Step 3 — Fetch DeFi positions from TRES\n\n**Do NOT use the `positions` sub-field on `internalAccount`** — it returns all historical snapshots (can be 3000+ entries per wallet) and will timeout or exceed token limits.\n\nInstead, use the dedicated `getStatelessWalletsPositions` query which returns **current** positions only:\n\n```graphql\nquery {\n  getStatelessWalletsPositions(\n    walletIdentifiers: [\"0x...\"],\n    platform: ETHEREUM,\n    application: \"aave-v3\"\n  ) {\n    walletIdentifier\n    displayName\n    positionType\n    platform\n    children {\n      symbol\n      amount\n      assetIdentifier\n      fiatValue\n    }\n    fiatValue\n    id\n  }\n}\n```\n\n**Required parameters:**\n- `walletIdentifiers`: array of wallet addresses\n- `platform`: must be an enum value like `ETHEREUM`, `POLYGON`, `ARBITRUM`, etc.\n\n**Optional but recommended:**\n- `application`: filter by protocol (e.g. `\"aave-v3\"`, `\"verse\"`, `\"lido\"`, `\"merkl\"`, `\"uniswap-v4\"`, `\"sablier\"`, `\"ethena\"`, `\"stakewise\"`, `\"quickswap\"`, `\"steer\"`, `\"yieldnest\"`, `\"morphoblue\"`)\n\n**IMPORTANT:** Without the `application` filter, the query returns empty results. Always specify the application.\n\n**Batching strategy:**\n1. First, fetch DeBank `all_complex_protocol_list` for each wallet to discover which protocols have positions\n2. Map DeBank protocol names to TRES application names (lowercase, hyphenated)\n3. Use GraphQL aliases to batch multiple wallet+platform+application combos into a single query:\n\n```graphql\nquery {\n  a1: getStatelessWalletsPositions(walletIdentifiers: [\"0x...\"], platform: ETHEREUM, application: \"aave-v3\") {\n    walletIdentifier displayName positionType platform id\n    children { symbol amount assetIdentifier fiatValue }\n  }\n  a2: getStatelessWalletsPositions(walletIdentifiers: [\"0x...\"], platform: ETHEREUM, application: \"verse\") {\n    walletIdentifier displayName positionType platform id\n    children { symbol amount assetIdentifier fiatValue }\n  }\n}\n```\n\nKeep each batched query to ~6 aliases max to avoid timeouts.\n\n### Step 4 — Retrieve DeBank API key\n\nRead `DEBANK_API_KEY` from plugin user config — do **not** ask the user to paste it in chat.\nIf the key is absent or empty, stop and display:\n\n> \"DEBANK_API_KEY is not configured. Please add it via the plugin settings (obtain your key at https:\u002F\u002Fcloud.debank.com).\"\n\n### Step 5 — Fetch DeBank data via bash\n\nFor each EVM wallet, fetch **two** endpoints:\n\n1. **Token balances:** `all_token_list` — covers all chains without requiring a `chain_id`\n2. **DeFi protocol positions:** `all_complex_protocol_list` — returns LP, staking, lending positions with underlying token amounts\n\nUse `--data-urlencode` with `-G` so the wallet address is never shell-interpolated into the URL string:\n\n```bash\n# Token balances\ncurl -s -G \\\n  -H \"AccessKey: ${user_config.DEBANK_API_KEY}\" \\\n  --data-urlencode \"id=$WALLET_ADDR\" \\\n  \"https:\u002F\u002Fpro-openapi.debank.com\u002Fv1\u002Fuser\u002Fall_token_list\"\n\n# DeFi positions\ncurl -s -G \\\n  -H \"AccessKey: ${user_config.DEBANK_API_KEY}\" \\\n  --data-urlencode \"id=$WALLET_ADDR\" \\\n  \"https:\u002F\u002Fpro-openapi.debank.com\u002Fv1\u002Fuser\u002Fall_complex_protocol_list\"\n```\n\n**Fiat-value filter:** Discard any token where `price \u003C 0.01` — these are excluded from all matching, display, and reporting.\n\n**Rate limiting:** Add a 0.3s delay between wallet requests to avoid 429 errors.\n\n### Step 6 — Match regular assets\n\nMatching must be **chain-aware**. DeBank's `all_token_list` returns a `chain` field per\ntoken (e.g. `\"eth\"`, `\"arb\"`, `\"bsc\"`). TRES balances are tied to a specific platform\nvia the wallet's `platforms` array or the balance's context. Always prefer a per-chain\nmatch before falling back to cross-chain aggregation.\n\n**Chain ID mapping** (DeBank `chain` → TRES platform):\n\n| DeBank `chain` | TRES platform |\n|---|---|\n| `eth` | ETHEREUM |\n| `arb` | ARBITRUM |\n| `op` | OPTIMISM |\n| `matic` | POLYGON |\n| `base` | BASE |\n| `bsc` | BNB (Binance) |\n| `avax` | AVALANCHE |\n| `ftm` | FANTOM |\n| `xdai` | GNOSIS |\n| `era` | ZKSYNC |\n| `celo` | CELO |\n| `linea` | LINEA |\n| `scrl` | SCROLL |\n| `mnt` | MOONBEAM |\n\n**Matching order (most specific first):**\n\n1. **Contract + chain match (best):** `asset.contract.identifier` (lowercase) vs DeBank\n   token `id` (lowercase), on the same chain. This is the most precise match.\n2. **Symbol + chain match:** For native tokens (no contract), match by `asset.symbol`\n   (case-insensitive) AND DeBank `chain` matching the TRES platform for that balance row.\n   This correctly handles the common case where a wallet holds ETH on both Ethereum and\n   Arbitrum — each TRES balance row matches its corresponding DeBank per-chain entry.\n3. **Symbol-only match (last resort):** If a TRES native token balance cannot be matched\n   to any specific DeBank chain entry, fall back to symbol-only matching. This handles\n   edge cases where TRES or DeBank uses a different chain label.\n\n### Step 7 — Match DeFi position underlying tokens\n\nThis is a critical step that compares DeFi position underlying tokens between TRES and DeBank.\n\n#### 7a. Filter out position NFT rows\n\nRemove position NFT tokens from the regular comparison (e.g. `UNI-V3-POS`, `RCL`, `SAB-LOCKUP`, `SLP`, `STEER`, `UNI-V4-POS`). These are replaced by the underlying token rows from positions.\n\n#### 7b. Process TRES positions\n\nFrom `getStatelessWalletsPositions` results, for each position:\n1. Aggregate `children` by symbol — a position may have multiple entries for the same token (e.g. supply + unclaimed rewards in QuickSwap or Uniswap V4), so sum the amounts\n2. Use `displayName` to identify the protocol and token composition\n\n```python\n# Example: aggregate children for a position\ndef aggregate_children(children):\n    agg = {}\n    for c in children:\n        sym = c['symbol']\n        amt = float(c['amount']) if isinstance(c['amount'], str) else c['amount']\n        if sym not in agg:\n            agg[sym] = {'amount': 0, 'assetIdentifier': c.get('assetIdentifier', '')}\n        agg[sym]['amount'] += amt\n    return agg\n```\n\n#### 7c. Process DeBank positions\n\nFrom `all_complex_protocol_list`, for each protocol's `portfolio_item_list`:\n1. Extract `asset_token_list` for supply tokens and `reward_token_list` for rewards\n2. Use protocol `name` and item `name` (e.g. \"Lending\", \"Liquidity Pool\") as the position label\n\n#### 7d. Compare position tokens\n\nMatch DeBank protocol positions to TRES positions by:\n1. Protocol name match (case-insensitive, first word)\n2. Token symbol overlap between children\n\nFor each matched position token:\n- **If TRES data exists:** Compare amounts, compute delta %, assign match\u002Fminor\u002Fmajor status\n- **If no TRES data:** Assign `position` status (purple badge)\n\n### Step 8 — Build and render the report\n\nCreate **two outputs**:\n1. **Interactive HTML file** — Dark-themed, with filter buttons, collapsible wallet cards, dedicated DeFi Positions section per wallet\n2. **PDF report** — Landscape A4, all wallet tables expanded, using reportlab\n\nSave both to the outputs directory.\n\n---\n\n## Report Layout — CRITICAL\n\n### DeFi Positions must be visually separated\n\nEach wallet card in the report MUST have **two distinct sections**:\n\n1. **DeFi Positions section** (top, purple-themed) — A dedicated box with purple border and dark purple background (`#1a1033` bg, `#7c3aed` border) showing all position-related rows. This section appears BEFORE the regular token table.\n\n2. **Regular tokens table** (below) — Standard token balance comparison rows.\n\n### Position asset indicator\n\nEvery position asset row MUST have a **purple dot indicator** (CSS circle, 8px, `#a855f7`) next to the asset name. This ensures positions are instantly recognizable:\n\n```html\n\u003Cspan style=\"display:inline-block;width:8px;height:8px;background:#a855f7;border-radius:50%;margin-right:6px;vertical-align:middle;\">\u003C\u002Fspan>\n```\n\n> **Do NOT use emojis or inline SVGs** — they may not render in all viewers. Use pure CSS shapes only.\n\n### Position rows show dual badges\n\nPosition rows that have a TRES match show TWO badges:\n- A `POSITION` badge (purple)\n- A match-status badge (`MATCH`\u002F`MINOR`\u002F`MAJOR`)\n\n### Auto-expand wallets with positions\n\nWallet cards that contain DeFi positions should be auto-expanded (`\u003Cdetails open>`) so positions are immediately visible.\n\n---\n\n## Number Formatting Rules\n\n### Token amounts\n- Max **3 decimal places** for all amounts\n- Amounts ≥ 1,000: use comma separator with 3 decimals (e.g., `846,492.356`)\n- Amounts \u003C 1,000: use 3 decimals (e.g., `0.386`)\n- Very small amounts (\u003C 0.000001): use scientific notation (e.g., `3.54e-07`)\n- Null\u002Fmissing: show em dash `—`\n\n```javascript\nfunction formatAmount(n) {\n  if (n === null || n === undefined) return '\\u2014';\n  if (Math.abs(n) \u003C 0.000001) return n.toExponential(2);\n  if (Math.abs(n) >= 1000) return n.toLocaleString('en-US', {minimumFractionDigits: 2, maximumFractionDigits: 3});\n  return n.toFixed(3);\n}\n```\n\n### Fiat values\n- Shown in **parentheses** next to every token amount: `846,492.356 ($17,562.21)`\n- Shown in **parentheses** next to every delta %: `5.33% ($81.21)`\n- Format: `($X,XXX.XX)` — always 2 decimal places, comma-separated thousands\n- Null\u002Fmissing: omit entirely (no empty parentheses)\n\n### Fiat value computation — CRITICAL\n\n**Use a single price source** (DeBank's token price) to compute fiat values for **both** the TRES and DeBank columns. This ensures:\n- When amounts match, the fiat delta is $0 (not inflated by pricing source differences)\n- The fiat delta next to delta % represents the actual USD value of the amount discrepancy\n\n```python\n# For regular tokens:\nprice = debank_token['price']  # single source\ntres_fiat = tres_amount * price\ndebank_fiat = debank_amount * price\ndelta_fiat = abs(tres_amount - debank_amount) * price\n\n# For position tokens — same principle:\nprice = debank_asset_token['price']\ntres_fiat = tres_aggregated_amount * price\ndebank_fiat = debank_amount * price\ndelta_fiat = abs(tres_aggregated_amount - debank_amount) * price\n```\n\n**Do NOT** use TRES `fiatValue` for the TRES column and DeBank price for the DeBank column — this creates misleading fiat deltas when TRES and DeBank use different token prices.\n\n---\n\n## Native Token Matching (Multi-Chain Wallets)\n\nNative tokens (ETH, BNB, etc.) often appear on multiple chains in TRES for a single\nwallet (e.g., ETH on Ethereum + ETH on Arbitrum). DeBank's `all_token_list` returns\n**separate per-chain entries** with a `chain` field — it does NOT aggregate them.\n\n**Rule: match per-chain first, aggregate only as a last resort.**\n\n1. **Per-chain match (default):** For each TRES native token balance, use the balance's\n   platform context to find the corresponding DeBank entry by symbol + chain. For example,\n   a wallet with 0.00956 ETH on Ethereum and 0.001168 ETH on Arbitrum should produce two\n   separate comparison rows — one matched to DeBank's `chain: \"eth\"` entry and one to\n   `chain: \"arb\"`.\n\n2. **Aggregation fallback (rare):** Only aggregate TRES balances across chains when\n   DeBank returns fewer entries than TRES for the same symbol. This can happen if DeBank\n   merges certain bridged token balances. When aggregating, add a note like\n   `\"Aggregated: ETH (eth) + ETH (arb)\"`.\n\n**Why this matters:** Blindly aggregating before comparing creates false discrepancies.\nIf Ethereum ETH matches perfectly but Arbitrum ETH has a gap, aggregation masks the\nEthereum match and produces a single misleading delta. Per-chain matching preserves\ngranularity and makes it easy to identify exactly which chain is out of sync.\n\n---\n\n## Status Badges\n\n| Badge | Color | Hex | Meaning |\n|---|---|---|---|\n| **Match** | Green | `#22c55e` | Delta \u003C 1% |\n| **Minor** | Orange | `#f59e0b` | Delta 1–10% |\n| **Major** | Red | `#ef4444` | Delta > 10% |\n| **Missing** | Grey | `#6b7280` | Asset in TRES but not found in DeBank |\n| **Untracked** | Blue | `#3b82f6` | Asset in DeBank but not tracked in TRES |\n| **Position** | Purple | `#a855f7` | DeFi position token (with or without TRES data) |\n\n---\n\n## Report Sections\n\nThe rendered report (both HTML and PDF) includes:\n\n1. **Summary cards** — Wallets checked, assets compared, matched, minor, major, missing, untracked, positions, and match rate %\n2. **Filter bar** (HTML only) — Buttons to filter by status: All, Match, Minor, Major, Missing, Untracked, Position\n3. **Per-wallet card** containing:\n   - **DeFi Positions box** (purple-themed, at top) — Position assets with purple dot indicator, protocol label, dual status badges\n   - **Regular tokens table** — Each asset with symbol, chain, TRES amount (+ fiat), DeBank amount (+ fiat), delta % (+ fiat delta), status badge\n4. **Skipped wallets** — List of wallets not validated and the reason why\n5. **Notes & Caveats** — Sync lag, DeFi positions explanation, native token aggregation, price filter, missing\u002Funtracked explanations\n\n---\n\n## Important Caveats\n\n- **Sync lag:** TRES balances reflect the last sync time. Recent on-chain activity may show as a discrepancy.\n- **DeFi positions:** Underlying tokens from LP, staking, and lending positions are shown as individual rows in a dedicated purple section. Both TRES and DeBank amounts are compared where TRES position data is available. Active LP positions will naturally show some discrepancy because TRES and DeBank snapshot at different times.\n- **Native token matching:** ETH, BNB, etc. are matched per-chain first (using DeBank's `chain` field mapped to TRES platforms). Multi-chain balances are only aggregated as a fallback when DeBank returns fewer entries than TRES for the same symbol.\n- **Multi-chain coverage:** DeBank `all_token_list` covers all chains; tokens on chains not configured in TRES appear as \"Untracked.\"\n- **Price filter:** Tokens with `price \u003C $0.01` (zero-price, null, or micro-cap) are excluded from all reports.\n- **Missing in DeBank:** Typically spam\u002Fairdrop tokens (HEX, ASCZBR, etc.) that DeBank filters out.\n- **Untracked in TRES:** Tokens on chains not configured in TRES, or small dust amounts.\n\n---\n\n## Error Handling\n\n| Situation | Response |\n|---|---|\n| DeBank `401` error | Display \"Invalid API key\" in artifact |\n| DeBank `429` error | Display \"Rate limited — reload in 60s\" |\n| Empty token list for non-empty wallet | Flag wallet as suspicious |\n| Non-EVM wallet | Skip and list in \"Skipped wallets\" section |\n| `internalAccount` positions timeout | Use `getStatelessWalletsPositions` per wallet\u002Fplatform\u002Fapplication instead |\n| `getStatelessWalletsPositions` returns empty | Ensure `application` parameter is provided; without it the query returns empty |\n| Position ID not extractable | Skip that position (don't crash) |\n| `amount` field is string not number | Always cast with `float()` before arithmetic |\n\n---\n\n## Next Steps (after report renders)\n\n- **Re-run** — Rebuild the report with fresh data at any time\n- **Drill down** — For any Major discrepancy, inspect the specific asset across platforms in TRES to identify which chain is out of sync\n- **Position discrepancies** — Minor discrepancies on active LP positions are expected due to different snapshot times between TRES and DeBank\n",{"name":5,"description":7},"main","163301d1904c0a994539f5226ce0fcd65b8652bf","tres-finance-plugin\u002Fskills\u002Ftres-asset-balance-validation",357,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-10 15:47:08",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add anthropics\u002Fclaude-plugins-community --skill tres-asset-balance-validation",{"tool":63,"command":64},"bunx","bunx skills add anthropics\u002Fclaude-plugins-community --skill tres-asset-balance-validation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-plugins-community --skill tres-asset-balance-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-asset-balance-validation\u002FSKILL.md",true,[],[72,104,125,147,171,195],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":87,"publishedAt":44},"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",[78,83,86],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[34,88,89,90,91,43,41,92,93,94,95,96,97,98,99,100,101,102,38,103],"tres wallets upload","upload","typing","ingestion","creation","xlsx","selection","MCP","confirmation","connect","collection","preview","api","batch","guides","request",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":44},"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",[],[111,89,25,112,113,114,43,115,116,117,33,118,119,120,40,31,121,122,123,124],"tres upload tx header validation","bulk","do","import","parsing","for","manual","fix","missing","general","workflow","csv","contacts","with",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":44},"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",[131],{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},[133,134,135,136,137,95,39,138,139,140,141,142,37,143,27,144,145,113,146,116],"tres tx story","Story","show","memory","hex","show me","analysis","analyze","me","diagram","flow","blockchain","STRING","visualize",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":44},"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",[153],{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},[155,156,157,158,135,159,95,39,160,161,162,100,163,164,165,166,167,168,169,170],"tres settings management","settings","management","SET","get","configure","ask","commit","change","organization","update","read","write","sync","mcp graphql","flags",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":179,"publishedAt":44},"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",[177,178],{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[180,181,182,135,183,43,184,95,185,186,187,188,189,140,190,191,192,193,164,194],"tres rollup rules","Rules","rollup","gas","up","impact","reduce","Connector","review","consolidate","create","transactions","delete","data-driven","activity",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":203,"publishedAt":44},"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",[201,202],{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[188,204,182,205,206,207,208,209,40,210,95,185,39,99,211,187,212,213,190,214],"tres rollup review","standalone","never","mode","issues","design","new","candidate","filter","valid","catch"]