[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718G9QZ4B2DJVEB3MAW5ZB1":3,"skill-same:01M718G9QZ4B2DJVEB3MAW5ZB1":81},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":6,"updatedAt":66,"install":67,"resources":80},"01M718G9QZ4B2DJVEB3MAW5ZB1","tres-wallets-upload",null,"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\".","anthropics\u002Fclaude-plugins-community","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M718C1RS4JJFM9KNJMTCAYJG",4874,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-wallets-upload\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"tres wallets upload","upload","wallets","request","on-chain","guides","batch","api","preview","collection","connect","confirmation","MCP","selection","xlsx","creation","chain","Wallet","ingestion","typing","2026-11-10 10:12:30",false,"---\nname: tres-wallets-upload\ndescription: >\n  Upload and onboard multiple on-chain wallets or exchange accounts into Tres Finance.\n  Use this skill whenever the user wants to add wallets, onboard wallets, import wallets,\n  upload wallet addresses, ingest wallets, or connect exchanges into Tres — whether from\n  a file (CSV\u002FExcel) or by typing them manually. This skill guides Claude through the full\n  flow: wallet type selection → input collection → validation → preview with editable\n  HTML table → exchange credential collection (if exchange) → user confirmation → batch\n  creation via the TRES MCP API. Always trigger this skill for wallet onboarding, wallet\n  data ingestion, or any request to \"add wallets to Tres\".\ncompatibility: \"Requires TRES Finance MCP connected (https:\u002F\u002Fai.tres.finance\u002Fmcp)\"\n---\n\n# TRES Wallet Upload Skill\n\nOnboard on-chain wallets and exchange accounts into Tres Finance with validation, preview, and confirmation.\n\n---\n\n> ⚠️ **EXECUTION RULE — READ BEFORE STARTING:**\n> This skill is a strict sequential checklist. You MUST follow every step in the exact order written — do not skip, merge, or reorder steps. Before moving to the next step, verify the current step is fully complete. Steps that involve API calls (schema fetch, existing-wallet check, batch mutation) are mandatory — never skip them to save time or because results seem obvious. If you catch yourself about to skip a step, stop and execute it first.\n\n---\n\n## Step 0 — Ask Wallet Type\n\nBefore doing anything else, ask the user what kind of wallet they want to add using `ask_user_input_v0`:\n\n```\nquestion: \"What would you like to add to Tres?\"\noptions:\n  - \"On-Chain Wallets (Ethereum, Solana, Bitcoin, etc.)\"\n  - \"Exchange Accounts (Binance, Coinbase, Kraken, etc.)\"\ntype: single_select\n```\n\n- If the user selects **On-Chain Wallets** → proceed to **[ON-CHAIN FLOW]** (Step OC-1)\n- If the user selects **Exchange Accounts** → proceed to **[EXCHANGE FLOW]** (Step EX-1)\n\n---\n\n---\n\n# ON-CHAIN FLOW\n\n---\n\n## Step OC-1 — Ask for Input Method\n\nAsk the user how they want to provide their on-chain wallets using `ask_user_input_v0`:\n\n```\nquestion: \"How would you like to add your wallets?\"\noptions:\n  - \"Upload a file (CSV or Excel)\"\n  - \"Enter manually in a table\"\ntype: single_select\n```\n\nWait for the user's response, then proceed to the matching option in Step OC-2.\n\n---\n\n## Step OC-2 — Collect Wallet Data\n\n### Option A: File Upload\nIf the user selects \"Upload a file\" (or uploads a CSV or Excel file directly):\n- Read the file with pandas \u002F openpyxl from `\u002Fmnt\u002Fuser-data\u002Fuploads\u002F`\n- Expected columns (flexible): `name`, `address` (or `identifier`), `network` (or `platform`), `tags` (optional), `description` (optional)\n- Normalise header names (case-insensitive, strip spaces, accept aliases)\n- Parse into a list of wallet dicts, then proceed to Step OC-3\n\n### Option B: Simple Manual Entry (conversational)\nIf the user selects \"Enter manually in a table\":\n- **Do NOT render an HTML widget.** Instead, ask the user to provide their wallets in plain text, one per line, in this format:\n  ```\n  Name | Address | Network | Tags (optional)\n  ```\n  Example:\n  ```\n  Treasury Hot | 0xABCD...1234 | ETHEREUM | defi,treasury\n  Cold Storage | bc1q...xyz | BITCOIN |\n  ```\n- Once the user pastes their wallets, parse the lines into a list of wallet dicts, then proceed to Step OC-4.\n- If the user is unsure of the network name, tell them to type it as best they can and you will fuzzy-match it to the correct `ParentPlatform` value.\n\n---\n\n## Step OC-3 — Fetch Live Platform List from Schema\n\n**Always** fetch the ParentPlatform enum values live from the TRES MCP schema — never hardcode them. Use:\n\n```graphql\n# Via TRES MCP introspect tool:\nintrospect(\"ParentPlatform\")\n```\n\nThis returns the full list of valid enum values to use in the network dropdown and for validation.\n\n### Identifying exchanges vs on-chain wallets\n\nTo filter the ParentPlatform list to on-chain platforms only, exclude any value that matches a known exchange\u002Fcustodian. The authoritative live list of supported exchanges is fetched in the Exchange Flow (Step EX-1). As a local heuristic for the on-chain filter, exclude these:\n\n```\nANCHORAGE, AQUANOW, ASCENDEX, B2C2, BACKPACK, BINANCE_EXCHANGE, BINANCE_EXCHANGE_TR,\nBITCOIN_SUISSE, BITFINEX, BITGET, BITGO, BITMEX, BITSO, BITSTAMP, BITVAVO, BREX,\nBTC_MARKETS, BTCTURK, BULLISH, BYBIT, CEFFU, CIRCLE, COBO, COINBASE, COINBASE_COMMERCE,\nCOINBASE_EXCHANGE, COINBASE_INTERNATIONAL, COINBASE_PRIME, COINEX, COPPER, CRYPTOCOM,\nCRYPTOCOM_EXCHANGE, CUSTOMERS_BANK, DERIBIT, EQUALSMONEY, FALCONX, FIDELITY,\nFIFTH_THIRD_BANK, FIREBLOCKS, FORDEFI_UTXO, FTX, FTXUS, GATEIO, GEMINI, HITBTC, HTX,\nKRAKEN, KRAKEN_CUSTODY, KRAKEN_FUTURES, KUCOIN, LAYERONE, LEDGER_ENTERPRISE, LMAX,\nLUKKA, M2, MERCADO, MERCURY, MERCURY_TREASURY, MEOW, MEOW_TREASURY, MESH_PAYMENTS,\nMORGAN_STANLEY, NONCO, OKX, PAXFUL, PARADEX, QONTO, QREDO, REVOLUT_FR, REVOLUT_UK,\nSVB_GO, SVB_ONLINE, SYGNUM, TALOS, VERTEX, WHITEBIT, WINTERMUTE, WISE_US,\nBANK_HAPOALIM_BIZ, BANK_HAPOALIM_INTERNATIONAL, BANK_OF_AMERICA,\nBANQUE_POPULAIRE_RIVES_DE_PARIS, CHASE, CHECKOUT\n```\n\nAny platform NOT in this list is treated as an on-chain wallet requiring a standard blockchain address.\n\n---\n\n## Step OC-4 — Validate Wallets\n\nRun ALL checks below. Collect errors per-row; do NOT abort early.\n\n### Required field checks\n| Field | Rule |\n|-------|------|\n| `name` | Non-empty string |\n| `identifier` | Non-empty string |\n| `parentPlatform` | Must be a valid `ParentPlatform` enum value (from live schema) |\n\n### Network name normalisation\nIf a network name from a CSV is lowercase or mixed-case (e.g. `tezos`, `Ethereum`), uppercase it and fuzzy-match to the nearest valid `ParentPlatform` enum value. Show a warning banner in the preview noting the normalisation and asking the user to confirm.\n\n### Address format validation per network (on-chain only)\nApply these regex rules for on-chain wallets. Skip for exchanges.\n\n| Network(s) | Rule |\n|---|---|\n| ETHEREUM, BNB, POLYGON, AVALANCHE_*, ARBITRUM, OPTIMISM, BASE, FANTOM, MOONBEAM, and other EVM chains | `^0x[0-9a-fA-F]{40}$` |\n| BITCOIN | P2PKH `1...`, P2SH `3...`, or Bech32 `bc1...` — 25–62 chars |\n| SOLANA | Base58, 32–44 chars: `^[1-9A-HJ-NP-Za-km-z]{32,44}$` |\n| TRON | `^T[1-9A-HJ-NP-Za-km-z]{33}$` |\n| TEZOS | `^tz[123][1-9A-HJ-NP-Za-km-z]{33}$` |\n| SUI, APTOS | `^0x[0-9a-fA-F]{62,64}$` |\n| STELLAR | Starts with `G`, 56 chars |\n| RIPPLE | Starts with `r`, 25–34 chars |\n| CARDANO | Starts with `addr1`, length > 50 |\n| NEAR | Ends in `.near` OR 64-char hex |\n| TON | Starts with `EQ` or `UQ`, 48 chars |\n| ALGORAND | 58-char Base32 uppercase |\n\n### Network–address mismatch detection\nFlag obvious mismatches (e.g. `0x...` address on SOLANA network, or Bitcoin address on ETHEREUM).\n\n### Duplicate detection\n\n**Within-batch duplicates:**\nFlag rows sharing the same `(identifier, parentPlatform)` pair. Mark both as errors.\n\n**Existing-wallet check against Tres (batches ≤ 200 wallets):**\n```graphql\n{\n  internalAccount(identifier_In: [\"addr1\", \"addr2\", ...]) {\n    results { id name identifier parentPlatform }\n  }\n}\n```\nBuild a lookup: `key = identifier.toLowerCase() + \"|\" + parentPlatform.toUpperCase()`\n- Match → mark as **⚠️ warning** (yellow): `\"Exists (ID: XXXXX)\"` — API will update, not duplicate\n- Summary bar must show: `X new | Y already exist | Z errors`\n\nFor batches > 200: skip the API check, show a note in the preview.\n\n---\n\n## Step OC-5 — Show Text Preview\n\n> 🚫 **HARD GATE:** Do NOT render this preview until Step OC-4 (validation) AND the existing-wallet Tres API check are both fully complete. Showing the preview without the API check is a violation of this skill.\n\n**Do NOT render an HTML widget.** Instead, present the wallet data as a clean markdown table in plain text so the user can review it:\n\n```\n| # | Name | Address | Network | Tags | Status |\n|---|------|---------|---------|------|--------|\n| 1 | Treasury Hot | 0xABCD...1234 | ETHEREUM | defi | ✅ New |\n| 2 | Cold Wallet | bc1q...xyz | BITCOIN | | ⚠️ Exists (ID: 12345) |\n| 3 | Bad Wallet | invalid-addr | SOLANA | | ❌ Invalid address |\n```\n\n- Show a summary line: `X new | Y already exist | Z errors`\n- List all errors below the table with row number and description:\n  ```\n  Errors:\n  - Row 3 (Bad Wallet): Invalid SOLANA address format\n  ```\n- If there are errors, tell the user to correct and re-paste the data before proceeding\n- If there are only warnings (existing wallets), ask: \"Ready to upload? Existing wallets will be updated. Type **yes** to confirm.\"\n- If all rows are valid, ask: \"Ready to upload N wallets to Tres Finance. Type **yes** to confirm.\"\n\nWhen the user confirms → proceed to Step OC-6.\n\n---\n\n## Step OC-6 — Final Confirmation\n\nWhen Claude receives `TRES_WALLET_UPLOAD_CONFIRMED:`:\n1. Parse the JSON payload\n2. Present a plain-text summary:\n   ```\n   About to upload N wallets to Tres Finance:\n   - 3 ETHEREUM wallets\n   - 2 SOLANA wallets\n   - 1 TEZOS wallet (will update existing)\n\n   Shall I proceed?\n   ```\n3. Wait for explicit user confirmation (\"yes\", \"confirm\", \"go ahead\")\n\n---\n\n## Step OC-7 — Execute Batch Upload\n\nCall `updateBatchInternalAccounts` via TRES MCP:\n\n```graphql\nmutation UpdateBatchInternalAccounts($internalAccounts: [InternalAccountInput]) {\n  updateBatchInternalAccounts(internalAccounts: $internalAccounts) {\n    internalAccounts {\n      id\n      name\n      identifier\n      parentPlatform\n      status\n    }\n    validationResults {\n      iaIdentifier\n      validationResult {\n        issueType\n        errorMessage\n      }\n    }\n  }\n}\n```\n\nVariables per wallet:\n```json\n{\n  \"name\": \"Treasury Hot\",\n  \"identifier\": \"0xABCD...\",\n  \"parentPlatform\": \"ETHEREUM\",\n  \"tags\": [\"defi\", \"treasury\"],\n  \"enforceCollectTransactions\": true\n}\n```\n\nNote: `platformKeys` is not included for on-chain wallets.\n\n### Chunking\nIf batch > 100 wallets, split into chunks of 50 and call sequentially.\n\n### Result handling\n- Parse `validationResults` — surface any `issueType` \u002F `errorMessage` to the user\n- Show success count and any failures\n- For failures, offer to retry just the failed wallets\n\n---\n\n---\n\n# EXCHANGE FLOW\n\n---\n\n## Step EX-1 — Introduction & Guide\n\nShow the user the integration guide link:\n\n> Before connecting an exchange, please review the **Tres Finance Exchange Integration Guide**:\n> 👉 https:\u002F\u002Fhelp.tres.finance\u002Farticle\u002Fintegrating-your-exchange-accounts-with-tres-finance\n\nThen fetch the **live validated exchange list** from TRES MCP — never hardcode it:\n\n```graphql\nquery GetAllValidatedExchanges {\n  ledgerFilters {\n    allValidatedExchanges {\n      id\n      displayName\n    }\n  }\n}\n```\n\nThis returns the authoritative list of supported exchanges (47 as of writing, but always fetch live). Sort A-Z by `displayName`. Present as a native `\u003Cselect>` dropdown using `ask_user_input_v0` or inline in a `show_widget` form, mirroring the Tres UI with a \"Connection Guidelines ↗\" link alongside the label.\n\n---\n\n## Step EX-2 — Fetch Required Fields for the Selected Exchange\n\nOnce the user selects an exchange, fetch its credential fields. **Use the `id` value (lowercase) as the `exchangeName`:**\n\n```graphql\nquery ExchangeRequiredFields {\n  exchangeRequiredFields {\n    requiredFields(exchangeName: \"\u003Cexchange_id_lowercase>\") {\n      name\n      type\n      description\n      mapping\n    }\n  }\n}\n```\n\n**Important:** Skip any field where `mapping` starts with `https:\u002F\u002F` — these are integration guide links, not credential inputs. Show them as a clickable link instead.\n\nStore the remaining fields. Each field has:\n- `name` — the credential field key\n- `description` — the human-readable label to show the user\n- `mapping` — the key used when constructing `platformKeys` (e.g. `platform_keys.api_key`)\n- `type` — use to determine input type\n\n---\n\n## Step EX-3 — Collect Exchange Credentials (Conversational)\n\n**Do NOT render an HTML widget.** Instead, ask the user for credentials in plain conversational steps.\n\nFirst, show the integration guide link:\n> 📖 Before connecting, review the guide: https:\u002F\u002Fhelp.tres.finance\u002Farticle\u002Fintegrating-your-exchange-accounts-with-tres-finance\n\nThen ask for the fields one by one (or all at once in a single prompt), clearly listing what is needed:\n\n```\nTo connect \u003CExchange Name>, I need the following:\n\n**Account Name** (required) — a friendly name for this account in Tres\n**API Key** (required)\n**API Secret** (required, will be stored securely)\n**Tags** (optional) — comma-separated tags\n\nPlease provide these values. Keep API secrets private — do not share them in public channels.\n```\n\n- For fields where `field.name` contains \"secret\", \"private\", \"signing\", or \"passphrase\" — note they will be stored securely\n- For optional fields (e.g. OKX sub-account), label them clearly as `(optional)`\n- Skip any field where `mapping` starts with `https:\u002F\u002F` — show it as a link instead\n\n### Mandatory confirmations (ask as yes\u002Fno questions before proceeding)\nBefore accepting the credentials, ask:\n1. \"Do you confirm the API key has **read-only permissions**? (yes\u002Fno)\"\n2. \"Do you agree to the **Tres Finance Terms of Service**? (yes\u002Fno)\"\n\nOnly proceed once both are confirmed.\n\nOnce all credentials and confirmations are collected, store them in the queue format and proceed to Step EX-4.\n\n---\n\n## Step EX-4 — Accumulate Exchange Accounts\n\nAfter collecting credentials for an exchange:\n1. Parse and store the account data in a pending queue\n2. Confirm: `✅ \u003CaccountName> (\u003Cexchange>) added to queue`\n3. Display the running queue as a brief list:\n   ```\n   Queued accounts:\n   1. My Binance Account (BINANCE_EXCHANGE)\n   ```\n4. Ask: \"Would you like to **add another exchange** or **proceed to upload**?\"\n\nIf user wants to add another → loop back to **Step EX-1** (queued accounts are preserved).\nIf user wants to proceed → go to **Step EX-5**.\n\n---\n\n## Step EX-5 — Final Review & Confirmation\n\nPresent a plain-text summary of all queued accounts:\n\n```\nReady to connect the following exchange accounts to Tres Finance:\n\n1. My Binance Account (BINANCE_EXCHANGE)\n2. Kraken Main (KRAKEN)\n\nShall I proceed?\n```\n\nWait for explicit user confirmation (\"yes\", \"confirm\", \"go ahead\", etc.)\n\n---\n\n## Step EX-6 — Execute Exchange Account Creation\n\nCall `updateBatchInternalAccounts` via TRES MCP for all queued accounts:\n\n```graphql\nmutation UpdateBatchInternalAccounts($internalAccounts: [InternalAccountInput]) {\n  updateBatchInternalAccounts(internalAccounts: $internalAccounts) {\n    internalAccounts {\n      id\n      name\n      identifier\n      parentPlatform\n      status\n    }\n    validationResults {\n      iaIdentifier\n      validationResult {\n        issueType\n        errorMessage\n      }\n    }\n  }\n}\n```\n\nVariables per exchange account:\n```json\n{\n  \"name\": \"\u003CaccountName>\",\n  \"identifier\": \"\u003CaccountName>\",\n  \"parentPlatform\": \"\u003CEXCHANGE_ID_UPPERCASE>\",\n  \"tags\": [\"\u003Ctag1>\"],\n  \"enforceCollectTransactions\": true,\n  \"platformKeys\": \"{\\\"api_key\\\": \\\"...\\\", \\\"api_secret\\\": \\\"...\\\"}\"\n}\n```\n\n**Important:**\n- `identifier` = account name (no blockchain address for exchanges)\n- `platformKeys` = a **JSON string** (not an object), built from `field.mapping` → value pairs collected in the form\n- `parentPlatform` = exchange `id` uppercased (e.g. `binance_exchange` → `BINANCE_EXCHANGE`)\n- Process all accounts in a single batch call where possible\n\n### Result handling\n- Show success\u002Ffailure per account\n- Surface `issueType` and `errorMessage` for failures\n- Offer to retry failed accounts\n\n---\n\n## Error Messages & Recovery\n\n| Situation | What to do |\n|-----------|-----------|\n| CSV has no `address` column | Ask user to map which column contains the wallet address |\n| Unknown network name | Fuzzy-match to nearest `ParentPlatform` enum value, show warning banner, ask user to confirm |\n| Address format invalid | Mark as error in preview; user must fix or remove the row before upload |\n| Duplicate in batch | Mark both rows as errors; user must remove or fix one |\n| Wallet already exists in Tres | Mark as ⚠️ warning (yellow); proceed — API will update it |\n| No file and no wallets typed | Prompt user to either upload a file or use the manual table |\n| Batch > 200 wallets | Skip existing-wallet API check; show informational note |\n| MCP mutation returns error | Show error per wallet; offer retry |\n| Exchange credentials rejected | Show the validation error and prompt user to re-enter credentials |\n| `exchangeRequiredFields` returns empty | Inform user that this exchange may need manual setup; link to the guide |\n| `allValidatedExchanges` returns empty | Fall back to informing user and linking to https:\u002F\u002Fhelp.tres.finance |\n","# TRES Wallet Upload Skill\n\nOnboard on-chain wallets and exchange accounts into Tres Finance with validation, preview, and confirmation.\n\n---\n\n> ⚠️ **EXECUTION RULE — READ BEFORE STARTING:**\n> This skill is a strict sequential checklist. You MUST follow every step in the exact order written — do not skip, merge, or reorder steps. Before moving to the next step, verify the current step is fully complete. Steps that involve API calls (schema fetch, existing-wallet check, batch mutation) are mandatory — never skip them to save time or because results seem obvious. If you catch yourself about to skip a step, stop and execute it first.\n\n---\n\n## Step 0 — Ask Wallet Type\n\nBefore doing anything else, ask the user what kind of wallet they want to add using `ask_user_input_v0`:\n\n```\nquestion: \"What would you like to add to Tres?\"\noptions:\n  - \"On-Chain Wallets (Ethereum, Solana, Bitcoin, etc.)\"\n  - \"Exchange Accounts (Binance, Coinbase, Kraken, etc.)\"\ntype: single_select\n```\n\n- If the user selects **On-Chain Wallets** → proceed to **[ON-CHAIN FLOW]** (Step OC-1)\n- If the user selects **Exchange Accounts** → proceed to **[EXCHANGE FLOW]** (Step EX-1)\n\n---\n\n---\n\n# ON-CHAIN FLOW\n\n---\n\n## Step OC-1 — Ask for Input Method\n\nAsk the user how they want to provide their on-chain wallets using `ask_user_input_v0`:\n\n```\nquestion: \"How would you like to add your wallets?\"\noptions:\n  - \"Upload a file (CSV or Excel)\"\n  - \"Enter manually in a table\"\ntype: single_select\n```\n\nWait for the user's response, then proceed to the matching option in Step OC-2.\n\n---\n\n## Step OC-2 — Collect Wallet Data\n\n### Option A: File Upload\nIf the user selects \"Upload a file\" (or uploads a CSV or Excel file directly):\n- Read the file with pandas \u002F openpyxl from `\u002Fmnt\u002Fuser-data\u002Fuploads\u002F`\n- Expected columns (flexible): `name`, `address` (or `identifier`), `network` (or `platform`), `tags` (optional), `description` (optional)\n- Normalise header names (case-insensitive, strip spaces, accept aliases)\n- Parse into a list of wallet dicts, then proceed to Step OC-3\n\n### Option B: Simple Manual Entry (conversational)\nIf the user selects \"Enter manually in a table\":\n- **Do NOT render an HTML widget.** Instead, ask the user to provide their wallets in plain text, one per line, in this format:\n  ```\n  Name | Address | Network | Tags (optional)\n  ```\n  Example:\n  ```\n  Treasury Hot | 0xABCD...1234 | ETHEREUM | defi,treasury\n  Cold Storage | bc1q...xyz | BITCOIN |\n  ```\n- Once the user pastes their wallets, parse the lines into a list of wallet dicts, then proceed to Step OC-4.\n- If the user is unsure of the network name, tell them to type it as best they can and you will fuzzy-match it to the correct `ParentPlatform` value.\n\n---\n\n## Step OC-3 — Fetch Live Platform List from Schema\n\n**Always** fetch the ParentPlatform enum values live from the TRES MCP schema — never hardcode them. Use:\n\n```graphql\n# Via TRES MCP introspect tool:\nintrospect(\"ParentPlatform\")\n```\n\nThis returns the full list of valid enum values to use in the network dropdown and for validation.\n\n### Identifying exchanges vs on-chain wallets\n\nTo filter the ParentPlatform list to on-chain platforms only, exclude any value that matches a known exchange\u002Fcustodian. The authoritative live list of supported exchanges is fetched in the Exchange Flow (Step EX-1). As a local heuristic for the on-chain filter, exclude these:\n\n```\nANCHORAGE, AQUANOW, ASCENDEX, B2C2, BACKPACK, BINANCE_EXCHANGE, BINANCE_EXCHANGE_TR,\nBITCOIN_SUISSE, BITFINEX, BITGET, BITGO, BITMEX, BITSO, BITSTAMP, BITVAVO, BREX,\nBTC_MARKETS, BTCTURK, BULLISH, BYBIT, CEFFU, CIRCLE, COBO, COINBASE, COINBASE_COMMERCE,\nCOINBASE_EXCHANGE, COINBASE_INTERNATIONAL, COINBASE_PRIME, COINEX, COPPER, CRYPTOCOM,\nCRYPTOCOM_EXCHANGE, CUSTOMERS_BANK, DERIBIT, EQUALSMONEY, FALCONX, FIDELITY,\nFIFTH_THIRD_BANK, FIREBLOCKS, FORDEFI_UTXO, FTX, FTXUS, GATEIO, GEMINI, HITBTC, HTX,\nKRAKEN, KRAKEN_CUSTODY, KRAKEN_FUTURES, KUCOIN, LAYERONE, LEDGER_ENTERPRISE, LMAX,\nLUKKA, M2, MERCADO, MERCURY, MERCURY_TREASURY, MEOW, MEOW_TREASURY, MESH_PAYMENTS,\nMORGAN_STANLEY, NONCO, OKX, PAXFUL, PARADEX, QONTO, QREDO, REVOLUT_FR, REVOLUT_UK,\nSVB_GO, SVB_ONLINE, SYGNUM, TALOS, VERTEX, WHITEBIT, WINTERMUTE, WISE_US,\nBANK_HAPOALIM_BIZ, BANK_HAPOALIM_INTERNATIONAL, BANK_OF_AMERICA,\nBANQUE_POPULAIRE_RIVES_DE_PARIS, CHASE, CHECKOUT\n```\n\nAny platform NOT in this list is treated as an on-chain wallet requiring a standard blockchain address.\n\n---\n\n## Step OC-4 — Validate Wallets\n\nRun ALL checks below. Collect errors per-row; do NOT abort early.\n\n### Required field checks\n| Field | Rule |\n|-------|------|\n| `name` | Non-empty string |\n| `identifier` | Non-empty string |\n| `parentPlatform` | Must be a valid `ParentPlatform` enum value (from live schema) |\n\n### Network name normalisation\nIf a network name from a CSV is lowercase or mixed-case (e.g. `tezos`, `Ethereum`), uppercase it and fuzzy-match to the nearest valid `ParentPlatform` enum value. Show a warning banner in the preview noting the normalisation and asking the user to confirm.\n\n### Address format validation per network (on-chain only)\nApply these regex rules for on-chain wallets. Skip for exchanges.\n\n| Network(s) | Rule |\n|---|---|\n| ETHEREUM, BNB, POLYGON, AVALANCHE_*, ARBITRUM, OPTIMISM, BASE, FANTOM, MOONBEAM, and other EVM chains | `^0x[0-9a-fA-F]{40}$` |\n| BITCOIN | P2PKH `1...`, P2SH `3...`, or Bech32 `bc1...` — 25–62 chars |\n| SOLANA | Base58, 32–44 chars: `^[1-9A-HJ-NP-Za-km-z]{32,44}$` |\n| TRON | `^T[1-9A-HJ-NP-Za-km-z]{33}$` |\n| TEZOS | `^tz[123][1-9A-HJ-NP-Za-km-z]{33}$` |\n| SUI, APTOS | `^0x[0-9a-fA-F]{62,64}$` |\n| STELLAR | Starts with `G`, 56 chars |\n| RIPPLE | Starts with `r`, 25–34 chars |\n| CARDANO | Starts with `addr1`, length > 50 |\n| NEAR | Ends in `.near` OR 64-char hex |\n| TON | Starts with `EQ` or `UQ`, 48 chars |\n| ALGORAND | 58-char Base32 uppercase |\n\n### Network–address mismatch detection\nFlag obvious mismatches (e.g. `0x...` address on SOLANA network, or Bitcoin address on ETHEREUM).\n\n### Duplicate detection\n\n**Within-batch duplicates:**\nFlag rows sharing the same `(identifier, parentPlatform)` pair. Mark both as errors.\n\n**Existing-wallet check against Tres (batches ≤ 200 wallets):**\n```graphql\n{\n  internalAccount(identifier_In: [\"addr1\", \"addr2\", ...]) {\n    results { id name identifier parentPlatform }\n  }\n}\n```\nBuild a lookup: `key = identifier.toLowerCase() + \"|\" + parentPlatform.toUpperCase()`\n- Match → mark as **⚠️ warning** (yellow): `\"Exists (ID: XXXXX)\"` — API will update, not duplicate\n- Summary bar must show: `X new | Y already exist | Z errors`\n\nFor batches > 200: skip the API check, show a note in the preview.\n\n---\n\n## Step OC-5 — Show Text Preview\n\n> 🚫 **HARD GATE:** Do NOT render this preview until Step OC-4 (validation) AND the existing-wallet Tres API check are both fully complete. Showing the preview without the API check is a violation of this skill.\n\n**Do NOT render an HTML widget.** Instead, present the wallet data as a clean markdown table in plain text so the user can review it:\n\n```\n| # | Name | Address | Network | Tags | Status |\n|---|------|---------|---------|------|--------|\n| 1 | Treasury Hot | 0xABCD...1234 | ETHEREUM | defi | ✅ New |\n| 2 | Cold Wallet | bc1q...xyz | BITCOIN | | ⚠️ Exists (ID: 12345) |\n| 3 | Bad Wallet | invalid-addr | SOLANA | | ❌ Invalid address |\n```\n\n- Show a summary line: `X new | Y already exist | Z errors`\n- List all errors below the table with row number and description:\n  ```\n  Errors:\n  - Row 3 (Bad Wallet): Invalid SOLANA address format\n  ```\n- If there are errors, tell the user to correct and re-paste the data before proceeding\n- If there are only warnings (existing wallets), ask: \"Ready to upload? Existing wallets will be updated. Type **yes** to confirm.\"\n- If all rows are valid, ask: \"Ready to upload N wallets to Tres Finance. Type **yes** to confirm.\"\n\nWhen the user confirms → proceed to Step OC-6.\n\n---\n\n## Step OC-6 — Final Confirmation\n\nWhen Claude receives `TRES_WALLET_UPLOAD_CONFIRMED:`:\n1. Parse the JSON payload\n2. Present a plain-text summary:\n   ```\n   About to upload N wallets to Tres Finance:\n   - 3 ETHEREUM wallets\n   - 2 SOLANA wallets\n   - 1 TEZOS wallet (will update existing)\n\n   Shall I proceed?\n   ```\n3. Wait for explicit user confirmation (\"yes\", \"confirm\", \"go ahead\")\n\n---\n\n## Step OC-7 — Execute Batch Upload\n\nCall `updateBatchInternalAccounts` via TRES MCP:\n\n```graphql\nmutation UpdateBatchInternalAccounts($internalAccounts: [InternalAccountInput]) {\n  updateBatchInternalAccounts(internalAccounts: $internalAccounts) {\n    internalAccounts {\n      id\n      name\n      identifier\n      parentPlatform\n      status\n    }\n    validationResults {\n      iaIdentifier\n      validationResult {\n        issueType\n        errorMessage\n      }\n    }\n  }\n}\n```\n\nVariables per wallet:\n```json\n{\n  \"name\": \"Treasury Hot\",\n  \"identifier\": \"0xABCD...\",\n  \"parentPlatform\": \"ETHEREUM\",\n  \"tags\": [\"defi\", \"treasury\"],\n  \"enforceCollectTransactions\": true\n}\n```\n\nNote: `platformKeys` is not included for on-chain wallets.\n\n### Chunking\nIf batch > 100 wallets, split into chunks of 50 and call sequentially.\n\n### Result handling\n- Parse `validationResults` — surface any `issueType` \u002F `errorMessage` to the user\n- Show success count and any failures\n- For failures, offer to retry just the failed wallets\n\n---\n\n---\n\n# EXCHANGE FLOW\n\n---\n\n## Step EX-1 — Introduction & Guide\n\nShow the user the integration guide link:\n\n> Before connecting an exchange, please review the **Tres Finance Exchange Integration Guide**:\n> 👉 https:\u002F\u002Fhelp.tres.finance\u002Farticle\u002Fintegrating-your-exchange-accounts-with-tres-finance\n\nThen fetch the **live validated exchange list** from TRES MCP — never hardcode it:\n\n```graphql\nquery GetAllValidatedExchanges {\n  ledgerFilters {\n    allValidatedExchanges {\n      id\n      displayName\n    }\n  }\n}\n```\n\nThis returns the authoritative list of supported exchanges (47 as of writing, but always fetch live). Sort A-Z by `displayName`. Present as a native `\u003Cselect>` dropdown using `ask_user_input_v0` or inline in a `show_widget` form, mirroring the Tres UI with a \"Connection Guidelines ↗\" link alongside the label.\n\n---\n\n## Step EX-2 — Fetch Required Fields for the Selected Exchange\n\nOnce the user selects an exchange, fetch its credential fields. **Use the `id` value (lowercase) as the `exchangeName`:**\n\n```graphql\nquery ExchangeRequiredFields {\n  exchangeRequiredFields {\n    requiredFields(exchangeName: \"\u003Cexchange_id_lowercase>\") {\n      name\n      type\n      description\n      mapping\n    }\n  }\n}\n```\n\n**Important:** Skip any field where `mapping` starts with `https:\u002F\u002F` — these are integration guide links, not credential inputs. Show them as a clickable link instead.\n\nStore the remaining fields. Each field has:\n- `name` — the credential field key\n- `description` — the human-readable label to show the user\n- `mapping` — the key used when constructing `platformKeys` (e.g. `platform_keys.api_key`)\n- `type` — use to determine input type\n\n---\n\n## Step EX-3 — Collect Exchange Credentials (Conversational)\n\n**Do NOT render an HTML widget.** Instead, ask the user for credentials in plain conversational steps.\n\nFirst, show the integration guide link:\n> 📖 Before connecting, review the guide: https:\u002F\u002Fhelp.tres.finance\u002Farticle\u002Fintegrating-your-exchange-accounts-with-tres-finance\n\nThen ask for the fields one by one (or all at once in a single prompt), clearly listing what is needed:\n\n```\nTo connect \u003CExchange Name>, I need the following:\n\n**Account Name** (required) — a friendly name for this account in Tres\n**API Key** (required)\n**API Secret** (required, will be stored securely)\n**Tags** (optional) — comma-separated tags\n\nPlease provide these values. Keep API secrets private — do not share them in public channels.\n```\n\n- For fields where `field.name` contains \"secret\", \"private\", \"signing\", or \"passphrase\" — note they will be stored securely\n- For optional fields (e.g. OKX sub-account), label them clearly as `(optional)`\n- Skip any field where `mapping` starts with `https:\u002F\u002F` — show it as a link instead\n\n### Mandatory confirmations (ask as yes\u002Fno questions before proceeding)\nBefore accepting the credentials, ask:\n1. \"Do you confirm the API key has **read-only permissions**? (yes\u002Fno)\"\n2. \"Do you agree to the **Tres Finance Terms of Service**? (yes\u002Fno)\"\n\nOnly proceed once both are confirmed.\n\nOnce all credentials and confirmations are collected, store them in the queue format and proceed to Step EX-4.\n\n---\n\n## Step EX-4 — Accumulate Exchange Accounts\n\nAfter collecting credentials for an exchange:\n1. Parse and store the account data in a pending queue\n2. Confirm: `✅ \u003CaccountName> (\u003Cexchange>) added to queue`\n3. Display the running queue as a brief list:\n   ```\n   Queued accounts:\n   1. My Binance Account (BINANCE_EXCHANGE)\n   ```\n4. Ask: \"Would you like to **add another exchange** or **proceed to upload**?\"\n\nIf user wants to add another → loop back to **Step EX-1** (queued accounts are preserved).\nIf user wants to proceed → go to **Step EX-5**.\n\n---\n\n## Step EX-5 — Final Review & Confirmation\n\nPresent a plain-text summary of all queued accounts:\n\n```\nReady to connect the following exchange accounts to Tres Finance:\n\n1. My Binance Account (BINANCE_EXCHANGE)\n2. Kraken Main (KRAKEN)\n\nShall I proceed?\n```\n\nWait for explicit user confirmation (\"yes\", \"confirm\", \"go ahead\", etc.)\n\n---\n\n## Step EX-6 — Execute Exchange Account Creation\n\nCall `updateBatchInternalAccounts` via TRES MCP for all queued accounts:\n\n```graphql\nmutation UpdateBatchInternalAccounts($internalAccounts: [InternalAccountInput]) {\n  updateBatchInternalAccounts(internalAccounts: $internalAccounts) {\n    internalAccounts {\n      id\n      name\n      identifier\n      parentPlatform\n      status\n    }\n    validationResults {\n      iaIdentifier\n      validationResult {\n        issueType\n        errorMessage\n      }\n    }\n  }\n}\n```\n\nVariables per exchange account:\n```json\n{\n  \"name\": \"\u003CaccountName>\",\n  \"identifier\": \"\u003CaccountName>\",\n  \"parentPlatform\": \"\u003CEXCHANGE_ID_UPPERCASE>\",\n  \"tags\": [\"\u003Ctag1>\"],\n  \"enforceCollectTransactions\": true,\n  \"platformKeys\": \"{\\\"api_key\\\": \\\"...\\\", \\\"api_secret\\\": \\\"...\\\"}\"\n}\n```\n\n**Important:**\n- `identifier` = account name (no blockchain address for exchanges)\n- `platformKeys` = a **JSON string** (not an object), built from `field.mapping` → value pairs collected in the form\n- `parentPlatform` = exchange `id` uppercased (e.g. `binance_exchange` → `BINANCE_EXCHANGE`)\n- Process all accounts in a single batch call where possible\n\n### Result handling\n- Show success\u002Ffailure per account\n- Surface `issueType` and `errorMessage` for failures\n- Offer to retry failed accounts\n\n---\n\n## Error Messages & Recovery\n\n| Situation | What to do |\n|-----------|-----------|\n| CSV has no `address` column | Ask user to map which column contains the wallet address |\n| Unknown network name | Fuzzy-match to nearest `ParentPlatform` enum value, show warning banner, ask user to confirm |\n| Address format invalid | Mark as error in preview; user must fix or remove the row before upload |\n| Duplicate in batch | Mark both rows as errors; user must remove or fix one |\n| Wallet already exists in Tres | Mark as ⚠️ warning (yellow); proceed — API will update it |\n| No file and no wallets typed | Prompt user to either upload a file or use the manual table |\n| Batch > 200 wallets | Skip existing-wallet API check; show informational note |\n| MCP mutation returns error | Show error per wallet; offer retry |\n| Exchange credentials rejected | Show the validation error and prompt user to re-enter credentials |\n| `exchangeRequiredFields` returns empty | Inform user that this exchange may need manual setup; link to the guide |\n| `allValidatedExchanges` returns empty | Fall back to informing user and linking to https:\u002F\u002Fhelp.tres.finance |\n",{"name":5,"description":57,"compatibility":58},"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\".\n","Requires TRES Finance MCP connected (https:\u002F\u002Fai.tres.finance\u002Fmcp)","main","163301d1904c0a994539f5226ce0fcd65b8652bf","tres-finance-plugin\u002Fskills\u002Ftres-wallets-upload",360,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-12 15:56:31",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add anthropics\u002Fclaude-plugins-community --skill tres-wallets-upload",{"tool":73,"command":74},"bunx","bunx skills add anthropics\u002Fclaude-plugins-community --skill tres-wallets-upload",{"tool":76,"command":77},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-plugins-community --skill tres-wallets-upload","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-wallets-upload\u002FSKILL.md",true,[],[82,107,132,156,180,200],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":52},"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",[],[89,33,90,91,92,93,49,94,95,96,97,98,99,100,101,102,103,104,105,106],"tres upload tx header validation","validation","bulk","do","import","parsing","for","manual","trigger","fix","missing","general","only","use","workflow","csv","contacts","with",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":114,"publishedAt":52},"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",[113],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[115,116,117,118,119,44,120,121,122,123,124,125,126,127,128,129,130,92,131,95],"tres tx story","Story","show","memory","hex","when","show me","analysis","analyze","me","diagram","generate","flow","asset","blockchain","STRING","visualize",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"publishedAt":52},"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",[138],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[140,141,142,143,117,144,44,120,145,146,147,39,148,149,150,151,152,153,154,155],"tres settings management","settings","management","SET","get","configure","ask","commit","change","organization","update","read","write","sync","mcp graphql","flags",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":164,"publishedAt":52},"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",[162,163],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[165,166,167,117,168,49,169,44,170,171,172,173,174,123,175,176,177,178,149,179],"tres rollup rules","Rules","rollup","gas","up","impact","reduce","Connector","review","consolidate","create","transactions","delete","data-driven","activity",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":188,"publishedAt":52},"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",[186,187],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[173,189,167,190,191,192,193,194,101,195,44,170,120,40,196,172,197,198,175,199],"tres rollup review","standalone","never","mode","issues","design","new","candidate","filter","valid","catch",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":207,"publishedAt":52},"01M718F9C31MH0XFSZ29Z4X7WD","tres-request-skill-update","Submit feedback about the TRES Claude plugin — bug reports, feature requests, skill improvements, new skill ideas, MCP issues, workflow friction, or positive feedback about what's working well. Use this skill whenever the user wants to share any kind of feedback about the plugin, its skills, or the TRES MCP. Trigger phrases include: \"submit feedback\", \"report a bug\", \"request a feature\", \"suggest an improvement\", \"I have an idea\", \"something is broken\", \"the skill isn't working\", \"I love this skill\", \"this worked great\", \"the MCP is returning wrong data\", \"the flow is confusing\", \"can you fix the skill\", \"file a skill request\", \"give feedback\", \"this could be better\". Also trigger proactively when the conversation appears to be wrapping up — e.g. the user says \"thanks\", \"that's all\", \"looks good\", \"we're done\", \"nothing else\", or any other signal that the task is complete. In that case, offer a brief feedback prompt instead of launching the full guided flow. Do NOT trigger for general questions about how a skill works — only when the user wants to submit feedback or the conversation is ending.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-request-skill-update\u002FSKILL.md",[206],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[208,35,150,209,210,211,212,213,214,169,98,193,215,101,195,216,44,120,103,217],"skill update","tres request skill update","conversation","brief","broken","submit","re","good","give feedback","you"]