[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718CWKWRFZ0MGR72EJ82TJM":3,"skill-same:01M718CWKWRFZ0MGR72EJ82TJM":83},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M718CWKWRFZ0MGR72EJ82TJM","tres-asc845-swap-reprice-skill",null,"Reprice swap transaction legs under ASC 845 (Nonmonetary Transactions) to ensure clearing accounts net to zero. Use this skill whenever the user wants to: reprice swaps, fix clearing account residuals, apply equal-value exchange to swap legs, run setBatchUseCounterpartyFiatValue, zero out a clearing account, apply ASC 845, fix swap pricing mismatches, ensure no gain\u002Floss on swaps, or close a month where a swaps\u002Ftrade clearing account has a residual balance. Also trigger when the user mentions \"counterparty fiat value\", \"swap repricing\", \"clearing account net to zero\", or \"equal value exchange\".","anthropics\u002Fclaude-plugins-community","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M718C1RS4JJFM9KNJMTCAYJG",4892,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-asc845-swap-reprice-skill\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],"tres asc845 swap reprice skill","swap","close","exchange","trade","transactions","transaction","Connector","apply","when","use","MCP","fiat","fix","trigger","pricing","ZeRO","value","balance","asc","2026-11-10 10:12:30",false,"---\nname: tres-asc845-swap-reprice-skill\ndescription: >\n  Reprice swap transaction legs under ASC 845 (Nonmonetary Transactions) to ensure clearing accounts\n  net to zero. Use this skill whenever the user wants to: reprice swaps, fix clearing account residuals,\n  apply equal-value exchange to swap legs, run setBatchUseCounterpartyFiatValue, zero out a clearing\n  account, apply ASC 845, fix swap pricing mismatches, ensure no gain\u002Floss on swaps, or close a month\n  where a swaps\u002Ftrade clearing account has a residual balance. Also trigger when the user mentions\n  \"counterparty fiat value\", \"swap repricing\", \"clearing account net to zero\", or \"equal value exchange\".\ncompatibility: \"Requires TRES Finance MCP connector\"\n---\n\n# ASC 845 Swap Repricing Skill\n\n## Purpose\n\nImplements **equal-value exchange under ASC 845 (Nonmonetary Transactions)** for swap transactions\nin TRES Finance. In a simultaneous swap, the fair value of the asset surrendered (outflow) is the\nbest evidence of the fair value of the asset received (inflow). This skill reprices inflow legs to\nmatch outflow legs so that clearing accounts net to zero.\n\n## When to Use\n\n- A swaps\u002Ftrade clearing account has a non-zero residual after month-end\n- User wants to apply ASC 845 to a population of swap transactions\n- User says \"setBatchUseCounterpartyFiatValue\" or similar\n\n## MCP Server\n\nAll GraphQL calls use the **`user-tres-finance`** MCP server (`execute` tool).\n\nVariable keys and nested input fields MUST use **camelCase** (e.g. `timestamp_Gte`, not `timestamp_gte`).\n\n## Prerequisites\n\n- TRES Finance MCP connection (`user-tres-finance`)\n- The user must specify:\n  1. **Target ERP account** — the clearing account to zero out (e.g. \"Swaps Clearing Account\", NS #818)\n  2. **Transaction scope** — either a date range (timestamp_Gte \u002F timestamp_Lte) or specific tx hashes\n  3. **Confirmation** — user must approve before mutations are executed\n\n## Workflow\n\n### Step 1: Gather Parameters\n\nAsk the user for:\n- Target ERP account name or ID (the clearing account)\n- Date range OR list of transaction hashes\n- **Activity tags** (optional) — filter to only transactions with specific classification activities\n  (e.g. \"STAKING LOCKUP\", \"SWAP\"). None, one, or many may be selected. If omitted, all activities\n  are included. Use `tx_Classification_Activity_In` on the TRES query.\n- Currency (default: USD)\n- Whether to run in **dry-run** (preview only) or **execute** mode\n\n### Step 2: Query Subtransactions\n\nUse the TRES `subTransaction` query to fetch all subtransactions in scope. Include these fields:\n```graphql\n{\n  id\n  amount\n  balanceFactor\n  timestamp\n  fiatValue\n  isManualFiatValue\n  belongsTo { id name }\n  asset { assetClass { symbol } }\n  tx { id identifier classification { activity } }\n  flowRule {\n    ruleName\n    integrationAccount { name value }\n  }\n}\n```\n\nIf activity tags were specified, pass them as `tx_Classification_Activity_In: [\"STAKING LOCKUP\", \"SWAP\"]`\non the query. Note: transactions with `classification: null` will be excluded when this filter is used,\nso only apply it when the user explicitly requests it.\n\nPaginate in batches of 50 (to avoid timeouts). Save the combined results to a JSON file for the orchestrator script.\n\n### Step 3: Run the Orchestrator Script\n\nFrom the skill `scripts\u002F` directory, run `orchestrate_reprice.py` (handles MCP response shapes, account filter, preview, and mutation JSON):\n\n```bash\ncd \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Ftres-asc845-swap-reprice-skill\u002Fscripts\" && \\\npython3 orchestrate_reprice.py \\\n  --input \u002Fpath\u002Fto\u002Fswap_reprice_input.json \\\n  --account-name \"Swaps Clearing Account\" \\\n  --output \u002Fpath\u002Fto\u002Freprice_plan.json \\\n  --mutations-output \u002Fpath\u002Fto\u002Freprice_mutations.json\n```\n\nUse `--account-value` instead of `--account-name` when filtering by ERP account number. Pass `--activity-tags SWAP \"STAKING LOCKUP\"` when the user requested activity filters.\n\nThe script prints a preview to stdout and writes:\n- `reprice_plan.json` — full plan with per-transaction adjustments\n- `reprice_mutations.json` — ready-to-execute `setManualFiatValue` variables\n\nFor lower-level repricing only (no orchestration), use `reprice_swaps.py` directly — see `scripts\u002Freprice_swaps.py` for flags.\n\n### Step 4: Repricing Logic (ASC 845)\n\nThe orchestrator implements the logic below. Read `scripts\u002Freprice_swaps.py` for the canonical implementation.\n\nThe core principle: calculate the **difference** between total outflow fiat and total inflow fiat,\nthen distribute that difference across inflows **in proportion to their token amounts**. This\npreserves the original pricing as a base and makes the minimum adjustment needed.\n\nFor each parent transaction:\n\n**Case 1: One outflow, one inflow**\n```\ninflow.newFiatValue = outflow.fiatValue\n```\n\n**Case 2: One outflow, many inflows**\n```\ndifference = outflow.fiatValue - sum(inflow.fiatValue for each inflow)\ntotalInflowTokens = sum(inflow.amount for each inflow)\nfor each inflow:\n    tokenProportion = inflow.amount \u002F totalInflowTokens\n    inflow.newFiatValue = inflow.fiatValue + (difference * tokenProportion)\n```\n\n**Case 3: Many outflows, one inflow**\n```\ninflow.newFiatValue = sum(outflow.fiatValue for each outflow)\n```\n\n**Case 4: Many outflows, many inflows**\n```\ntotalOutflowFiat = sum(outflow.fiatValue for each outflow)\ntotalInflowFiat = sum(inflow.fiatValue for each inflow)\ndifference = totalOutflowFiat - totalInflowFiat\ntotalInflowTokens = sum(inflow.amount for each inflow)\nfor each inflow:\n    tokenProportion = inflow.amount \u002F totalInflowTokens\n    inflow.newFiatValue = inflow.fiatValue + (difference * tokenProportion)\n```\n\n**Worked example (Case 2):**\n```\nBefore:  Outflow = 100 tokens @ $100 | Inflows = 25 tokens @ $25, 25 @ $25, 35 @ $35 (total $85)\n         Difference = $100 - $85 = $15 | Total inflow tokens = 85\n\nAfter:   Inflow 1: $25 + ($15 × 25\u002F85) = $25 + $4.41 = $29.41\n         Inflow 2: $25 + ($15 × 25\u002F85) = $25 + $4.41 = $29.41\n         Inflow 3: $35 + ($15 × 35\u002F85) = $35 + $6.18 = $41.18\n         Total inflows after = $100.00 ✓  (clearing account nets to zero)\n```\n\n**Edge cases:**\n- If `totalInflowTokens == 0`, distribute the difference equally across inflows\n- If a subtransaction already has `isManualFiatValue == true`, flag it for user review (it was already manually repriced)\n- Skip transactions with only outflows or only inflows (not a complete swap)\n- Last inflow in the group receives the remainder to absorb rounding (ensures exact match)\n\n### Step 5: Preview the Reprice Plan\n\nPresent the orchestrator stdout summary and\u002For the plan JSON to the user:\n\n```\nTX Identifier | Outflow Total | Inflow Before | Inflow After | Adjustment\n------------- | ------------- | ------------- | ------------ | ----------\n0xabc...      | $1,234.56     | $1,230.00     | $1,234.56    | +$4.56\n0xdef...      | $5,678.90     | $5,670.00     | $5,678.90    | +$8.90\n```\n\nAlso show aggregate stats:\n- Total transactions affected\n- Total outflow fiat\n- Total inflow fiat (before)\n- Total inflow fiat (after)\n- Net clearing account residual (before → after, should go to $0)\n- Count of already-manually-priced subtxs being overwritten\n\n### Step 6: Execute (with user confirmation)\n\n**Never run mutations without explicit user confirmation.**\n\nOnly after the user confirms, execute `setManualFiatValue` for each inflow subtransaction (use variables from `reprice_mutations.json`):\n\n```graphql\nmutation SetManualFiatValue($id: ID!, $newFiatValue: String!, $currency: String) {\n  setManualFiatValue(id: $id, newFiatValue: $newFiatValue, currency: $currency) {\n    subTransaction {\n      id\n      fiatValue\n      isManualFiatValue\n    }\n  }\n}\n```\n\nExecute one at a time (not batch) to handle locked-period errors gracefully.\nIf `setBatchManualFiatValue` is preferred for speed, group inflows by asset\nwhere a uniform per-unit price applies.\n\n**Important**: `setManualFiatValue` takes `newFiatValue` as a string.\n`setBatchManualFiatValue` takes `ids` (list) and `newUnitValue` (Float) and computes\n`newUnitValue * amount` — only use this if all subtxs in the batch should have the same unit price.\n\n### Step 7: Verify\n\nRe-query the subtransactions and re-aggregate to confirm the clearing account now nets to zero.\n\n## Error Handling\n\n- **Locked period**: If a subtransaction is in a locked period, warn the user. They must unlock\n  via `deleteLockedPeriod`, apply changes, then re-lock via `createLockedPeriod`.\n- **Missing fiat values**: If outflow fiatValue is null, skip the transaction and flag it.\n- **Zero-value legs**: If outflow total is $0, skip (nothing to propagate).\n- **Already manual**: Flag but still overwrite — only after the user confirmed the batch.\n\n## Script Reference\n\n| Script | Role |\n|--------|------|\n| `scripts\u002Forchestrate_reprice.py` | Primary entry — parse MCP JSON, filter, preview, write plan + mutations |\n| `scripts\u002Freprice_swaps.py` | Core ASC 845 repricing engine (imported by orchestrator; usable standalone) |\n","# ASC 845 Swap Repricing Skill\n\n## Purpose\n\nImplements **equal-value exchange under ASC 845 (Nonmonetary Transactions)** for swap transactions\nin TRES Finance. In a simultaneous swap, the fair value of the asset surrendered (outflow) is the\nbest evidence of the fair value of the asset received (inflow). This skill reprices inflow legs to\nmatch outflow legs so that clearing accounts net to zero.\n\n## When to Use\n\n- A swaps\u002Ftrade clearing account has a non-zero residual after month-end\n- User wants to apply ASC 845 to a population of swap transactions\n- User says \"setBatchUseCounterpartyFiatValue\" or similar\n\n## MCP Server\n\nAll GraphQL calls use the **`user-tres-finance`** MCP server (`execute` tool).\n\nVariable keys and nested input fields MUST use **camelCase** (e.g. `timestamp_Gte`, not `timestamp_gte`).\n\n## Prerequisites\n\n- TRES Finance MCP connection (`user-tres-finance`)\n- The user must specify:\n  1. **Target ERP account** — the clearing account to zero out (e.g. \"Swaps Clearing Account\", NS #818)\n  2. **Transaction scope** — either a date range (timestamp_Gte \u002F timestamp_Lte) or specific tx hashes\n  3. **Confirmation** — user must approve before mutations are executed\n\n## Workflow\n\n### Step 1: Gather Parameters\n\nAsk the user for:\n- Target ERP account name or ID (the clearing account)\n- Date range OR list of transaction hashes\n- **Activity tags** (optional) — filter to only transactions with specific classification activities\n  (e.g. \"STAKING LOCKUP\", \"SWAP\"). None, one, or many may be selected. If omitted, all activities\n  are included. Use `tx_Classification_Activity_In` on the TRES query.\n- Currency (default: USD)\n- Whether to run in **dry-run** (preview only) or **execute** mode\n\n### Step 2: Query Subtransactions\n\nUse the TRES `subTransaction` query to fetch all subtransactions in scope. Include these fields:\n```graphql\n{\n  id\n  amount\n  balanceFactor\n  timestamp\n  fiatValue\n  isManualFiatValue\n  belongsTo { id name }\n  asset { assetClass { symbol } }\n  tx { id identifier classification { activity } }\n  flowRule {\n    ruleName\n    integrationAccount { name value }\n  }\n}\n```\n\nIf activity tags were specified, pass them as `tx_Classification_Activity_In: [\"STAKING LOCKUP\", \"SWAP\"]`\non the query. Note: transactions with `classification: null` will be excluded when this filter is used,\nso only apply it when the user explicitly requests it.\n\nPaginate in batches of 50 (to avoid timeouts). Save the combined results to a JSON file for the orchestrator script.\n\n### Step 3: Run the Orchestrator Script\n\nFrom the skill `scripts\u002F` directory, run `orchestrate_reprice.py` (handles MCP response shapes, account filter, preview, and mutation JSON):\n\n```bash\ncd \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Ftres-asc845-swap-reprice-skill\u002Fscripts\" && \\\npython3 orchestrate_reprice.py \\\n  --input \u002Fpath\u002Fto\u002Fswap_reprice_input.json \\\n  --account-name \"Swaps Clearing Account\" \\\n  --output \u002Fpath\u002Fto\u002Freprice_plan.json \\\n  --mutations-output \u002Fpath\u002Fto\u002Freprice_mutations.json\n```\n\nUse `--account-value` instead of `--account-name` when filtering by ERP account number. Pass `--activity-tags SWAP \"STAKING LOCKUP\"` when the user requested activity filters.\n\nThe script prints a preview to stdout and writes:\n- `reprice_plan.json` — full plan with per-transaction adjustments\n- `reprice_mutations.json` — ready-to-execute `setManualFiatValue` variables\n\nFor lower-level repricing only (no orchestration), use `reprice_swaps.py` directly — see `scripts\u002Freprice_swaps.py` for flags.\n\n### Step 4: Repricing Logic (ASC 845)\n\nThe orchestrator implements the logic below. Read `scripts\u002Freprice_swaps.py` for the canonical implementation.\n\nThe core principle: calculate the **difference** between total outflow fiat and total inflow fiat,\nthen distribute that difference across inflows **in proportion to their token amounts**. This\npreserves the original pricing as a base and makes the minimum adjustment needed.\n\nFor each parent transaction:\n\n**Case 1: One outflow, one inflow**\n```\ninflow.newFiatValue = outflow.fiatValue\n```\n\n**Case 2: One outflow, many inflows**\n```\ndifference = outflow.fiatValue - sum(inflow.fiatValue for each inflow)\ntotalInflowTokens = sum(inflow.amount for each inflow)\nfor each inflow:\n    tokenProportion = inflow.amount \u002F totalInflowTokens\n    inflow.newFiatValue = inflow.fiatValue + (difference * tokenProportion)\n```\n\n**Case 3: Many outflows, one inflow**\n```\ninflow.newFiatValue = sum(outflow.fiatValue for each outflow)\n```\n\n**Case 4: Many outflows, many inflows**\n```\ntotalOutflowFiat = sum(outflow.fiatValue for each outflow)\ntotalInflowFiat = sum(inflow.fiatValue for each inflow)\ndifference = totalOutflowFiat - totalInflowFiat\ntotalInflowTokens = sum(inflow.amount for each inflow)\nfor each inflow:\n    tokenProportion = inflow.amount \u002F totalInflowTokens\n    inflow.newFiatValue = inflow.fiatValue + (difference * tokenProportion)\n```\n\n**Worked example (Case 2):**\n```\nBefore:  Outflow = 100 tokens @ $100 | Inflows = 25 tokens @ $25, 25 @ $25, 35 @ $35 (total $85)\n         Difference = $100 - $85 = $15 | Total inflow tokens = 85\n\nAfter:   Inflow 1: $25 + ($15 × 25\u002F85) = $25 + $4.41 = $29.41\n         Inflow 2: $25 + ($15 × 25\u002F85) = $25 + $4.41 = $29.41\n         Inflow 3: $35 + ($15 × 35\u002F85) = $35 + $6.18 = $41.18\n         Total inflows after = $100.00 ✓  (clearing account nets to zero)\n```\n\n**Edge cases:**\n- If `totalInflowTokens == 0`, distribute the difference equally across inflows\n- If a subtransaction already has `isManualFiatValue == true`, flag it for user review (it was already manually repriced)\n- Skip transactions with only outflows or only inflows (not a complete swap)\n- Last inflow in the group receives the remainder to absorb rounding (ensures exact match)\n\n### Step 5: Preview the Reprice Plan\n\nPresent the orchestrator stdout summary and\u002For the plan JSON to the user:\n\n```\nTX Identifier | Outflow Total | Inflow Before | Inflow After | Adjustment\n------------- | ------------- | ------------- | ------------ | ----------\n0xabc...      | $1,234.56     | $1,230.00     | $1,234.56    | +$4.56\n0xdef...      | $5,678.90     | $5,670.00     | $5,678.90    | +$8.90\n```\n\nAlso show aggregate stats:\n- Total transactions affected\n- Total outflow fiat\n- Total inflow fiat (before)\n- Total inflow fiat (after)\n- Net clearing account residual (before → after, should go to $0)\n- Count of already-manually-priced subtxs being overwritten\n\n### Step 6: Execute (with user confirmation)\n\n**Never run mutations without explicit user confirmation.**\n\nOnly after the user confirms, execute `setManualFiatValue` for each inflow subtransaction (use variables from `reprice_mutations.json`):\n\n```graphql\nmutation SetManualFiatValue($id: ID!, $newFiatValue: String!, $currency: String) {\n  setManualFiatValue(id: $id, newFiatValue: $newFiatValue, currency: $currency) {\n    subTransaction {\n      id\n      fiatValue\n      isManualFiatValue\n    }\n  }\n}\n```\n\nExecute one at a time (not batch) to handle locked-period errors gracefully.\nIf `setBatchManualFiatValue` is preferred for speed, group inflows by asset\nwhere a uniform per-unit price applies.\n\n**Important**: `setManualFiatValue` takes `newFiatValue` as a string.\n`setBatchManualFiatValue` takes `ids` (list) and `newUnitValue` (Float) and computes\n`newUnitValue * amount` — only use this if all subtxs in the batch should have the same unit price.\n\n### Step 7: Verify\n\nRe-query the subtransactions and re-aggregate to confirm the clearing account now nets to zero.\n\n## Error Handling\n\n- **Locked period**: If a subtransaction is in a locked period, warn the user. They must unlock\n  via `deleteLockedPeriod`, apply changes, then re-lock via `createLockedPeriod`.\n- **Missing fiat values**: If outflow fiatValue is null, skip the transaction and flag it.\n- **Zero-value legs**: If outflow total is $0, skip (nothing to propagate).\n- **Already manual**: Flag but still overwrite — only after the user confirmed the batch.\n\n## Script Reference\n\n| Script | Role |\n|--------|------|\n| `scripts\u002Forchestrate_reprice.py` | Primary entry — parse MCP JSON, filter, preview, write plan + mutations |\n| `scripts\u002Freprice_swaps.py` | Core ASC 845 repricing engine (imported by orchestrator; usable standalone) |\n",{"name":5,"description":49,"compatibility":50},"Reprice swap transaction legs under ASC 845 (Nonmonetary Transactions) to ensure clearing accounts net to zero. Use this skill whenever the user wants to: reprice swaps, fix clearing account residuals, apply equal-value exchange to swap legs, run setBatchUseCounterpartyFiatValue, zero out a clearing account, apply ASC 845, fix swap pricing mismatches, ensure no gain\u002Floss on swaps, or close a month where a swaps\u002Ftrade clearing account has a residual balance. Also trigger when the user mentions \"counterparty fiat value\", \"swap repricing\", \"clearing account net to zero\", or \"equal value exchange\".\n","Requires TRES Finance MCP connector","main","163301d1904c0a994539f5226ce0fcd65b8652bf","tres-finance-plugin\u002Fskills\u002Ftres-asc845-swap-reprice-skill",363,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-12 15:56:31",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add anthropics\u002Fclaude-plugins-community --skill tres-asc845-swap-reprice-skill",{"tool":65,"command":66},"bunx","bunx skills add anthropics\u002Fclaude-plugins-community --skill tres-asc845-swap-reprice-skill",{"tool":68,"command":69},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-plugins-community --skill tres-asc845-swap-reprice-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-asc845-swap-reprice-skill\u002FSKILL.md",true,[73,79],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Forchestrate_reprice.py","SCRIPT","脚本",6254,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-asc845-swap-reprice-skill\u002Fscripts\u002Forchestrate_reprice.py",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Freprice_swaps.py",19407,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-asc845-swap-reprice-skill\u002Fscripts\u002Freprice_swaps.py",[84,119,141,165,189,211],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":99,"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",[90,93,94],{"categoryNo":91,"categoryName":92,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[100,101,102,103,104,105,106,107,108,109,35,110,111,112,113,114,115,116,117,118],"wallets","tres wallets upload","upload","typing","ingestion","Wallet","chain","creation","xlsx","selection","confirmation","connect","collection","preview","api","batch","guides","on-chain","request",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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",[],[126,102,127,128,129,130,105,131,132,133,38,37,134,135,136,34,137,138,139,140],"tres upload tx header validation","validation","bulk","do","import","parsing","for","manual","missing","general","only","workflow","csv","contacts","with",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"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",[147],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[149,150,151,152,153,35,33,154,155,156,157,158,159,160,161,162,163,129,164,132],"tres tx story","Story","show","memory","hex","show me","analysis","analyze","me","diagram","generate","flow","asset","blockchain","STRING","visualize",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"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",[171],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[173,174,175,176,151,177,35,33,178,179,180,114,181,182,183,184,185,186,187,188],"tres settings management","settings","management","SET","get","configure","ask","commit","change","organization","update","read","write","sync","mcp graphql","flags",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":197,"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",[195,196],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},[198,199,200,151,201,105,202,35,203,204,31,205,206,156,207,29,208,209,182,210],"tres rollup rules","Rules","rollup","gas","up","impact","reduce","review","consolidate","create","delete","data-driven","activity",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":219,"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",[217,218],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},[205,220,200,221,222,223,224,225,136,226,35,203,33,113,227,31,228,229,207,230],"tres rollup review","standalone","never","mode","issues","design","new","candidate","filter","valid","catch"]