[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-tres-onboarding":3,"mdc--asrjpl-key":37,"related-repo-anthropic-tres-onboarding":713,"related-org-anthropic-tres-onboarding":815},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"tres-onboarding","onboard entities into TRES Finance","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",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"anthropic","Anthropic","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fanthropic.png","anthropics",[13,17,20,23],{"name":14,"slug":15,"type":16},"Operations","operations","tag",{"name":18,"slug":19,"type":16},"Finance","finance",{"name":21,"slug":22,"type":16},"Accounting","accounting",{"name":24,"slug":25,"type":16},"Reconciliation","reconciliation",294,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community","2026-07-02T07:37:41.705565",null,69,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"Community plugin marketplace for Claude Cowork and Claude Code. Read-only mirror — submit plugins at clau.de\u002Fplugin-directory-submission.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Ftree\u002FHEAD\u002Ftres-finance-plugin\u002Fskills\u002Ftres-onboarding","---\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",{"data":38,"body":40},{"name":4,"description":6,"compatibility":39},"Requires TRES Finance MCP connector and all sub-skills listed below",{"type":41,"children":42},"root",[43,52,58,62,69,80,241,244,250,255,265,272,289,294,304,307,313,327,332,341,344,350,364,369,378,381,387,401,406,415,418,424,438,443,452,455,461,475,480,489,499,502,508,522,527,536,539,545,559,564,569,572,578,583,653,656,662,674,680,685,708],{"type":44,"tag":45,"props":46,"children":48},"element","h1",{"id":47},"tres-finance-full-entity-onboarding",[49],{"type":50,"value":51},"text","TRES Finance — Full Entity Onboarding",{"type":44,"tag":53,"props":54,"children":55},"p",{},[56],{"type":50,"value":57},"Orchestrate 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.",{"type":44,"tag":59,"props":60,"children":61},"hr",{},[],{"type":44,"tag":63,"props":64,"children":66},"h2",{"id":65},"before-you-start",[67],{"type":50,"value":68},"Before You Start",{"type":44,"tag":53,"props":70,"children":71},{},[72,78],{"type":44,"tag":73,"props":74,"children":75},"strong",{},[76],{"type":50,"value":77},"No visualizations for input gathering.",{"type":50,"value":79}," 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.",{"type":44,"tag":81,"props":82,"children":83},"ol",{},[84,95,124],{"type":44,"tag":85,"props":86,"children":87},"li",{},[88,93],{"type":44,"tag":73,"props":89,"children":90},{},[91],{"type":50,"value":92},"Confirm intent.",{"type":50,"value":94}," The user must have explicitly requested a full onboarding (new entity,\nnew customer, new account). If the request is ambiguous, ask: \"Are you looking to run the\nfull onboarding flow for a new entity, or do you just need help with a specific step\n(like uploading wallets or validating balances)?\"",{"type":44,"tag":85,"props":96,"children":97},{},[98,103,105],{"type":44,"tag":73,"props":99,"children":100},{},[101],{"type":50,"value":102},"Collect context.",{"type":50,"value":104}," Ask the user in plain text (no widgets, no forms) for:",{"type":44,"tag":106,"props":107,"children":108},"ul",{},[109,114,119],{"type":44,"tag":85,"props":110,"children":111},{},[112],{"type":50,"value":113},"The entity\u002Fcustomer\u002Faccount name",{"type":44,"tag":85,"props":115,"children":116},{},[117],{"type":50,"value":118},"Any wallets or exchange accounts they already have ready (file, list, etc.)",{"type":44,"tag":85,"props":120,"children":121},{},[122],{"type":50,"value":123},"Whether they have a target date in mind for the onboarding",{"type":44,"tag":85,"props":125,"children":126},{},[127,132,134],{"type":44,"tag":73,"props":128,"children":129},{},[130],{"type":50,"value":131},"Present the roadmap.",{"type":50,"value":133}," Before diving in, show the user the roadmap as plain text\nin the chat (not as an HTML widget or visualization) so they know what to expect.\nUse something like:",{"type":44,"tag":135,"props":136,"children":137},"blockquote",{},[138,154,236],{"type":44,"tag":53,"props":139,"children":140},{},[141,143,152],{"type":50,"value":142},"Here's the onboarding roadmap for ",{"type":44,"tag":73,"props":144,"children":145},{},[146],{"type":44,"tag":147,"props":148,"children":149},"span",{},[150],{"type":50,"value":151},"Entity Name",{"type":50,"value":153},":",{"type":44,"tag":81,"props":155,"children":156},{},[157,167,177,187,196,206,216,226],{"type":44,"tag":85,"props":158,"children":159},{},[160,165],{"type":44,"tag":73,"props":161,"children":162},{},[163],{"type":50,"value":164},"Upload Wallets",{"type":50,"value":166}," — Add on-chain wallets and\u002For exchange accounts",{"type":44,"tag":85,"props":168,"children":169},{},[170,175],{"type":44,"tag":73,"props":171,"children":172},{},[173],{"type":50,"value":174},"Data Collection (Commit)",{"type":50,"value":176}," — Pull on-chain data for the uploaded wallets",{"type":44,"tag":85,"props":178,"children":179},{},[180,185],{"type":44,"tag":73,"props":181,"children":182},{},[183],{"type":50,"value":184},"Validate Balances",{"type":50,"value":186}," — Cross-check TRES balances against on-chain sources",{"type":44,"tag":85,"props":188,"children":189},{},[190,194],{"type":44,"tag":73,"props":191,"children":192},{},[193],{"type":50,"value":24},{"type":50,"value":195}," — Review and resolve any balance gaps",{"type":44,"tag":85,"props":197,"children":198},{},[199,204],{"type":44,"tag":73,"props":200,"children":201},{},[202],{"type":50,"value":203},"Cost Basis",{"type":50,"value":205}," — Configure and run cost basis calculation",{"type":44,"tag":85,"props":207,"children":208},{},[209,214],{"type":44,"tag":73,"props":210,"children":211},{},[212],{"type":50,"value":213},"Export Unidentified Addresses",{"type":50,"value":215}," — Extract 3rd-party addresses from transactions",{"type":44,"tag":85,"props":217,"children":218},{},[219,224],{"type":44,"tag":73,"props":220,"children":221},{},[222],{"type":50,"value":223},"Import Contacts",{"type":50,"value":225}," — Label and import the identified addresses back into TRES",{"type":44,"tag":85,"props":227,"children":228},{},[229,234],{"type":44,"tag":73,"props":230,"children":231},{},[232],{"type":50,"value":233},"Rollup Rules",{"type":50,"value":235}," — Set up transaction aggregation for high-volume wallets",{"type":44,"tag":53,"props":237,"children":238},{},[239],{"type":50,"value":240},"We'll go through each step together. Ready to start?",{"type":44,"tag":59,"props":242,"children":243},{},[],{"type":44,"tag":63,"props":245,"children":247},{"id":246},"the-onboarding-pipeline",[248],{"type":50,"value":249},"The Onboarding Pipeline",{"type":44,"tag":53,"props":251,"children":252},{},[253],{"type":50,"value":254},"Work 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.",{"type":44,"tag":53,"props":256,"children":257},{},[258,263],{"type":44,"tag":73,"props":259,"children":260},{},[261],{"type":50,"value":262},"Important:",{"type":50,"value":264}," 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.",{"type":44,"tag":266,"props":267,"children":269},"h3",{"id":268},"step-1-upload-wallets",[270],{"type":50,"value":271},"Step 1: Upload Wallets",{"type":44,"tag":53,"props":273,"children":274},{},[275,280,282],{"type":44,"tag":73,"props":276,"children":277},{},[278],{"type":50,"value":279},"Skill:",{"type":50,"value":281}," ",{"type":44,"tag":283,"props":284,"children":286},"code",{"className":285},[],[287],{"type":50,"value":288},"tres-wallets-upload",{"type":44,"tag":53,"props":290,"children":291},{},[292],{"type":50,"value":293},"Invoke 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.",{"type":44,"tag":53,"props":295,"children":296},{},[297,302],{"type":44,"tag":73,"props":298,"children":299},{},[300],{"type":50,"value":301},"Transition:",{"type":50,"value":303}," \"Wallets are uploaded. Next, we'll collect on-chain data for them.\"",{"type":44,"tag":59,"props":305,"children":306},{},[],{"type":44,"tag":266,"props":308,"children":310},{"id":309},"step-2-data-collection-commit",[311],{"type":50,"value":312},"Step 2: Data Collection (Commit)",{"type":44,"tag":53,"props":314,"children":315},{},[316,320,321],{"type":44,"tag":73,"props":317,"children":318},{},[319],{"type":50,"value":279},{"type":50,"value":281},{"type":44,"tag":283,"props":322,"children":324},{"className":323},[],[325],{"type":50,"value":326},"tres-data-collection-commit",{"type":44,"tag":53,"props":328,"children":329},{},[330],{"type":50,"value":331},"Invoke 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.",{"type":44,"tag":53,"props":333,"children":334},{},[335,339],{"type":44,"tag":73,"props":336,"children":337},{},[338],{"type":50,"value":301},{"type":50,"value":340}," \"Data collection is in progress \u002F complete. Next, let's validate that the\nbalances TRES pulled match what's actually on-chain.\"",{"type":44,"tag":59,"props":342,"children":343},{},[],{"type":44,"tag":266,"props":345,"children":347},{"id":346},"step-3-validate-balances",[348],{"type":50,"value":349},"Step 3: Validate Balances",{"type":44,"tag":53,"props":351,"children":352},{},[353,357,358],{"type":44,"tag":73,"props":354,"children":355},{},[356],{"type":50,"value":279},{"type":50,"value":281},{"type":44,"tag":283,"props":359,"children":361},{"className":360},[],[362],{"type":50,"value":363},"tres-asset-balance-validation",{"type":44,"tag":53,"props":365,"children":366},{},[367],{"type":50,"value":368},"Invoke 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.",{"type":44,"tag":53,"props":370,"children":371},{},[372,376],{"type":44,"tag":73,"props":373,"children":374},{},[375],{"type":50,"value":301},{"type":50,"value":377}," \"Balance validation is done. Let's move on to reconciliation to close any\nremaining gaps.\"",{"type":44,"tag":59,"props":379,"children":380},{},[],{"type":44,"tag":266,"props":382,"children":384},{"id":383},"step-4-reconciliation",[385],{"type":50,"value":386},"Step 4: Reconciliation",{"type":44,"tag":53,"props":388,"children":389},{},[390,394,395],{"type":44,"tag":73,"props":391,"children":392},{},[393],{"type":50,"value":279},{"type":50,"value":281},{"type":44,"tag":283,"props":396,"children":398},{"className":397},[],[399],{"type":50,"value":400},"tres-recon-gaps",{"type":44,"tag":53,"props":402,"children":403},{},[404],{"type":50,"value":405},"Invoke 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.",{"type":44,"tag":53,"props":407,"children":408},{},[409,413],{"type":44,"tag":73,"props":410,"children":411},{},[412],{"type":50,"value":301},{"type":50,"value":414}," \"Reconciliation is squared away. Now let's set up cost basis calculation.\"",{"type":44,"tag":59,"props":416,"children":417},{},[],{"type":44,"tag":266,"props":419,"children":421},{"id":420},"step-5-cost-basis",[422],{"type":50,"value":423},"Step 5: Cost Basis",{"type":44,"tag":53,"props":425,"children":426},{},[427,431,432],{"type":44,"tag":73,"props":428,"children":429},{},[430],{"type":50,"value":279},{"type":50,"value":281},{"type":44,"tag":283,"props":433,"children":435},{"className":434},[],[436],{"type":50,"value":437},"tres-cost-basis",{"type":44,"tag":53,"props":439,"children":440},{},[441],{"type":50,"value":442},"Invoke 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.",{"type":44,"tag":53,"props":444,"children":445},{},[446,450],{"type":44,"tag":73,"props":447,"children":448},{},[449],{"type":50,"value":301},{"type":50,"value":451}," \"Cost basis is configured and running. Next, let's identify the external\naddresses your wallets have been interacting with.\"",{"type":44,"tag":59,"props":453,"children":454},{},[],{"type":44,"tag":266,"props":456,"children":458},{"id":457},"step-6-export-unidentified-addresses",[459],{"type":50,"value":460},"Step 6: Export Unidentified Addresses",{"type":44,"tag":53,"props":462,"children":463},{},[464,468,469],{"type":44,"tag":73,"props":465,"children":466},{},[467],{"type":50,"value":279},{"type":50,"value":281},{"type":44,"tag":283,"props":470,"children":472},{"className":471},[],[473],{"type":50,"value":474},"tres-export-3rd-party-contacts",{"type":44,"tag":53,"props":476,"children":477},{},[478],{"type":50,"value":479},"Invoke 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).",{"type":44,"tag":53,"props":481,"children":482},{},[483,487],{"type":44,"tag":73,"props":484,"children":485},{},[486],{"type":50,"value":301},{"type":50,"value":488}," \"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.\"",{"type":44,"tag":53,"props":490,"children":491},{},[492,497],{"type":44,"tag":73,"props":493,"children":494},{},[495],{"type":50,"value":496},"Note:",{"type":50,"value":498}," 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.",{"type":44,"tag":59,"props":500,"children":501},{},[],{"type":44,"tag":266,"props":503,"children":505},{"id":504},"step-7-import-contacts",[506],{"type":50,"value":507},"Step 7: Import Contacts",{"type":44,"tag":53,"props":509,"children":510},{},[511,515,516],{"type":44,"tag":73,"props":512,"children":513},{},[514],{"type":50,"value":279},{"type":50,"value":281},{"type":44,"tag":283,"props":517,"children":519},{"className":518},[],[520],{"type":50,"value":521},"tres-import-contacts",{"type":44,"tag":53,"props":523,"children":524},{},[525],{"type":50,"value":526},"Invoke 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.",{"type":44,"tag":53,"props":528,"children":529},{},[530,534],{"type":44,"tag":73,"props":531,"children":532},{},[533],{"type":50,"value":301},{"type":50,"value":535}," \"Contacts are imported! Last step — let's set up rollup rules for any\nhigh-volume wallets.\"",{"type":44,"tag":59,"props":537,"children":538},{},[],{"type":44,"tag":266,"props":540,"children":542},{"id":541},"step-8-rollup-rules",[543],{"type":50,"value":544},"Step 8: Rollup Rules",{"type":44,"tag":53,"props":546,"children":547},{},[548,552,553],{"type":44,"tag":73,"props":549,"children":550},{},[551],{"type":50,"value":279},{"type":50,"value":281},{"type":44,"tag":283,"props":554,"children":556},{"className":555},[],[557],{"type":50,"value":558},"tres-rollup-rules",{"type":44,"tag":53,"props":560,"children":561},{},[562],{"type":50,"value":563},"Invoke 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.",{"type":44,"tag":53,"props":565,"children":566},{},[567],{"type":50,"value":568},"If no wallets need rollup rules, skip this step.",{"type":44,"tag":59,"props":570,"children":571},{},[],{"type":44,"tag":63,"props":573,"children":575},{"id":574},"completion",[576],{"type":50,"value":577},"Completion",{"type":44,"tag":53,"props":579,"children":580},{},[581],{"type":50,"value":582},"Once all steps are done (or skipped where appropriate), wrap up with a summary:",{"type":44,"tag":135,"props":584,"children":585},{},[586,600,605,648],{"type":44,"tag":53,"props":587,"children":588},{},[589],{"type":44,"tag":73,"props":590,"children":591},{},[592,594,598],{"type":50,"value":593},"Onboarding complete for ",{"type":44,"tag":147,"props":595,"children":596},{},[597],{"type":50,"value":151},{"type":50,"value":599},"!",{"type":44,"tag":53,"props":601,"children":602},{},[603],{"type":50,"value":604},"Here's what we accomplished:",{"type":44,"tag":106,"props":606,"children":607},{},[608,613,618,623,628,638,643],{"type":44,"tag":85,"props":609,"children":610},{},[611],{"type":50,"value":612},"Uploaded X wallets across Y networks",{"type":44,"tag":85,"props":614,"children":615},{},[616],{"type":50,"value":617},"Collected on-chain data",{"type":44,"tag":85,"props":619,"children":620},{},[621],{"type":50,"value":622},"Validated balances (note any outstanding issues)",{"type":44,"tag":85,"props":624,"children":625},{},[626],{"type":50,"value":627},"Reconciled gaps (note status)",{"type":44,"tag":85,"props":629,"children":630},{},[631,633],{"type":50,"value":632},"Configured cost basis strategy: ",{"type":44,"tag":147,"props":634,"children":635},{},[636],{"type":50,"value":637},"strategy",{"type":44,"tag":85,"props":639,"children":640},{},[641],{"type":50,"value":642},"Exported and imported Z contacts",{"type":44,"tag":85,"props":644,"children":645},{},[646],{"type":50,"value":647},"Set up N rollup rules",{"type":44,"tag":53,"props":649,"children":650},{},[651],{"type":50,"value":652},"The entity is ready to go in TRES Finance.",{"type":44,"tag":59,"props":654,"children":655},{},[],{"type":44,"tag":63,"props":657,"children":659},{"id":658},"handling-interruptions-and-resumption",[660],{"type":50,"value":661},"Handling Interruptions and Resumption",{"type":44,"tag":53,"props":663,"children":664},{},[665,667,672],{"type":50,"value":666},"The 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 ",{"type":44,"tag":147,"props":668,"children":669},{},[670],{"type":50,"value":671},"entity",{"type":50,"value":673},"?\", pick up from the next incomplete step.",{"type":44,"tag":63,"props":675,"children":677},{"id":676},"skipping-steps",[678],{"type":50,"value":679},"Skipping Steps",{"type":44,"tag":53,"props":681,"children":682},{},[683],{"type":50,"value":684},"The user can skip any step if it's not relevant. For example:",{"type":44,"tag":106,"props":686,"children":687},{},[688,693,698,703],{"type":44,"tag":85,"props":689,"children":690},{},[691],{"type":50,"value":692},"No EVM wallets → skip balance validation (Step 3)",{"type":44,"tag":85,"props":694,"children":695},{},[696],{"type":50,"value":697},"No gaps → reconciliation completes quickly (Step 4)",{"type":44,"tag":85,"props":699,"children":700},{},[701],{"type":50,"value":702},"No need for contacts right now → skip Steps 6-7",{"type":44,"tag":85,"props":704,"children":705},{},[706],{"type":50,"value":707},"No high-volume wallets → skip rollup rules (Step 8)",{"type":44,"tag":53,"props":709,"children":710},{},[711],{"type":50,"value":712},"Always respect the user's choice and move to the next step.",{"items":714,"total":814},[715,734,753,767,777,789,801],{"slug":716,"name":716,"fn":717,"description":718,"org":719,"tags":720,"stars":26,"repoUrl":27,"updatedAt":733},"quickdesign","generate AI media assets","Use the `quickdesign` CLI to generate AI media — UGC promo videos, image edits, product creatives, video upscales — through Seedance, Kling, Sora2, Nano Banana, and GPT Image. Invoke this skill whenever the user asks for a talking-avatar video, multi-segment ad \u002F promo \u002F explainer, image edit (object swap, angle change, state change), product photoshoot, or video upscale via QuickDesign.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[721,724,727,730],{"name":722,"slug":723,"type":16},"Creative","creative",{"name":725,"slug":726,"type":16},"Image Generation","image-generation",{"name":728,"slug":729,"type":16},"Marketing","marketing",{"name":731,"slug":732,"type":16},"Video","video","2026-07-01T08:09:32.316182",{"slug":735,"name":735,"fn":736,"description":737,"org":738,"tags":739,"stars":26,"repoUrl":27,"updatedAt":752},"testdino-audit","audit Playwright test code","Use only when the user explicitly asks for a TestDino audit of Playwright automated test code. Routes through the audit tools the TestDino MCP server exposes (get_audit_report + submit_audit_report, or the legacy test_audit). For generic code review or non-Playwright targets, do a normal review instead.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[740,743,746,749],{"name":741,"slug":742,"type":16},"Audit","audit",{"name":744,"slug":745,"type":16},"Code Analysis","code-analysis",{"name":747,"slug":748,"type":16},"Playwright","playwright",{"name":750,"slug":751,"type":16},"Testing","testing","2026-07-02T07:37:17.341081",{"slug":754,"name":754,"fn":755,"description":756,"org":757,"tags":758,"stars":26,"repoUrl":27,"updatedAt":766},"testdino-health","manage TestDino connection status","Use when the user wants to check TestDino connection status, validate their PAT, discover available organizations and projects, or find the right projectId. Always call this first when the project context is ambiguous before any other TestDino tool.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[759,762,765],{"name":760,"slug":761,"type":16},"Monitoring","monitoring",{"name":763,"slug":764,"type":16},"QA","qa",{"name":750,"slug":751,"type":16},"2026-07-02T07:37:18.566504",{"slug":768,"name":768,"fn":769,"description":770,"org":771,"tags":772,"stars":26,"repoUrl":27,"updatedAt":776},"testdino-manual-runs","manage manual QA execution runs in TestDino","Use when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed\u002Ffailed\u002Fblocked\u002Fskipped\u002Fretest\u002Funtested). Accepts counter-style IDs like RUN-12 and TC-156.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[773,774,775],{"name":14,"slug":15,"type":16},{"name":763,"slug":764,"type":16},{"name":750,"slug":751,"type":16},"2026-07-02T07:37:23.446065",{"slug":778,"name":778,"fn":779,"description":780,"org":781,"tags":782,"stars":26,"repoUrl":27,"updatedAt":788},"testdino-manual-tests","manage manual QA test cases in TestDino","Use when the user wants to create, update, or browse manual QA test cases and suites in TestDino — not execution runs. Covers list_manual_test_suites, list_manual_test_cases, get_manual_test_case, create_manual_test_case, update_manual_test_case, create_manual_test_suite.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[783,786,787],{"name":784,"slug":785,"type":16},"Documentation","documentation",{"name":763,"slug":764,"type":16},{"name":750,"slug":751,"type":16},"2026-07-02T07:37:22.247052",{"slug":790,"name":790,"fn":791,"description":792,"org":793,"tags":794,"stars":26,"repoUrl":27,"updatedAt":800},"testdino-releases","manage TestDino releases and milestones","Use when the user wants to browse, inspect, create, or update releases\u002Fmilestones in a TestDino project. Covers list_releases, get_release, create_release, and update_release. Accepts counter-style IDs like MS-12.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[795,798,799],{"name":796,"slug":797,"type":16},"Project Management","project-management",{"name":763,"slug":764,"type":16},{"name":750,"slug":751,"type":16},"2026-07-02T07:37:19.793846",{"slug":802,"name":802,"fn":803,"description":804,"org":805,"tags":806,"stars":26,"repoUrl":27,"updatedAt":813},"testdino-runs","inspect automated test runs","Use when the user wants to inspect automated test runs, list failed or flaky tests, debug a failing testcase with historical context, or filter runs by branch, commit, author, environment, browser, status, or tags. Includes list_testruns, get_run_details, list_testcase, get_testcase_details, and debug_testcase.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[807,810,811,812],{"name":808,"slug":809,"type":16},"Debugging","debugging",{"name":747,"slug":748,"type":16},{"name":763,"slug":764,"type":16},{"name":750,"slug":751,"type":16},"2026-07-02T07:37:16.07175",30,{"items":816,"total":999},[817,836,850,862,881,892,913,933,947,962,970,983],{"slug":818,"name":818,"fn":819,"description":820,"org":821,"tags":822,"stars":833,"repoUrl":834,"updatedAt":835},"algorithmic-art","create algorithmic art with p5.js","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[823,824,827,830],{"name":722,"slug":723,"type":16},{"name":825,"slug":826,"type":16},"Design","design",{"name":828,"slug":829,"type":16},"Generative Art","generative-art",{"name":831,"slug":832,"type":16},"JavaScript","javascript",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-04-06T17:56:15.455818",{"slug":837,"name":837,"fn":838,"description":839,"org":840,"tags":841,"stars":833,"repoUrl":834,"updatedAt":849},"brand-guidelines","apply Anthropic brand colors and typography","Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[842,845,846],{"name":843,"slug":844,"type":16},"Branding","branding",{"name":825,"slug":826,"type":16},{"name":847,"slug":848,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":851,"name":851,"fn":852,"description":853,"org":854,"tags":855,"stars":833,"repoUrl":834,"updatedAt":861},"canvas-design","create posters and visual art as PNG or PDF","Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[856,857,858],{"name":722,"slug":723,"type":16},{"name":825,"slug":826,"type":16},{"name":859,"slug":860,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":863,"name":863,"fn":864,"description":865,"org":866,"tags":867,"stars":833,"repoUrl":834,"updatedAt":880},"claude-api","build apps with the Claude API","Reference for the Claude API \u002F Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.\nTRIGGER — read BEFORE opening the target file; don't skip because it \"looks like a one-liner\" — whenever: the prompt names Claude\u002FAnthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing\u002Fmodel choice\u002Flimits\u002Fcaching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent\u002FMCP\u002Ftool-definition\u002Fmulti-agent\u002FRAG\u002FLLM-judge\u002Fcomputer-use; generate\u002Fsummarize\u002Fextract\u002Fclassify\u002Frewrite\u002Fconverse over NL; debugging refusals\u002Fcutoffs\u002Fstreaming\u002Ftool-calls\u002Ftokens).\nSKIP only when another provider is being worked on (overrides all triggers): OpenAI\u002FGPT\u002FGemini\u002FLlama\u002FMistral\u002FCohere\u002FOllama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[868,871,872,875,877],{"name":869,"slug":870,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":873,"slug":874,"type":16},"Anthropic SDK","anthropic-sdk",{"name":876,"slug":863,"type":16},"Claude API",{"name":878,"slug":879,"type":16},"LLM","llm","2026-07-28T05:36:08.213335",{"slug":882,"name":882,"fn":883,"description":884,"org":885,"tags":886,"stars":833,"repoUrl":834,"updatedAt":891},"doc-coauthoring","co-author documentation and technical specs","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[887,888],{"name":784,"slug":785,"type":16},{"name":889,"slug":890,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":893,"name":893,"fn":894,"description":895,"org":896,"tags":897,"stars":833,"repoUrl":834,"updatedAt":912},"docx","create and edit Word documents","Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[898,901,903,906,909],{"name":899,"slug":900,"type":16},"Documents","documents",{"name":902,"slug":893,"type":16},"DOCX",{"name":904,"slug":905,"type":16},"Office","office",{"name":907,"slug":908,"type":16},"Templates","templates",{"name":910,"slug":911,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":914,"name":914,"fn":915,"description":916,"org":917,"tags":918,"stars":833,"repoUrl":834,"updatedAt":932},"frontend-design","design production-grade frontend interfaces","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[919,920,923,926,929],{"name":825,"slug":826,"type":16},{"name":921,"slug":922,"type":16},"Frontend","frontend",{"name":924,"slug":925,"type":16},"React","react",{"name":927,"slug":928,"type":16},"Tailwind CSS","tailwind-css",{"name":930,"slug":931,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":934,"name":934,"fn":935,"description":936,"org":937,"tags":938,"stars":833,"repoUrl":834,"updatedAt":946},"internal-comms","write internal company communications","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[939,942,943],{"name":940,"slug":941,"type":16},"Communications","communications",{"name":907,"slug":908,"type":16},{"name":944,"slug":945,"type":16},"Writing","writing","2026-04-06T17:56:20.695522",{"slug":948,"name":948,"fn":949,"description":950,"org":951,"tags":952,"stars":833,"repoUrl":834,"updatedAt":961},"mcp-builder","build MCP servers","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node\u002FTypeScript (MCP SDK).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[953,954,957,958],{"name":869,"slug":870,"type":16},{"name":955,"slug":956,"type":16},"API Development","api-development",{"name":878,"slug":879,"type":16},{"name":959,"slug":960,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":860,"name":860,"fn":963,"description":964,"org":965,"tags":966,"stars":833,"repoUrl":834,"updatedAt":969},"read edit and manipulate PDF files","Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text\u002Ftables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting\u002Fdecrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[967,968],{"name":899,"slug":900,"type":16},{"name":859,"slug":860,"type":16},"2026-04-06T17:56:02.483316",{"slug":971,"name":971,"fn":972,"description":973,"org":974,"tags":975,"stars":833,"repoUrl":834,"updatedAt":982},"pptx","create and edit PowerPoint presentations","Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[976,979],{"name":977,"slug":978,"type":16},"PowerPoint","powerpoint",{"name":980,"slug":981,"type":16},"Presentations","presentations","2026-07-18T05:16:24.1471",{"slug":984,"name":984,"fn":985,"description":986,"org":987,"tags":988,"stars":833,"repoUrl":834,"updatedAt":998},"skill-creator","create and optimize agent skills","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[989,990,991,994,997],{"name":869,"slug":870,"type":16},{"name":784,"slug":785,"type":16},{"name":992,"slug":993,"type":16},"Evals","evals",{"name":995,"slug":996,"type":16},"Performance","performance",{"name":889,"slug":890,"type":16},"2026-04-19T06:45:40.804",490]