[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718DT0Q028XX4FAMSJMDXSH":3,"skill-same:01M718DT0Q028XX4FAMSJMDXSH":85},{"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":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M718DT0Q028XX4FAMSJMDXSH","tres-export-3rd-party-contacts",null,"Extract all 3rd-party (non-owned) addresses from a TRES Finance environment and export them as an XLSX workbook to help users build their contacts list. Use this skill whenever the user wants to export, list, or identify 3rd-party addresses, counterparties, or external addresses from their transactions — even if they don't say 'contacts'. Also trigger when the user asks to prepare a contacts import file, find unknown addresses, or build an address book from transaction history. Do NOT trigger for viewing existing contacts or searching the address book — only for extracting NEW 3rd-party addresses from transaction data.","anthropics\u002Fclaude-plugins-community","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M718C1RS4JJFM9KNJMTCAYJG",4869,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-export-3rd-party-contacts\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],"contacts","export","party","tres export 3rd party contacts","for","history","import","do","as","addresses","list","data","contacts import","transactions","unknown","when","new","only","xlsx","extracting","2026-11-10 10:12:30",false,"---\nname: tres-export-3rd-party-contacts\ndescription: \"Extract all 3rd-party (non-owned) addresses from a TRES Finance environment and export them as an XLSX workbook to help users build their contacts list. Use this skill whenever the user wants to export, list, or identify 3rd-party addresses, counterparties, or external addresses from their transactions — even if they don't say 'contacts'. Also trigger when the user asks to prepare a contacts import file, find unknown addresses, or build an address book from transaction history. Do NOT trigger for viewing existing contacts or searching the address book — only for extracting NEW 3rd-party addresses from transaction data.\"\n---\n\n# TRES Finance — Export 3rd-Party Addresses as Contacts Workbook\n\n## Goal\n\nFetch all **unidentified** external addresses from the user's TRES environment using the `accountTxsSummary` query (the same data source that powers the \"Unidentified Addresses\" tab in the TRES UI), deduplicate them, enrich them with activity data, and produce an XLSX workbook with two tabs:\n\n1. **Contacts** — the import-ready sheet matching the TRES contacts template. The user fills in names and tags here, then imports this sheet back into TRES.\n2. **Address details** — enrichment data (network, tx counts, fiat volumes) to help users identify who each address belongs to.\n\nThe workflow gives users a fast way to build their address book: Claude extracts, deduplicates, and enriches the unidentified addresses, and the user just needs to label them.\n\n## MCP Server\n\nAll GraphQL calls use the **user-tres-finance** MCP server (`execute` tool).\n\n## Workflow\n\n### Step 1 — Authenticate\n\nCall `get_viewer` (no arguments) to confirm the session is active and note the organization name.\n\n### Step 2 — Fetch unidentified addresses\n\nUse the `accountTxsSummary` query with `identificationState: \"UNIDENTIFIED\"` — this is the same query the TRES UI uses for the \"Unidentified Addresses\" tab under Accounts. It already excludes the organization's own wallets and returns only external counterparty addresses that haven't been named yet.\n\n```graphql\nquery UnidentifiedAddresses($limit: Int, $offset: Int, $identificationState: String, $excludeInternalAccounts: Boolean, $fiatCurrency: String) {\n  accountTxsSummary(\n    limit: $limit\n    offset: $offset\n    identificationState: $identificationState\n    excludeInternalAccounts: $excludeInternalAccounts\n    fiatCurrency: $fiatCurrency\n  ) {\n    totalCount\n    results {\n      accountIdentifier\n      displayName\n      inflowTxCount\n      outflowTxCount\n      inflowFiatValue\n      outflowFiatValue\n    }\n  }\n}\n```\n\nVariables:\n```json\n{\n  \"limit\": 500,\n  \"offset\": 0,\n  \"identificationState\": \"UNIDENTIFIED\",\n  \"excludeInternalAccounts\": true,\n  \"fiatCurrency\": \"usd\"\n}\n```\n\nPaginate through all results (increment `offset` by 500 each time until you've collected all entries from `totalCount`).\n\n### Step 3 — Deduplicate and detect network\n\nThe `accountTxsSummary` query can return the same address more than once (e.g. different casing variants of the same EVM address, or separate rows for sender vs. receiver context). Deduplicate by **lowercased** `accountIdentifier`:\n\n- Build a dictionary keyed by `accountIdentifier.lower()`\n- For each address, keep the first occurrence's original casing and accumulate the total inflow + outflow tx count and fiat values\n- Skip addresses with an empty or null `accountIdentifier`\n\nSort the deduplicated addresses by total fiat volume (inflow + outflow) descending, so the most active counterparties appear first — these are typically the ones the user will want to label first.\n\n**Network detection:** The API does not return a network field, so infer the network from the address format. Use these rules:\n\n| Address pattern | Network |\n|---|---|\n| Starts with `0x` (42 chars, hex) | EVM |\n| Starts with `KT1` | Tezos (contract) |\n| Starts with `tz1`, `tz2`, `tz3` | Tezos |\n| Starts with `T` (34 chars, base58) | Tron |\n| Starts with `bc1` or `1` or `3` (25–62 chars) | Bitcoin |\n| Starts with `r` (25–35 chars) | XRP Ledger |\n| Starts with `cosmos1` | Cosmos |\n| Starts with `osmo1` | Osmosis |\n| Starts with `terra1` | Terra |\n| Starts with `addr1` or `stake1` | Cardano |\n| Starts with `bnb1` | BNB Beacon Chain |\n| Starts with `G` (56 chars) | Stellar |\n| Starts with `D` or `A` or `L` or `M` or `ltc1` (26–35 chars) | Litecoin\u002FDogecoin (best guess) |\n| None of the above | Unknown |\n\nThis is a best-effort heuristic — EVM addresses in particular could belong to Ethereum, Polygon, Arbitrum, Base, Avalanche, BSC, or any other EVM-compatible chain. The label \"EVM\" is intentionally broad because the address alone can't distinguish which chain it's on.\n\n### Step 4 — Build the XLSX workbook\n\nUse Python with `openpyxl==3.1.5`. If not installed, stop and display:\n> \"openpyxl is not installed. Please run: `python3 -m venv .venv && .venv\u002Fbin\u002Fpip install openpyxl==3.1.5`\"\n\n#### Tab 1: \"Contacts\" (import-ready)\n\nThis sheet matches the TRES contacts import template exactly:\n\n| Contact Name | Contact Address | Contact Tag |\n|---|---|---|\n| *(blank)* | 0xABC... | *(blank)* |\n\n- **Contact Name**: leave blank (the user will fill this in)\n- **Contact Address**: the address identifier (original casing)\n- **Contact Tag**: leave blank (the user will fill this in)\n- Sorted by total fiat volume descending (same order as Address details)\n\n#### Tab 2: \"Address details\" (enrichment)\n\n| Contact Address | Network | Inflow Txs | Outflow Txs | Inflow USD | Outflow USD | Total USD |\n|---|---|---|---|---|---|---|\n| 0xABC... | EVM | 142 | 38 | 1,240,500 | 890,200 | 2,130,700 |\n| KT1Xyz... | Tezos (contract) | 6 | 0 | 40,144,631 | 0 | 40,144,631 |\n| TBmxn... | Tron | 23 | 5 | 340,100 | 52,000 | 392,100 |\n\n- Same address order as the Contacts tab (sorted by Total USD descending)\n- `Network`: inferred from address format (see Step 3)\n- `Inflow Txs` \u002F `Outflow Txs`: from `accountTxsSummary` results\n- `Inflow USD` \u002F `Outflow USD`: from `accountTxsSummary` fiat values\n- `Total USD`: sum of inflow + outflow fiat values\n\n#### Formatting guidelines\n\n- Bold the header row on all tabs\n- Auto-fit column widths for readability\n- Format USD columns as numbers (no $ prefix in cells — use Excel number formatting)\n- The \"Contacts\" tab should be the first\u002Factive sheet when the file opens, since that's the one the user will work in\n\n### Step 5 — Save and present\n\nSave the XLSX to the outputs directory. Use a descriptive filename like `tres_3rd_party_contacts_\u003Corg_name>_\u003Cdate>.xlsx` (replace spaces and special chars with underscores).\n\nPresent the file to the user with a brief summary:\n- How many unique unidentified addresses were found\n- Total number of transactions involving these addresses\n- A link to the XLSX file\n\nThen explain what each tab is for:\n\n> **Your workbook has 2 tabs:**\n>\n> 1. **Contacts** — This is the import-ready sheet. Fill in the **Contact Name** for each address you recognize, and optionally add a **Contact Tag** (e.g. `Exchange`, `Vendor`, `Treasury`). When you're done, use the **contacts import skill** to upload this sheet back into TRES.\n>\n> 2. **Address details** — Reference tab showing the detected network, activity stats for each address (inflow\u002Foutflow transaction counts and USD volumes). Use this to prioritize which addresses to label — the highest-volume counterparties are at the top. The network column helps narrow down which chain the address belongs to.\n\n## Edge Cases\n\n- **No unidentified addresses found**: If the result set is empty, tell the user — it likely means all counterparty addresses are already in the contacts list.\n- **Mixed-case addresses**: EVM addresses can appear in different checksummed forms. Always compare in lowercase for deduplication, but preserve the original case in the output.\n- **Zero\u002Fburn addresses**: Include `0x0000000000000000000000000000000000000000` in the output if it appears — the user may still want to label it as \"Burn Address\" or similar.\n- **Unknown network**: If an address doesn't match any known pattern, set Network to \"Unknown\". Don't skip the address — it's still a valid counterparty.\n","# TRES Finance — Export 3rd-Party Addresses as Contacts Workbook\n\n## Goal\n\nFetch all **unidentified** external addresses from the user's TRES environment using the `accountTxsSummary` query (the same data source that powers the \"Unidentified Addresses\" tab in the TRES UI), deduplicate them, enrich them with activity data, and produce an XLSX workbook with two tabs:\n\n1. **Contacts** — the import-ready sheet matching the TRES contacts template. The user fills in names and tags here, then imports this sheet back into TRES.\n2. **Address details** — enrichment data (network, tx counts, fiat volumes) to help users identify who each address belongs to.\n\nThe workflow gives users a fast way to build their address book: Claude extracts, deduplicates, and enriches the unidentified addresses, and the user just needs to label them.\n\n## MCP Server\n\nAll GraphQL calls use the **user-tres-finance** MCP server (`execute` tool).\n\n## Workflow\n\n### Step 1 — Authenticate\n\nCall `get_viewer` (no arguments) to confirm the session is active and note the organization name.\n\n### Step 2 — Fetch unidentified addresses\n\nUse the `accountTxsSummary` query with `identificationState: \"UNIDENTIFIED\"` — this is the same query the TRES UI uses for the \"Unidentified Addresses\" tab under Accounts. It already excludes the organization's own wallets and returns only external counterparty addresses that haven't been named yet.\n\n```graphql\nquery UnidentifiedAddresses($limit: Int, $offset: Int, $identificationState: String, $excludeInternalAccounts: Boolean, $fiatCurrency: String) {\n  accountTxsSummary(\n    limit: $limit\n    offset: $offset\n    identificationState: $identificationState\n    excludeInternalAccounts: $excludeInternalAccounts\n    fiatCurrency: $fiatCurrency\n  ) {\n    totalCount\n    results {\n      accountIdentifier\n      displayName\n      inflowTxCount\n      outflowTxCount\n      inflowFiatValue\n      outflowFiatValue\n    }\n  }\n}\n```\n\nVariables:\n```json\n{\n  \"limit\": 500,\n  \"offset\": 0,\n  \"identificationState\": \"UNIDENTIFIED\",\n  \"excludeInternalAccounts\": true,\n  \"fiatCurrency\": \"usd\"\n}\n```\n\nPaginate through all results (increment `offset` by 500 each time until you've collected all entries from `totalCount`).\n\n### Step 3 — Deduplicate and detect network\n\nThe `accountTxsSummary` query can return the same address more than once (e.g. different casing variants of the same EVM address, or separate rows for sender vs. receiver context). Deduplicate by **lowercased** `accountIdentifier`:\n\n- Build a dictionary keyed by `accountIdentifier.lower()`\n- For each address, keep the first occurrence's original casing and accumulate the total inflow + outflow tx count and fiat values\n- Skip addresses with an empty or null `accountIdentifier`\n\nSort the deduplicated addresses by total fiat volume (inflow + outflow) descending, so the most active counterparties appear first — these are typically the ones the user will want to label first.\n\n**Network detection:** The API does not return a network field, so infer the network from the address format. Use these rules:\n\n| Address pattern | Network |\n|---|---|\n| Starts with `0x` (42 chars, hex) | EVM |\n| Starts with `KT1` | Tezos (contract) |\n| Starts with `tz1`, `tz2`, `tz3` | Tezos |\n| Starts with `T` (34 chars, base58) | Tron |\n| Starts with `bc1` or `1` or `3` (25–62 chars) | Bitcoin |\n| Starts with `r` (25–35 chars) | XRP Ledger |\n| Starts with `cosmos1` | Cosmos |\n| Starts with `osmo1` | Osmosis |\n| Starts with `terra1` | Terra |\n| Starts with `addr1` or `stake1` | Cardano |\n| Starts with `bnb1` | BNB Beacon Chain |\n| Starts with `G` (56 chars) | Stellar |\n| Starts with `D` or `A` or `L` or `M` or `ltc1` (26–35 chars) | Litecoin\u002FDogecoin (best guess) |\n| None of the above | Unknown |\n\nThis is a best-effort heuristic — EVM addresses in particular could belong to Ethereum, Polygon, Arbitrum, Base, Avalanche, BSC, or any other EVM-compatible chain. The label \"EVM\" is intentionally broad because the address alone can't distinguish which chain it's on.\n\n### Step 4 — Build the XLSX workbook\n\nUse Python with `openpyxl==3.1.5`. If not installed, stop and display:\n> \"openpyxl is not installed. Please run: `python3 -m venv .venv && .venv\u002Fbin\u002Fpip install openpyxl==3.1.5`\"\n\n#### Tab 1: \"Contacts\" (import-ready)\n\nThis sheet matches the TRES contacts import template exactly:\n\n| Contact Name | Contact Address | Contact Tag |\n|---|---|---|\n| *(blank)* | 0xABC... | *(blank)* |\n\n- **Contact Name**: leave blank (the user will fill this in)\n- **Contact Address**: the address identifier (original casing)\n- **Contact Tag**: leave blank (the user will fill this in)\n- Sorted by total fiat volume descending (same order as Address details)\n\n#### Tab 2: \"Address details\" (enrichment)\n\n| Contact Address | Network | Inflow Txs | Outflow Txs | Inflow USD | Outflow USD | Total USD |\n|---|---|---|---|---|---|---|\n| 0xABC... | EVM | 142 | 38 | 1,240,500 | 890,200 | 2,130,700 |\n| KT1Xyz... | Tezos (contract) | 6 | 0 | 40,144,631 | 0 | 40,144,631 |\n| TBmxn... | Tron | 23 | 5 | 340,100 | 52,000 | 392,100 |\n\n- Same address order as the Contacts tab (sorted by Total USD descending)\n- `Network`: inferred from address format (see Step 3)\n- `Inflow Txs` \u002F `Outflow Txs`: from `accountTxsSummary` results\n- `Inflow USD` \u002F `Outflow USD`: from `accountTxsSummary` fiat values\n- `Total USD`: sum of inflow + outflow fiat values\n\n#### Formatting guidelines\n\n- Bold the header row on all tabs\n- Auto-fit column widths for readability\n- Format USD columns as numbers (no $ prefix in cells — use Excel number formatting)\n- The \"Contacts\" tab should be the first\u002Factive sheet when the file opens, since that's the one the user will work in\n\n### Step 5 — Save and present\n\nSave the XLSX to the outputs directory. Use a descriptive filename like `tres_3rd_party_contacts_\u003Corg_name>_\u003Cdate>.xlsx` (replace spaces and special chars with underscores).\n\nPresent the file to the user with a brief summary:\n- How many unique unidentified addresses were found\n- Total number of transactions involving these addresses\n- A link to the XLSX file\n\nThen explain what each tab is for:\n\n> **Your workbook has 2 tabs:**\n>\n> 1. **Contacts** — This is the import-ready sheet. Fill in the **Contact Name** for each address you recognize, and optionally add a **Contact Tag** (e.g. `Exchange`, `Vendor`, `Treasury`). When you're done, use the **contacts import skill** to upload this sheet back into TRES.\n>\n> 2. **Address details** — Reference tab showing the detected network, activity stats for each address (inflow\u002Foutflow transaction counts and USD volumes). Use this to prioritize which addresses to label — the highest-volume counterparties are at the top. The network column helps narrow down which chain the address belongs to.\n\n## Edge Cases\n\n- **No unidentified addresses found**: If the result set is empty, tell the user — it likely means all counterparty addresses are already in the contacts list.\n- **Mixed-case addresses**: EVM addresses can appear in different checksummed forms. Always compare in lowercase for deduplication, but preserve the original case in the output.\n- **Zero\u002Fburn addresses**: Include `0x0000000000000000000000000000000000000000` in the output if it appears — the user may still want to label it as \"Burn Address\" or similar.\n- **Unknown network**: If an address doesn't match any known pattern, set Network to \"Unknown\". Don't skip the address — it's still a valid counterparty.\n",{"name":5,"description":7},"main","163301d1904c0a994539f5226ce0fcd65b8652bf","tres-finance-plugin\u002Fskills\u002Ftres-export-3rd-party-contacts",357,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-11 15:47:52",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add anthropics\u002Fclaude-plugins-community --skill tres-export-3rd-party-contacts",{"tool":71,"command":72},"bunx","bunx skills add anthropics\u002Fclaude-plugins-community --skill tres-export-3rd-party-contacts",{"tool":74,"command":75},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-plugins-community --skill tres-export-3rd-party-contacts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-export-3rd-party-contacts\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"evals\u002Fevals.json","REFERENCE","参考文档",1245,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-export-3rd-party-contacts\u002Fevals\u002Fevals.json",[86,115,135,159,183,206],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":95,"publishedAt":52},"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",[92,93,94],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[96,97,98,99,100,101,102,103,50,104,105,106,107,108,109,110,111,112,113,114],"wallets","tres wallets upload","upload","typing","ingestion","Wallet","chain","creation","selection","MCP","confirmation","connect","collection","preview","api","batch","guides","on-chain","request",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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",[],[122,98,123,124,39,38,101,125,36,126,127,128,129,130,49,131,132,133,32,134],"tres upload tx header validation","validation","bulk","parsing","manual","trigger","fix","missing","general","use","workflow","csv","with",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"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",[141],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[143,144,145,146,147,105,47,148,149,150,151,152,153,154,155,156,157,39,158,36],"tres tx story","Story","show","memory","hex","show me","analysis","analyze","me","diagram","generate","flow","asset","blockchain","STRING","visualize",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"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",[165],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[167,168,169,170,145,171,105,47,172,173,174,110,175,176,177,178,179,180,181,182],"tres settings management","settings","management","SET","get","configure","ask","commit","change","organization","update","read","write","sync","mcp graphql","flags",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":191,"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",[189,190],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[192,193,194,145,195,101,196,105,197,198,199,200,201,150,202,45,203,204,176,205],"tres rollup rules","Rules","rollup","gas","up","impact","reduce","Connector","review","consolidate","create","delete","data-driven","activity",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":214,"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",[212,213],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[200,215,194,216,217,218,219,220,49,48,105,197,47,109,221,199,222,223,202,224],"tres rollup review","standalone","never","mode","issues","design","candidate","filter","valid","catch"]