[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718F9C31MH0XFSZ29Z4X7WD":3,"skill-same:01M718F9C31MH0XFSZ29Z4X7WD":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M718F9C31MH0XFSZ29Z4X7WD","tres-request-skill-update",null,"Submit feedback about the TRES Claude plugin — bug reports, feature requests, skill improvements, new skill ideas, MCP issues, workflow friction, or positive feedback about what's working well. Use this skill whenever the user wants to share any kind of feedback about the plugin, its skills, or the TRES MCP. Trigger phrases include: \"submit feedback\", \"report a bug\", \"request a feature\", \"suggest an improvement\", \"I have an idea\", \"something is broken\", \"the skill isn't working\", \"I love this skill\", \"this worked great\", \"the MCP is returning wrong data\", \"the flow is confusing\", \"can you fix the skill\", \"file a skill request\", \"give feedback\", \"this could be better\". Also trigger proactively when the conversation appears to be wrapping up — e.g. the user says \"thanks\", \"that's all\", \"looks good\", \"we're done\", \"nothing else\", or any other signal that the task is complete. In that case, offer a brief feedback prompt instead of launching the full guided flow. Do NOT trigger for general questions about how a skill works — only when the user wants to submit feedback or the conversation is ending.","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-request-skill-update\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"request","update","tres request skill update","skill update","you","workflow","when","MCP","give feedback","new","only","good","issues","fix","up","re","submit","broken","brief","conversation","2026-11-10 10:12:30",false,"---\nname: tres-request-skill-update\ndescription: >\n  Submit feedback about the TRES Claude plugin — bug reports, feature requests, skill\n  improvements, new skill ideas, MCP issues, workflow friction, or positive feedback about\n  what's working well. Use this skill whenever the user wants to share any kind of feedback\n  about the plugin, its skills, or the TRES MCP. Trigger phrases include: \"submit feedback\",\n  \"report a bug\", \"request a feature\", \"suggest an improvement\", \"I have an idea\",\n  \"something is broken\", \"the skill isn't working\", \"I love this skill\", \"this worked great\",\n  \"the MCP is returning wrong data\", \"the flow is confusing\", \"can you fix the skill\",\n  \"file a skill request\", \"give feedback\", \"this could be better\".\n  Also trigger proactively when the conversation appears to be wrapping up — e.g. the user\n  says \"thanks\", \"that's all\", \"looks good\", \"we're done\", \"nothing else\", or any other\n  signal that the task is complete. In that case, offer a brief feedback prompt instead of\n  launching the full guided flow.\n  Do NOT trigger for general questions about how a skill works — only when the user wants to\n  submit feedback or the conversation is ending.\n---\n\n# TRES Plugin Feedback\n\nGuide the user through submitting clear, actionable feedback about the TRES Claude plugin\nand save it via the `save_ai_conversation_feedback` TRES MCP tool. No extra configuration\nrequired — works for any user with a TRES API token.\n\nThis skill operates in two modes:\n\n1. **Explicit feedback** — the user asks to submit feedback, report a bug, etc. Run the full\n   guided flow starting at Step 1.\n2. **End-of-conversation prompt** — the conversation is wrapping up. Offer a quick,\n   non-intrusive nudge (see Step 0) and only proceed to the full flow if the user opts in.\n\n---\n\n## Step 0 — End-of-Conversation Prompt\n\nWhen the conversation appears to be ending (the user says \"thanks\", \"that's all\", \"looks\ngood\", etc.) and this skill is triggered proactively:\n\nAsk casually:\n\n> **Before you go — any feedback on how this session went? Bugs, ideas, or things that could\n> be better? Happy to log it for the team in 30 seconds.**\n\n- If the user **declines** (\"no\", \"I'm good\", \"nah\") — say \"No worries, have a great day!\"\n  and stop. Do NOT push further.\n- If the user **shares something** — transition into Step 1 and run the full guided flow,\n  but keep it lightweight. Skip questions they've already answered in the conversation and\n  aim for a quick turnaround.\n- Keep the tone light and optional — this should never feel like a mandatory survey.\n\n---\n\n## Step 1 — Identify Submitter\n\n1. Call `get_viewer` (TRES MCP, no arguments) to identify the submitter.\n   - Extract the organization name from the response.\n   - If `get_viewer` fails, use `\"Unknown org\"` as the submitter and continue.\n\n2. Get the user's git identity for the feedback record:\n   ```bash\n   git config user.name && git config user.email\n   ```\n   Use line 1 as `agent_name` and line 2 as `agent_email`. If git is not available, use\n   the system username and leave email empty.\n\nTell the user: **\"You're connected as {orgName}. What feedback would you like to share?\"**\n\n---\n\n## Step 2 — Understand the Feedback\n\nLet the user describe their feedback in their own words first. Then classify it into one of\nthese categories based on what they said:\n\n| Category | When to use |\n|---|---|\n| Bug report | Something is broken, erroring, or producing wrong results |\n| Feature request | A new capability that doesn't exist yet |\n| Improvement | An existing feature works but could be better (UX, formatting, flow, performance) |\n| New skill idea | A proposal for an entirely new skill |\n| MCP \u002F data issue | The TRES MCP is returning wrong data, missing fields, or behaving unexpectedly |\n| Positive feedback | Something is working well and the user wants the team to know |\n| General feedback | Anything else — workflow friction, confusion, documentation, onboarding |\n\nConfirm the category with the user: **\"It sounds like this is a {category} — is that right?\"**\n\nIf the feedback is about a specific skill or MCP tool, identify which one. If it's general\nor about the plugin overall, note that.\n\n**Known skills:**\n\n| Skill | Description |\n|---|---|\n| `tres-asc845-swap-reprice-skill` | ASC 845 swap repricing to zero clearing account residuals |\n| `tres-explorer-tx-to-ledger` | Add explorer TX to the TRES ledger |\n| `tres-tx-story` | TX flow diagram and explanation |\n| `tres-recon-gaps` | Reconciliation gap resolution |\n| `tres-asset-balance-validation` | Balance validation vs DeBank |\n| `tres-report-analyzer` | Analyze TRES report XLSX exports |\n| `tres-report-advisor` | Recommend the right TRES report |\n| `tres-invoice-bill-matching` | Match txs to ERP invoices\u002Fbills |\n| `tres-export-3rd-party-contacts` | Export unidentified counterparties to XLSX |\n| `tres-import-contacts` | Import contacts from CSV\u002FXLSX |\n| `tres-cost-basis` | Cost basis calculation, strategy, issues, reevaluations, exports |\n| `tres-rollup-rules` | Sub-transaction rollup rules (aggregate txs) |\n| `tres-onboarding` | Full entity onboarding (orchestrates sub-skills) |\n| `tres-settings-management` | Org and platform settings |\n| `tres-wallets-upload` | Wallet onboarding |\n| `tres-upload-tx-header-validation` | Bulk transaction CSV header naming validation |\n| `tres-request-skill-update` | This feedback skill |\n\n> **Maintainer note**: update this table when new skills are added to the plugin.\n\n---\n\n## Step 3 — Dig Deeper\n\nBased on the category, ask targeted follow-up questions to make the feedback actionable.\nAsk one or two questions at a time — keep it conversational, not interrogative.\n\n**For bug reports:**\n- What exactly happened? What did you see?\n- What did you expect to happen instead?\n- What were you doing when it happened? (steps to reproduce)\n- Did you see an error message? If so, what did it say?\n- Can you share a specific example? (tx hash, wallet address, input you used)\n\n**For feature requests & improvements:**\n- What problem would this solve for you?\n- How do you handle this today without the feature?\n- Can you describe what the ideal experience would look like?\n- How often do you run into this need?\n\n**For new skill ideas:**\n- What workflow or task would this skill automate?\n- Who on your team would use it, and how often?\n- Can you walk through a concrete example of how you'd use it?\n- What data source would it need? (TRES MCP, external API, local files)\n\n**For MCP \u002F data issues:**\n- Which MCP tool or query was involved?\n- What data did you get back, and what was wrong about it?\n- What did you expect the data to look like?\n- Can you share the specific query or identifiers you used?\n\n**For positive feedback:**\n- What specifically worked well?\n- Was there anything that surprised you (in a good way)?\n- Is there a particular workflow or use case where it really shined?\n- Would you change anything to make it even better?\n\n**For general feedback:**\n- What part of the experience are you reacting to?\n- Was anything confusing or unclear?\n- What would have made it better?\n\nAdapt based on what the user has already told you — skip questions they've already answered.\nThe goal is to get enough detail that someone reading the feedback can understand the context\nand take action without needing to ask follow-up questions.\n\n---\n\n## Step 4 — Preview the Feedback\n\nCompose the feedback and show it to the user for review. Format it clearly:\n\n```\nHeadline: {concise summary — max 80 chars}\n\nCategory: {Bug report | Feature request | Improvement | New skill idea | MCP issue | Positive feedback | General}\nArea: {skill name, \"MCP\", or \"General\"}\nOrg: {orgName}\n\n---\n\n{Well-structured description that includes:\n - What the feedback is about (context)\n - The core issue, idea, or praise (substance)\n - Supporting details — steps to reproduce, examples, expected behavior, etc.\n - Impact — how often this comes up, how many people it affects, how it blocks work}\n\nTags: {comma-separated list}\n```\n\n**Writing the description:**\n- Synthesize the user's answers into a clear, readable narrative — don't just dump Q&A pairs.\n- Lead with the most important point.\n- Include concrete details (tx hashes, error messages, specific steps) — these are what make\n  feedback actionable.\n- For positive feedback, be specific about what worked and why it mattered.\n\nAlso show the user the **conversation excerpt** that will be submitted (see Step 5 format).\nThis gives them informed visibility into what leaves their machine.\n\nAsk: **\"Here's what I'll submit — does this capture everything? Want to change anything?\"**\n\nIterate if the user wants edits. Only proceed on explicit confirmation.\n\n---\n\n## Step 5 — Submit Feedback\n\nCall `save_ai_conversation_feedback` with these arguments:\n\n| Argument | Value |\n|---|---|\n| `headline` | Concise summary (max 80 chars). Prefix with category: `[Bug]`, `[Feature]`, `[Improvement]`, `[New Skill]`, `[MCP Issue]`, `[Praise]`, or `[Feedback]` |\n| `description` | The full structured description from Step 4 |\n| `conversation` | Scoped and redacted conversation excerpt (see format below) |\n| `tags` | Array — always include `\"plugin-feedback\"`, plus the category tag (`\"bug\"`, `\"feature\"`, `\"improvement\"`, `\"new-skill\"`, `\"mcp-issue\"`, `\"praise\"`, `\"general\"`), plus the skill name if applicable |\n| `agent_name` | From git config (Step 1) |\n| `agent_email` | From git config (Step 1) |\n\n**Conversation format** — include only the **last 30 exchanges** (user+assistant pairs)\nfrom your context window, not the entire session history. Apply a redaction pass before\nincluding any message:\n\n- Replace `Bearer [A-Za-z0-9._\\-]{20,}` → `Bearer [REDACTED]`\n- Replace standalone 64-character hex strings → `[REDACTED_HEX]`\n- Replace file paths matching `\u002FUsers\u002F\u003Cname>\u002F` or `\u002Fhome\u002F\u003Cname>\u002F` → `\u002FUsers\u002F[REDACTED]\u002F`\n- Remove any apparent BIP-39 mnemonic phrases (12–24 dictionary words)\n\nFormat:\n```\nUSER: \u003Ctext, redacted>\n\nASSISTANT: \u003Ctext, redacted>\n\nTOOL_CALL: \u003Ctool_name>(arg1=value1, arg2=value2)\nTOOL_RESULT: \u003Cone-line summary of the result>\n\n... continue for the last 30 exchanges only ...\n```\n\n---\n\n## Step 6 — Report Result\n\n**On success:**\nTell the user:\n> Your feedback has been submitted — thank you! The team will review it.\n\nIf the feedback was a bug or blocker, add:\n> If this is urgent, reach out to the team directly as well.\n\n**On failure:**\nSurface the error from the MCP tool and suggest:\n- Check that the TRES API token is valid\n- Try again — it may be a transient issue\n\n---\n\n## Error Handling\n\n| Situation | Action |\n|---|---|\n| `get_viewer` fails | Continue with \"Unknown org\" as submitter |\n| `save_ai_conversation_feedback` fails | Surface the error; suggest checking TRES API token |\n| User cancels at preview | Say \"No problem — feedback was not submitted\" and stop |\n| User provides empty description | Ask again — a description is required |\n| git config unavailable | Use system username for agent_name, leave agent_email empty |\n","# TRES Plugin Feedback\n\nGuide the user through submitting clear, actionable feedback about the TRES Claude plugin\nand save it via the `save_ai_conversation_feedback` TRES MCP tool. No extra configuration\nrequired — works for any user with a TRES API token.\n\nThis skill operates in two modes:\n\n1. **Explicit feedback** — the user asks to submit feedback, report a bug, etc. Run the full\n   guided flow starting at Step 1.\n2. **End-of-conversation prompt** — the conversation is wrapping up. Offer a quick,\n   non-intrusive nudge (see Step 0) and only proceed to the full flow if the user opts in.\n\n---\n\n## Step 0 — End-of-Conversation Prompt\n\nWhen the conversation appears to be ending (the user says \"thanks\", \"that's all\", \"looks\ngood\", etc.) and this skill is triggered proactively:\n\nAsk casually:\n\n> **Before you go — any feedback on how this session went? Bugs, ideas, or things that could\n> be better? Happy to log it for the team in 30 seconds.**\n\n- If the user **declines** (\"no\", \"I'm good\", \"nah\") — say \"No worries, have a great day!\"\n  and stop. Do NOT push further.\n- If the user **shares something** — transition into Step 1 and run the full guided flow,\n  but keep it lightweight. Skip questions they've already answered in the conversation and\n  aim for a quick turnaround.\n- Keep the tone light and optional — this should never feel like a mandatory survey.\n\n---\n\n## Step 1 — Identify Submitter\n\n1. Call `get_viewer` (TRES MCP, no arguments) to identify the submitter.\n   - Extract the organization name from the response.\n   - If `get_viewer` fails, use `\"Unknown org\"` as the submitter and continue.\n\n2. Get the user's git identity for the feedback record:\n   ```bash\n   git config user.name && git config user.email\n   ```\n   Use line 1 as `agent_name` and line 2 as `agent_email`. If git is not available, use\n   the system username and leave email empty.\n\nTell the user: **\"You're connected as {orgName}. What feedback would you like to share?\"**\n\n---\n\n## Step 2 — Understand the Feedback\n\nLet the user describe their feedback in their own words first. Then classify it into one of\nthese categories based on what they said:\n\n| Category | When to use |\n|---|---|\n| Bug report | Something is broken, erroring, or producing wrong results |\n| Feature request | A new capability that doesn't exist yet |\n| Improvement | An existing feature works but could be better (UX, formatting, flow, performance) |\n| New skill idea | A proposal for an entirely new skill |\n| MCP \u002F data issue | The TRES MCP is returning wrong data, missing fields, or behaving unexpectedly |\n| Positive feedback | Something is working well and the user wants the team to know |\n| General feedback | Anything else — workflow friction, confusion, documentation, onboarding |\n\nConfirm the category with the user: **\"It sounds like this is a {category} — is that right?\"**\n\nIf the feedback is about a specific skill or MCP tool, identify which one. If it's general\nor about the plugin overall, note that.\n\n**Known skills:**\n\n| Skill | Description |\n|---|---|\n| `tres-asc845-swap-reprice-skill` | ASC 845 swap repricing to zero clearing account residuals |\n| `tres-explorer-tx-to-ledger` | Add explorer TX to the TRES ledger |\n| `tres-tx-story` | TX flow diagram and explanation |\n| `tres-recon-gaps` | Reconciliation gap resolution |\n| `tres-asset-balance-validation` | Balance validation vs DeBank |\n| `tres-report-analyzer` | Analyze TRES report XLSX exports |\n| `tres-report-advisor` | Recommend the right TRES report |\n| `tres-invoice-bill-matching` | Match txs to ERP invoices\u002Fbills |\n| `tres-export-3rd-party-contacts` | Export unidentified counterparties to XLSX |\n| `tres-import-contacts` | Import contacts from CSV\u002FXLSX |\n| `tres-cost-basis` | Cost basis calculation, strategy, issues, reevaluations, exports |\n| `tres-rollup-rules` | Sub-transaction rollup rules (aggregate txs) |\n| `tres-onboarding` | Full entity onboarding (orchestrates sub-skills) |\n| `tres-settings-management` | Org and platform settings |\n| `tres-wallets-upload` | Wallet onboarding |\n| `tres-upload-tx-header-validation` | Bulk transaction CSV header naming validation |\n| `tres-request-skill-update` | This feedback skill |\n\n> **Maintainer note**: update this table when new skills are added to the plugin.\n\n---\n\n## Step 3 — Dig Deeper\n\nBased on the category, ask targeted follow-up questions to make the feedback actionable.\nAsk one or two questions at a time — keep it conversational, not interrogative.\n\n**For bug reports:**\n- What exactly happened? What did you see?\n- What did you expect to happen instead?\n- What were you doing when it happened? (steps to reproduce)\n- Did you see an error message? If so, what did it say?\n- Can you share a specific example? (tx hash, wallet address, input you used)\n\n**For feature requests & improvements:**\n- What problem would this solve for you?\n- How do you handle this today without the feature?\n- Can you describe what the ideal experience would look like?\n- How often do you run into this need?\n\n**For new skill ideas:**\n- What workflow or task would this skill automate?\n- Who on your team would use it, and how often?\n- Can you walk through a concrete example of how you'd use it?\n- What data source would it need? (TRES MCP, external API, local files)\n\n**For MCP \u002F data issues:**\n- Which MCP tool or query was involved?\n- What data did you get back, and what was wrong about it?\n- What did you expect the data to look like?\n- Can you share the specific query or identifiers you used?\n\n**For positive feedback:**\n- What specifically worked well?\n- Was there anything that surprised you (in a good way)?\n- Is there a particular workflow or use case where it really shined?\n- Would you change anything to make it even better?\n\n**For general feedback:**\n- What part of the experience are you reacting to?\n- Was anything confusing or unclear?\n- What would have made it better?\n\nAdapt based on what the user has already told you — skip questions they've already answered.\nThe goal is to get enough detail that someone reading the feedback can understand the context\nand take action without needing to ask follow-up questions.\n\n---\n\n## Step 4 — Preview the Feedback\n\nCompose the feedback and show it to the user for review. Format it clearly:\n\n```\nHeadline: {concise summary — max 80 chars}\n\nCategory: {Bug report | Feature request | Improvement | New skill idea | MCP issue | Positive feedback | General}\nArea: {skill name, \"MCP\", or \"General\"}\nOrg: {orgName}\n\n---\n\n{Well-structured description that includes:\n - What the feedback is about (context)\n - The core issue, idea, or praise (substance)\n - Supporting details — steps to reproduce, examples, expected behavior, etc.\n - Impact — how often this comes up, how many people it affects, how it blocks work}\n\nTags: {comma-separated list}\n```\n\n**Writing the description:**\n- Synthesize the user's answers into a clear, readable narrative — don't just dump Q&A pairs.\n- Lead with the most important point.\n- Include concrete details (tx hashes, error messages, specific steps) — these are what make\n  feedback actionable.\n- For positive feedback, be specific about what worked and why it mattered.\n\nAlso show the user the **conversation excerpt** that will be submitted (see Step 5 format).\nThis gives them informed visibility into what leaves their machine.\n\nAsk: **\"Here's what I'll submit — does this capture everything? Want to change anything?\"**\n\nIterate if the user wants edits. Only proceed on explicit confirmation.\n\n---\n\n## Step 5 — Submit Feedback\n\nCall `save_ai_conversation_feedback` with these arguments:\n\n| Argument | Value |\n|---|---|\n| `headline` | Concise summary (max 80 chars). Prefix with category: `[Bug]`, `[Feature]`, `[Improvement]`, `[New Skill]`, `[MCP Issue]`, `[Praise]`, or `[Feedback]` |\n| `description` | The full structured description from Step 4 |\n| `conversation` | Scoped and redacted conversation excerpt (see format below) |\n| `tags` | Array — always include `\"plugin-feedback\"`, plus the category tag (`\"bug\"`, `\"feature\"`, `\"improvement\"`, `\"new-skill\"`, `\"mcp-issue\"`, `\"praise\"`, `\"general\"`), plus the skill name if applicable |\n| `agent_name` | From git config (Step 1) |\n| `agent_email` | From git config (Step 1) |\n\n**Conversation format** — include only the **last 30 exchanges** (user+assistant pairs)\nfrom your context window, not the entire session history. Apply a redaction pass before\nincluding any message:\n\n- Replace `Bearer [A-Za-z0-9._\\-]{20,}` → `Bearer [REDACTED]`\n- Replace standalone 64-character hex strings → `[REDACTED_HEX]`\n- Replace file paths matching `\u002FUsers\u002F\u003Cname>\u002F` or `\u002Fhome\u002F\u003Cname>\u002F` → `\u002FUsers\u002F[REDACTED]\u002F`\n- Remove any apparent BIP-39 mnemonic phrases (12–24 dictionary words)\n\nFormat:\n```\nUSER: \u003Ctext, redacted>\n\nASSISTANT: \u003Ctext, redacted>\n\nTOOL_CALL: \u003Ctool_name>(arg1=value1, arg2=value2)\nTOOL_RESULT: \u003Cone-line summary of the result>\n\n... continue for the last 30 exchanges only ...\n```\n\n---\n\n## Step 6 — Report Result\n\n**On success:**\nTell the user:\n> Your feedback has been submitted — thank you! The team will review it.\n\nIf the feedback was a bug or blocker, add:\n> If this is urgent, reach out to the team directly as well.\n\n**On failure:**\nSurface the error from the MCP tool and suggest:\n- Check that the TRES API token is valid\n- Try again — it may be a transient issue\n\n---\n\n## Error Handling\n\n| Situation | Action |\n|---|---|\n| `get_viewer` fails | Continue with \"Unknown org\" as submitter |\n| `save_ai_conversation_feedback` fails | Surface the error; suggest checking TRES API token |\n| User cancels at preview | Say \"No problem — feedback was not submitted\" and stop |\n| User provides empty description | Ask again — a description is required |\n| git config unavailable | Use system username for agent_name, leave agent_email empty |\n",{"name":5,"description":7},"main","163301d1904c0a994539f5226ce0fcd65b8652bf","tres-finance-plugin\u002Fskills\u002Ftres-request-skill-update",357,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-10 15:47:08",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add anthropics\u002Fclaude-plugins-community --skill tres-request-skill-update",{"tool":63,"command":64},"bunx","bunx skills add anthropics\u002Fclaude-plugins-community --skill tres-request-skill-update",{"tool":66,"command":67},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-plugins-community --skill tres-request-skill-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-request-skill-update\u002FSKILL.md",true,[],[72,106,128,152,175,198],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":87,"publishedAt":44},"01M718G9QZ4B2DJVEB3MAW5ZB1","tres-wallets-upload","Upload and onboard multiple on-chain wallets or exchange accounts into Tres Finance. Use this skill whenever the user wants to add wallets, onboard wallets, import wallets, upload wallet addresses, ingest wallets, or connect exchanges into Tres — whether from a file (CSV\u002FExcel) or by typing them manually. This skill guides Claude through the full flow: wallet type selection → input collection → validation → preview with editable HTML table → exchange credential collection (if exchange) → user confirmation → batch creation via the TRES MCP API. Always trigger this skill for wallet onboarding, wallet data ingestion, or any request to \"add wallets to Tres\".","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-wallets-upload\u002FSKILL.md",[78,81,82],{"categoryNo":79,"categoryName":80,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[88,89,90,91,92,93,94,95,96,97,31,98,99,100,101,102,103,104,105,24],"wallets","tres wallets upload","upload","typing","ingestion","Wallet","chain","creation","xlsx","selection","confirmation","connect","collection","preview","api","batch","guides","on-chain",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":44},"01M718G5RD9064Z574RQ4SEY38","tres-upload-tx-header-validation","The exact column header names required by the TRES Finance bulk transaction CSV upload. Use whenever building, fixing, or validating the header row of a TRES manual transaction or sub-transaction upload CSV — especially after an upload fails with \"Missing required column(s): ...\". Trigger phrases include: 'fix my CSV headers', 'bulk transaction upload failed', 'missing required columns', 'validate TRES upload CSV', 'transaction CSV template headers'. This skill is ONLY about the header naming convention; it does not cover row values or upload workflow. Do NOT trigger for contacts import CSV (use tres-import-contacts), wallet upload CSV (use tres-wallets-upload), or general CSV parsing unrelated to bulk TX upload headers.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-upload-tx-header-validation\u002FSKILL.md",[],[113,90,114,115,116,117,93,118,119,120,121,37,122,123,34,124,29,125,126,127],"tres upload tx header validation","validation","bulk","do","import","parsing","for","manual","trigger","missing","general","use","csv","contacts","with",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":44},"01M718G1F3DBWTX5H9RWPHHB4F","tres-tx-story","Analyze a blockchain transaction by its hash using TRES Finance MCP and generate a visual flow diagram showing all asset movements, followed by a plain-language explanation of what happened. Use this skill whenever the user provides a transaction hash and asks to \"analyze\", \"explain\", \"visualize\", \"diagram\", \"show me what happened in\", or \"tell the story of\" a transaction. Also trigger when the user pastes a tx hash (long hex string starting with 0x) and asks anything about it. Always use this skill for transaction hash analysis — do not attempt to answer from memory alone.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-tx-story\u002FSKILL.md",[134],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[136,137,138,139,140,31,30,141,142,143,144,145,146,147,148,149,150,116,151,119],"tres tx story","Story","show","memory","hex","show me","analysis","analyze","me","diagram","generate","flow","asset","blockchain","STRING","visualize",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":44},"01M718FW5ST9J56WY4TJ5G5A7X","tres-settings-management","Manage Organization Settings and Platform Settings via the TRES MCP GraphQL API. Use when users ask about org settings, platform settings, configuration, feature flags, enable\u002Fdisable platforms, balance diff, commit strategy, cost basis, ERP, pricing, sync boundaries, or any setting read\u002Fwrite operation. Trigger phrases include \"get settings\", \"show settings\", \"update settings\", \"change settings\", \"enable platform\", \"disable platform\", \"balance diff\", \"commit strategy\", \"cost basis strategy\", \"set min sync date\", \"configure\", \"turn on\", \"turn off\".","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-settings-management\u002FSKILL.md",[158],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[160,161,162,163,138,164,31,30,165,166,167,102,168,169,25,170,171,172,173,174],"tres settings management","settings","management","SET","get","configure","ask","commit","change","organization","read","write","sync","mcp graphql","flags",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":183,"publishedAt":44},"01M718FND35X9DPTNR7JTX2YX8","tres-rollup-rules","Analyze an organization's sub-transaction patterns in TRES Finance, identify groups of repetitive transactions, and propose data-driven rollup rules that consolidate them into one aggregated entry per interval (daily or monthly) for cleaner ERP integration. Also lists and deletes rollup rules. Trigger this skill whenever the user asks about rollup rules, transaction aggregation, consolidating transactions, reducing transaction noise, rolling up gas fees, rolling up staking rewards, rolling up micro-transactions, or collapsing many small ledger entries into fewer summary entries. Also trigger on \"create a rollup rule\", \"suggest rollup rules\", \"what should I roll up\", \"show my rollup rules\", \"delete a rollup rule\", \"aggregate transactions\", \"too many transactions\", \"reduce transaction count\", \"roll up fees\", \"daily rollup\", \"monthly rollup\". If a wallet has too many transactions, high-frequency activity, or noisy ledger entries, proactively suggest rollup rules. For computing the EXACT impact of a single already-specified rule or reviewing submitted\u002Fpending rules, use the tres-rollup-review skill instead.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-rollup-rules\u002FSKILL.md",[181,182],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},[184,185,186,138,187,93,38,31,188,189,190,191,192,143,193,194,195,196,169,197],"tres rollup rules","Rules","rollup","gas","impact","reduce","Connector","review","consolidate","create","transactions","delete","data-driven","activity",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":206,"publishedAt":44},"01M718FFX3KV2JRFVS2RCM719D","tres-rollup-review","Compute the EXACT sub-transaction impact of a rollup rule in TRES Finance — every filter applied — and flag genuine problems (zero matches, overlap, config mistakes) before the rule is created. Two modes. Mode A: a pre-create quality gate invoked by the tres-rollup-rules skill to vet proposed candidate rules. Mode B: standalone review of a rule someone submitted or of existing PENDING rules. Trigger this skill when the user says \"review this rollup rule\", \"what would this rollup rule actually match\", \"preview the rollup impact\", \"how many transactions would this rule catch\", \"is this rollup rule valid\", \"validate my rollup rule\", \"check my pending rollup rules\", or \"review the rollup requests\". Do NOT use this to design or propose new rollups — that is tres-rollup-rules. This skill only measures impact and flags issues; it never executes mutations.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-rollup-review\u002FSKILL.md",[204,205],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},[191,207,186,208,209,210,36,211,34,33,31,188,30,101,212,190,213,214,193,215],"tres rollup review","standalone","never","mode","design","candidate","filter","valid","catch"]