[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718EFKTP8VJR7AVNZKT57AA":3,"skill-same:01M718EFKTP8VJR7AVNZKT57AA":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},"01M718EFKTP8VJR7AVNZKT57AA","tres-onboarding",null,"End-to-end onboarding of a new entity, customer, or account into TRES Finance. Orchestrates 8 steps in order: wallet upload, data collection (commit), balance validation, reconciliation, cost basis, export unidentified addresses, import contacts, and rollup rules. Trigger ONLY when the user explicitly wants to onboard a new entity, customer, or account — e.g. \"onboard a new entity\", \"onboard new customer\", \"start onboarding for [name]\", \"set up a new account in TRES\", \"run the full onboarding flow\", \"I need to onboard [company name]\", \"new entity onboarding\". Do NOT trigger for individual tasks — those have their own dedicated skills. If the user asks to \"add wallets\" without mentioning onboarding, use tres-wallets-upload. \"Validate balances\" alone is tres-asset-balance-validation. \"Run a commit\" alone is tres-data-collection-commit. Only trigger when the user wants the full pipeline.","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-onboarding\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000040","财务",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"onboarding","tres onboarding","contacts","Connector","commit","tasks","collection","data-collection","when","MCP","new","only","up","company","end","pipeline","balances","Wallet","reconciliation","SET","2026-11-10 10:12:30",false,"---\nname: tres-onboarding\ndescription: >\n  End-to-end onboarding of a new entity, customer, or account into TRES Finance.\n  Orchestrates 8 steps in order: wallet upload, data collection (commit), balance\n  validation, reconciliation, cost basis, export unidentified addresses, import contacts,\n  and rollup rules. Trigger ONLY when the user explicitly wants to onboard a new entity,\n  customer, or account — e.g. \"onboard a new entity\", \"onboard new customer\", \"start\n  onboarding for [name]\", \"set up a new account in TRES\", \"run the full onboarding flow\",\n  \"I need to onboard [company name]\", \"new entity onboarding\". Do NOT trigger for\n  individual tasks — those have their own dedicated skills. If the user asks to \"add\n  wallets\" without mentioning onboarding, use tres-wallets-upload. \"Validate balances\" alone\n  is tres-asset-balance-validation. \"Run a commit\" alone is tres-data-collection-commit.\n  Only trigger when the user wants the full pipeline.\ncompatibility: \"Requires TRES Finance MCP connector and all sub-skills listed below\"\n---\n\n# TRES Finance — Full Entity Onboarding\n\nOrchestrate the complete onboarding of a new entity\u002Fcustomer\u002Faccount into TRES Finance.\nThis skill does not contain its own low-level logic — instead, it drives the user through\n8 sequential steps, invoking the dedicated skill for each one. Think of it as a conductor\nthat keeps the onboarding moving forward while each sub-skill handles the details.\n\n---\n\n## Before You Start\n\n**No visualizations for input gathering.** Do NOT use show_widget, HTML widgets, interactive\nforms, AskUserQuestion widgets, or any visualization tool when collecting initial context from\nthe user or presenting the onboarding roadmap. Ask all questions and present the roadmap as\nplain text in the chat. This keeps the flow fast and responsive — building a widget just to\nask for a name and wallet list adds unnecessary latency. Visualizations are fine later when\nindividual sub-skills need them (e.g., balance validation dashboards, recon gap tables), but\nthe onboarding kick-off and step transitions must be text-only.\n\n1. **Confirm intent.** The user must have explicitly requested a full onboarding (new entity,\n   new customer, new account). If the request is ambiguous, ask: \"Are you looking to run the\n   full onboarding flow for a new entity, or do you just need help with a specific step\n   (like uploading wallets or validating balances)?\"\n\n2. **Collect context.** Ask the user in plain text (no widgets, no forms) for:\n   - The entity\u002Fcustomer\u002Faccount name\n   - Any wallets or exchange accounts they already have ready (file, list, etc.)\n   - Whether they have a target date in mind for the onboarding\n\n3. **Present the roadmap.** Before diving in, show the user the roadmap as plain text\n   in the chat (not as an HTML widget or visualization) so they know what to expect.\n   Use something like:\n\n   > Here's the onboarding roadmap for **[Entity Name]**:\n   >\n   > 1. **Upload Wallets** — Add on-chain wallets and\u002For exchange accounts\n   > 2. **Data Collection (Commit)** — Pull on-chain data for the uploaded wallets\n   > 3. **Validate Balances** — Cross-check TRES balances against on-chain sources\n   > 4. **Reconciliation** — Review and resolve any balance gaps\n   > 5. **Cost Basis** — Configure and run cost basis calculation\n   > 6. **Export Unidentified Addresses** — Extract 3rd-party addresses from transactions\n   > 7. **Import Contacts** — Label and import the identified addresses back into TRES\n   > 8. **Rollup Rules** — Set up transaction aggregation for high-volume wallets\n   >\n   > We'll go through each step together. Ready to start?\n\n---\n\n## The Onboarding Pipeline\n\nWork through each step in order. After completing each step, briefly summarize what was\naccomplished and ask the user if they're ready to move on. If a step isn't relevant\n(e.g., no high-volume wallets that need rollup rules), the user can skip it.\n\n**Important:** For each step, invoke the corresponding skill by name. Read its SKILL.md\nand follow its instructions. The sub-skill handles all the details — your job is to\ntransition smoothly between steps and keep the user oriented.\n\n### Step 1: Upload Wallets\n**Skill:** `tres-wallets-upload`\n\nInvoke the tres-wallets-upload skill. This guides the user through adding their on-chain\nwallets and\u002For exchange accounts into TRES. Once wallets are created, confirm the count\nand proceed.\n\n**Transition:** \"Wallets are uploaded. Next, we'll collect on-chain data for them.\"\n\n---\n\n### Step 2: Data Collection (Commit)\n**Skill:** `tres-data-collection-commit`\n\nInvoke the tres-data-collection-commit skill. This triggers on-chain data collection for\nthe wallets that were just uploaded. The commit may take some time depending on the number\nof wallets and their history.\n\n**Transition:** \"Data collection is in progress \u002F complete. Next, let's validate that the\nbalances TRES pulled match what's actually on-chain.\"\n\n---\n\n### Step 3: Validate Balances\n**Skill:** `tres-asset-balance-validation`\n\nInvoke the tres-asset-balance-validation skill. This compares TRES balances against DeBank\n(for EVM wallets) and generates a discrepancy report. Review any issues with the user.\n\n**Transition:** \"Balance validation is done. Let's move on to reconciliation to close any\nremaining gaps.\"\n\n---\n\n### Step 4: Reconciliation\n**Skill:** `tres-recon-gaps`\n\nInvoke the tres-recon-gaps skill. This fetches reconciliation gap data, displays it, and\nhelps the user resolve any on-chain vs. book balance discrepancies. If there are no gaps,\ncelebrate and move on.\n\n**Transition:** \"Reconciliation is squared away. Now let's set up cost basis calculation.\"\n\n---\n\n### Step 5: Cost Basis\n**Skill:** `tres-cost-basis`\n\nInvoke the tres-cost-basis skill. This walks through strategy selection if needed, triggers\ncost basis calculation, surfaces per-asset results and financial issues, and covers\nreevaluations, spec-ID rules, and related cost basis operations as needed. Review any\nfinancial issues (negative balances, missing fiat prices) that surface.\n\n**Transition:** \"Cost basis is configured and running. Next, let's identify the external\naddresses your wallets have been interacting with.\"\n\n---\n\n### Step 6: Export Unidentified Addresses\n**Skill:** `tres-export-3rd-party-contacts`\n\nInvoke the tres-export-3rd-party-contacts skill. This extracts all unidentified external\naddresses from the entity's transactions and exports them as an XLSX workbook. The user\nwill need to review and label these addresses (who each address belongs to).\n\n**Transition:** \"The unidentified addresses have been exported. Once you've labeled them,\nwe'll import them back as contacts. If you need time to fill in the names, we can pause\nhere and come back to the next step later — just say 'continue onboarding' when ready.\"\n\n**Note:** This step produces output that the user needs to review and fill in offline.\nOffer to pause the onboarding here and resume later. If the user wants to continue\nimmediately (maybe they'll label contacts later), that's fine — skip to Step 8.\n\n---\n\n### Step 7: Import Contacts\n**Skill:** `tres-import-contacts`\n\nInvoke the tres-import-contacts skill. This reads the user's labeled contacts file and\nimports the address-to-name mappings into the TRES address book.\n\n**Transition:** \"Contacts are imported! Last step — let's set up rollup rules for any\nhigh-volume wallets.\"\n\n---\n\n### Step 8: Rollup Rules\n**Skill:** `tres-rollup-rules`\n\nInvoke the tres-rollup-rules skill. This helps the user identify wallets with high\ntransaction volume and create daily or monthly rollup rules to consolidate small\nsub-transactions (gas fees, staking rewards, etc.) into cleaner aggregated entries.\n\nIf no wallets need rollup rules, skip this step.\n\n---\n\n## Completion\n\nOnce all steps are done (or skipped where appropriate), wrap up with a summary:\n\n> **Onboarding complete for [Entity Name]!**\n>\n> Here's what we accomplished:\n> - Uploaded X wallets across Y networks\n> - Collected on-chain data\n> - Validated balances (note any outstanding issues)\n> - Reconciled gaps (note status)\n> - Configured cost basis strategy: [strategy]\n> - Exported and imported Z contacts\n> - Set up N rollup rules\n>\n> The entity is ready to go in TRES Finance.\n\n---\n\n## Handling Interruptions and Resumption\n\nThe user may need to pause and come back later (especially around Step 6-7 where they\nneed to label contacts offline). Keep track of which step was last completed. If the\nuser comes back and says something like \"continue onboarding\" or \"where were we with\nonboarding [entity]?\", pick up from the next incomplete step.\n\n## Skipping Steps\n\nThe user can skip any step if it's not relevant. For example:\n- No EVM wallets → skip balance validation (Step 3)\n- No gaps → reconciliation completes quickly (Step 4)\n- No need for contacts right now → skip Steps 6-7\n- No high-volume wallets → skip rollup rules (Step 8)\n\nAlways respect the user's choice and move to the next step.\n","# TRES Finance — Full Entity Onboarding\n\nOrchestrate the complete onboarding of a new entity\u002Fcustomer\u002Faccount into TRES Finance.\nThis skill does not contain its own low-level logic — instead, it drives the user through\n8 sequential steps, invoking the dedicated skill for each one. Think of it as a conductor\nthat keeps the onboarding moving forward while each sub-skill handles the details.\n\n---\n\n## Before You Start\n\n**No visualizations for input gathering.** Do NOT use show_widget, HTML widgets, interactive\nforms, AskUserQuestion widgets, or any visualization tool when collecting initial context from\nthe user or presenting the onboarding roadmap. Ask all questions and present the roadmap as\nplain text in the chat. This keeps the flow fast and responsive — building a widget just to\nask for a name and wallet list adds unnecessary latency. Visualizations are fine later when\nindividual sub-skills need them (e.g., balance validation dashboards, recon gap tables), but\nthe onboarding kick-off and step transitions must be text-only.\n\n1. **Confirm intent.** The user must have explicitly requested a full onboarding (new entity,\n   new customer, new account). If the request is ambiguous, ask: \"Are you looking to run the\n   full onboarding flow for a new entity, or do you just need help with a specific step\n   (like uploading wallets or validating balances)?\"\n\n2. **Collect context.** Ask the user in plain text (no widgets, no forms) for:\n   - The entity\u002Fcustomer\u002Faccount name\n   - Any wallets or exchange accounts they already have ready (file, list, etc.)\n   - Whether they have a target date in mind for the onboarding\n\n3. **Present the roadmap.** Before diving in, show the user the roadmap as plain text\n   in the chat (not as an HTML widget or visualization) so they know what to expect.\n   Use something like:\n\n   > Here's the onboarding roadmap for **[Entity Name]**:\n   >\n   > 1. **Upload Wallets** — Add on-chain wallets and\u002For exchange accounts\n   > 2. **Data Collection (Commit)** — Pull on-chain data for the uploaded wallets\n   > 3. **Validate Balances** — Cross-check TRES balances against on-chain sources\n   > 4. **Reconciliation** — Review and resolve any balance gaps\n   > 5. **Cost Basis** — Configure and run cost basis calculation\n   > 6. **Export Unidentified Addresses** — Extract 3rd-party addresses from transactions\n   > 7. **Import Contacts** — Label and import the identified addresses back into TRES\n   > 8. **Rollup Rules** — Set up transaction aggregation for high-volume wallets\n   >\n   > We'll go through each step together. Ready to start?\n\n---\n\n## The Onboarding Pipeline\n\nWork through each step in order. After completing each step, briefly summarize what was\naccomplished and ask the user if they're ready to move on. If a step isn't relevant\n(e.g., no high-volume wallets that need rollup rules), the user can skip it.\n\n**Important:** For each step, invoke the corresponding skill by name. Read its SKILL.md\nand follow its instructions. The sub-skill handles all the details — your job is to\ntransition smoothly between steps and keep the user oriented.\n\n### Step 1: Upload Wallets\n**Skill:** `tres-wallets-upload`\n\nInvoke the tres-wallets-upload skill. This guides the user through adding their on-chain\nwallets and\u002For exchange accounts into TRES. Once wallets are created, confirm the count\nand proceed.\n\n**Transition:** \"Wallets are uploaded. Next, we'll collect on-chain data for them.\"\n\n---\n\n### Step 2: Data Collection (Commit)\n**Skill:** `tres-data-collection-commit`\n\nInvoke the tres-data-collection-commit skill. This triggers on-chain data collection for\nthe wallets that were just uploaded. The commit may take some time depending on the number\nof wallets and their history.\n\n**Transition:** \"Data collection is in progress \u002F complete. Next, let's validate that the\nbalances TRES pulled match what's actually on-chain.\"\n\n---\n\n### Step 3: Validate Balances\n**Skill:** `tres-asset-balance-validation`\n\nInvoke the tres-asset-balance-validation skill. This compares TRES balances against DeBank\n(for EVM wallets) and generates a discrepancy report. Review any issues with the user.\n\n**Transition:** \"Balance validation is done. Let's move on to reconciliation to close any\nremaining gaps.\"\n\n---\n\n### Step 4: Reconciliation\n**Skill:** `tres-recon-gaps`\n\nInvoke the tres-recon-gaps skill. This fetches reconciliation gap data, displays it, and\nhelps the user resolve any on-chain vs. book balance discrepancies. If there are no gaps,\ncelebrate and move on.\n\n**Transition:** \"Reconciliation is squared away. Now let's set up cost basis calculation.\"\n\n---\n\n### Step 5: Cost Basis\n**Skill:** `tres-cost-basis`\n\nInvoke the tres-cost-basis skill. This walks through strategy selection if needed, triggers\ncost basis calculation, surfaces per-asset results and financial issues, and covers\nreevaluations, spec-ID rules, and related cost basis operations as needed. Review any\nfinancial issues (negative balances, missing fiat prices) that surface.\n\n**Transition:** \"Cost basis is configured and running. Next, let's identify the external\naddresses your wallets have been interacting with.\"\n\n---\n\n### Step 6: Export Unidentified Addresses\n**Skill:** `tres-export-3rd-party-contacts`\n\nInvoke the tres-export-3rd-party-contacts skill. This extracts all unidentified external\naddresses from the entity's transactions and exports them as an XLSX workbook. The user\nwill need to review and label these addresses (who each address belongs to).\n\n**Transition:** \"The unidentified addresses have been exported. Once you've labeled them,\nwe'll import them back as contacts. If you need time to fill in the names, we can pause\nhere and come back to the next step later — just say 'continue onboarding' when ready.\"\n\n**Note:** This step produces output that the user needs to review and fill in offline.\nOffer to pause the onboarding here and resume later. If the user wants to continue\nimmediately (maybe they'll label contacts later), that's fine — skip to Step 8.\n\n---\n\n### Step 7: Import Contacts\n**Skill:** `tres-import-contacts`\n\nInvoke the tres-import-contacts skill. This reads the user's labeled contacts file and\nimports the address-to-name mappings into the TRES address book.\n\n**Transition:** \"Contacts are imported! Last step — let's set up rollup rules for any\nhigh-volume wallets.\"\n\n---\n\n### Step 8: Rollup Rules\n**Skill:** `tres-rollup-rules`\n\nInvoke the tres-rollup-rules skill. This helps the user identify wallets with high\ntransaction volume and create daily or monthly rollup rules to consolidate small\nsub-transactions (gas fees, staking rewards, etc.) into cleaner aggregated entries.\n\nIf no wallets need rollup rules, skip this step.\n\n---\n\n## Completion\n\nOnce all steps are done (or skipped where appropriate), wrap up with a summary:\n\n> **Onboarding complete for [Entity Name]!**\n>\n> Here's what we accomplished:\n> - Uploaded X wallets across Y networks\n> - Collected on-chain data\n> - Validated balances (note any outstanding issues)\n> - Reconciled gaps (note status)\n> - Configured cost basis strategy: [strategy]\n> - Exported and imported Z contacts\n> - Set up N rollup rules\n>\n> The entity is ready to go in TRES Finance.\n\n---\n\n## Handling Interruptions and Resumption\n\nThe user may need to pause and come back later (especially around Step 6-7 where they\nneed to label contacts offline). Keep track of which step was last completed. If the\nuser comes back and says something like \"continue onboarding\" or \"where were we with\nonboarding [entity]?\", pick up from the next incomplete step.\n\n## Skipping Steps\n\nThe user can skip any step if it's not relevant. For example:\n- No EVM wallets → skip balance validation (Step 3)\n- No gaps → reconciliation completes quickly (Step 4)\n- No need for contacts right now → skip Steps 6-7\n- No high-volume wallets → skip rollup rules (Step 8)\n\nAlways respect the user's choice and move to the next step.\n",{"name":5,"description":57,"compatibility":58},"End-to-end onboarding of a new entity, customer, or account into TRES Finance. Orchestrates 8 steps in order: wallet upload, data collection (commit), balance validation, reconciliation, cost basis, export unidentified addresses, import contacts, and rollup rules. Trigger ONLY when the user explicitly wants to onboard a new entity, customer, or account — e.g. \"onboard a new entity\", \"onboard new customer\", \"start onboarding for [name]\", \"set up a new account in TRES\", \"run the full onboarding flow\", \"I need to onboard [company name]\", \"new entity onboarding\". Do NOT trigger for individual tasks — those have their own dedicated skills. If the user asks to \"add wallets\" without mentioning onboarding, use tres-wallets-upload. \"Validate balances\" alone is tres-asset-balance-validation. \"Run a commit\" alone is tres-data-collection-commit. Only trigger when the user wants the full pipeline.\n","Requires TRES Finance MCP connector and all sub-skills listed below","main","163301d1904c0a994539f5226ce0fcd65b8652bf","tres-finance-plugin\u002Fskills\u002Ftres-onboarding",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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add anthropics\u002Fclaude-plugins-community --skill tres-onboarding",{"tool":73,"command":74},"bunx","bunx skills add anthropics\u002Fclaude-plugins-community --skill tres-onboarding",{"tool":76,"command":77},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-plugins-community --skill tres-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-onboarding\u002FSKILL.md",true,[],[82,111,134,158,180,202],{"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":93,"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",[88,91,92],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[94,95,96,97,98,49,99,100,101,102,41,103,104,38,105,106,107,108,109,110],"wallets","tres wallets upload","upload","typing","ingestion","chain","creation","xlsx","selection","confirmation","connect","preview","api","batch","guides","on-chain","request",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"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",[],[118,96,119,120,121,122,49,123,124,125,126,127,128,129,43,130,131,132,34,133],"tres upload tx header validation","validation","bulk","do","import","parsing","for","manual","trigger","fix","missing","general","use","workflow","csv","with",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"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",[140],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[142,143,144,145,146,41,40,147,148,149,150,151,152,153,154,155,156,121,157,124],"tres tx story","Story","show","memory","hex","show me","analysis","analyze","me","diagram","generate","flow","asset","blockchain","STRING","visualize",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"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",[164],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[166,167,168,51,144,169,41,40,170,171,36,106,172,173,174,175,176,177,178,179],"tres settings management","settings","management","get","configure","ask","change","organization","update","read","write","sync","mcp graphql","flags",{"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},"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",[186,187],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[189,190,191,144,192,49,44,41,193,194,35,195,196,149,197,198,199,200,173,201],"tres rollup rules","Rules","rollup","gas","impact","reduce","review","consolidate","create","transactions","delete","data-driven","activity",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":210,"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",[208,209],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[195,211,191,212,213,214,215,216,43,42,41,193,40,105,217,35,218,219,197,220],"tres rollup review","standalone","never","mode","issues","design","candidate","filter","valid","catch"]