[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718EAPY3HH8Q7XS7KVR44BC":3,"skill-same:01M718EAPY3HH8Q7XS7KVR44BC":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},"01M718EAPY3HH8Q7XS7KVR44BC","tres-ledger-link",null,"Build a TRES Finance dashboard ledger URL (Transactions tab) with a precise filter set — date range, wallets, assets, tags, status, amount, and more — so it can be shared with a customer or reused. Use whenever the user asks for a \"ledger link\", \"dashboard link\", \"filter URL\", or \"send \u003Ccustomer> a link to \u003Csome filtered view>\". Scoped to the Transactions tab only (not Accounting, Roll Forward, Pivot Tables, Cost Basis, or Trial Balances).","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-ledger-link\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"link","ledger","tres ledger link","scoped","for","filtered","view","tables","wallets","status","customer","dashboard","transactions","filter","URL","only","send","balances","SET","shared","2026-11-10 10:12:30",false,"---\nname: tres-ledger-link\ndescription: >\n  Build a TRES Finance dashboard ledger URL (Transactions tab) with a precise filter set — date\n  range, wallets, assets, tags, status, amount, and more — so it can be shared with a customer or\n  reused. Use whenever the user asks for a \"ledger link\", \"dashboard link\", \"filter URL\", or \"send\n  \u003Ccustomer> a link to \u003Csome filtered view>\". Scoped to the Transactions tab only (not Accounting,\n  Roll Forward, Pivot Tables, Cost Basis, or Trial Balances).\n---\n\n# Generate Dashboard Ledger Link\n\nYour job is to produce a working TRES Finance dashboard URL that opens the **Transactions tab of the\nledger** with a precise filter set applied, so the user can share it with a customer (or use it\nthemselves).\n\nThis skill is scoped to the **Transactions tab only**. If the user asks for a link to Accounting,\nRoll Forward, Pivot Tables, Cost Basis, or Trial Balances — stop and tell them this skill does not\ncover those tabs.\n\n---\n\n## Step 1 — Resolve the org subdomain\n\nThe dashboard URL is `https:\u002F\u002F\u003Corg-subdomain>.tres.finance\u002Fledger`.\n\nResolve `\u003Corg-subdomain>` from the MCP `get_viewer` query (use the returned `orgName`). **Do not ask\nthe user.**\n\n```graphql\nquery { viewer { orgName } }\n```\n\nState the subdomain you used in your final message so the user can correct it in one shot if it is\nwrong.\n\n---\n\n## Step 2 — Collect the filters the user wants\n\nRead the filters out of the user's request in plain English (date range, wallets, assets, tags,\nstatus, etc.). If a filter is ambiguous (e.g. \"USDC\" when the org has multiple USDC variants, or \"Q1\"\nwithout a year), ask before generating. A wrong value silently produces a broken \u002F empty view.\n\nOnly include filters the user explicitly asked for. The dashboard fills in defaults for everything\nelse — extra params just add noise.\n\n---\n\n## Step 3 — Build the URL\n\nBase path is always:\n\n```\nhttps:\u002F\u002F\u003Corg-subdomain>.tres.finance\u002Fledger\n```\n\nNo path segment after `\u002Fledger` (that is the Transactions tab).\n\nAppend `?` and the query string built from the rules below. URL-encode every value (spaces → `%20`).\nInside a single value, encode commas; between distinct array items, a comma is the literal delimiter.\n\n### 3.1 Date & pagination\n\n| Param      | Format \u002F values | Notes |\n|------------|-----------------|-------|\n| `fromDate` | `YYYY-MM-DD` | UTC date |\n| `toDate`   | `YYYY-MM-DD` | UTC date |\n| `dateType` | `Month to date`, `Year to date`, `Last 30 days`, `Last month`, `Before this month`, `Custom date`, `All time`, `Year`, `Quarters` | URL-encode spaces. **Omit** if `Last 30 days` (default). For an arbitrary `fromDate`\u002F`toDate` range, use `Custom date`. |\n| `page`     | integer | Omit if `1`. |\n| `pageSize` | integer | Omit if `20` (default). |\n\nIf `dateType=All%20time`, `fromDate` \u002F `toDate` are ignored — do not include them.\n\n### 3.2 Multi-select array filters (comma-joined IDs)\n\n| Param | What goes in it |\n|-------|-----------------|\n| `internalAccounts` | numeric database ID of org-owned wallets |\n| `tags` | wallet group IDs, or `no-label` for unlabeled |\n| `thirdPartyAccounts` | raw address string of an external account (sender\u002Freceiver identifier on a sub-transaction — not necessarily a named contact in the system) |\n| `customNameLabelTags` | contact group IDs |\n| `addresses` | raw unidentified address strings |\n| `assetClasses` | asset class enum IDs (e.g. `CRYPTO`, `FIAT`, `NFT`) |\n| `assets` | asset IDs |\n| `activities` | tag IDs uppercase (e.g. `SPAM`, `STAKING`), or `no-label` |\n| `automations` | automation IDs |\n| `platforms` | platform names **lowercased** (e.g. `ethereum`, `bitcoin` — NOT the uppercase enum) |\n| `actions` | financial action enum names (e.g. `SEND`, `RECEIVE`) |\n| `functions` | decoded function names |\n| `applications` | application IDs |\n| `protocols` | protocol IDs |\n| `methodIds` | 4-byte hex method IDs (`0xa9059cbb`) |\n| `transactionHash` | tx hash(es) |\n| `transactionView` | `readyPending` (default), `onlyReady`, `onlyPending`, `onlyDeleted` |\n| `transactionType` | any of `isManual`, `onlyPlug` |\n| `filterByBookmark` | bookmark types **lowercased** |\n| `missingCounterMatchedTransfers` | `all` (default), `false` (has counter transfer), `true` (no counter transfer) |\n| `balanceFactor` | `1` (Inflow), `-1` (Outflow). Typically a single value. |\n| `amountAsset` | single asset ID (pair with `amountBetween`) |\n\nIf you do not know the exact ID for a multi-select value, query the BFF via the `execute` MCP tool\nfirst to look it up. Do **not** guess.\n\n### 3.3 Range filter\n\n| Param | Format | Notes |\n|-------|--------|-------|\n| `amountBetween` | `\u003Cmin>,\u003Cmax>` | Either side may be empty: `100,500` (range), `100,` (≥100), `,500` (≤500). The single comma is required. |\n\n### 3.4 Boolean filters (include only when `true`)\n\n`showSpam`, `missingFiat`, `failedTransactions`, `nonTaxableType`, `missingCostBasis`,\n`internalTransactions`, `ignoreFee`\n\nExample: `?showSpam=true&missingFiat=true`. Never emit `=false` — `false` is the default.\n\n### 3.5 Notes \u002F radio-with-input\n\n| Param | Values |\n|-------|--------|\n| `commentContains` | `1` = has notes, `-1` = no notes, `0` = show all (omit), or any text string to search note content |\n\n### 3.6 Other singles\n\n| Param | Format |\n|-------|--------|\n| `savedFilters` | saved-filter ID (single value) |\n| `description` | single string |\n| `globalSearch` | single string |\n\n---\n\n## Step 4 — Validate before sending\n\nWalk the URL through this checklist. If any rule fails, fix it before handing it over.\n\n1. Path is exactly `\u002Fledger`. No tab suffix, no `?id=...`.\n2. `fromDate` \u002F `toDate` paired with `dateType=Custom%20date` (or `dateType` omitted), never with\n   `Last%2030%20days` or `All%20time`.\n3. No `=false` on any boolean.\n4. Multi-select values are **comma-joined**, never repeated keys (`?platforms=ethereum,bsc`, never\n   `?platforms=ethereum&platforms=bsc`).\n5. `platforms` values are **lowercased** (`ethereum`, not `ETHEREUM`). All other enum IDs match the\n   schema (`SPAM`, not `Spam`; `CRYPTO`, not `crypto`).\n6. `amountBetween` always has exactly one comma, even when one side is open.\n7. If `activities` includes `SPAM`, also set `showSpam=true` so the link is self-contained.\n8. If `transactionHash` is set, the dashboard ignores any date filter — warn the user when you also\n   see a date in their request.\n9. Spaces are URL-encoded (`Custom date` → `Custom%20date`).\n10. Only filters the user asked for are included.\n\n---\n\n## Step 5 — Hand it over\n\nSend the URL on its own line so it is easy to copy. Briefly state which filters are encoded (and which\nsubdomain you used) so the user can sanity-check before forwarding to the customer.\n\nExample handoff:\n\n> Built for org `\u003Csubdomain>`: filters are platform=ethereum, activities=SPAM, fromDate\u002FtoDate Apr\n> 2026 (Custom date), showSpam=true.\n>\n> https:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?fromDate=2026-04-01&toDate=2026-04-30&dateType=Custom%20date&platforms=ethereum&activities=SPAM&showSpam=true\n\n---\n\n## Worked examples\n\n**Last month's Ethereum SPAM transactions:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?fromDate=2026-04-01&toDate=2026-04-30&dateType=Custom%20date&platforms=ethereum&activities=SPAM&showSpam=true\n```\n\n**All-time view of two specific wallets:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?dateType=All%20time&internalAccounts=12345,67890\n```\n\n**USD-only large transfers ≥ 50k:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?assetClasses=FIAT&amountBetween=50000,&amountAsset=USD\n```\n\n**Failed transactions missing fiat in Q1 2026:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?fromDate=2026-01-01&toDate=2026-03-31&dateType=Custom%20date&failedTransactions=true&missingFiat=true\n```\n\n**A specific saved filter:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?savedFilters=12345\n```\n\n---\n\n## Rules\n\n- **This skill is for general, ad-hoc filtered views** the user describes in plain English. To pin a\n  single just-created transaction so a pending\u002Fbackdated row shows immediately, set `transactionHash`\n  with `dateType=All%20time`.\n- **Never hand-craft a ledger URL outside this skill** — use it whenever the user asks for a ledger \u002F\n  dashboard \u002F filter link.\n- **Never include `=false`** on a boolean filter.\n- **Never repeat a key** (`?x=a&x=b`) — comma-join into one value.\n- **Never use display names** where the dashboard expects enum IDs.\n- **Always validate** against the Step 4 checklist before responding.\n- **Always state** the subdomain and filters used in your handoff message.\n","# Generate Dashboard Ledger Link\n\nYour job is to produce a working TRES Finance dashboard URL that opens the **Transactions tab of the\nledger** with a precise filter set applied, so the user can share it with a customer (or use it\nthemselves).\n\nThis skill is scoped to the **Transactions tab only**. If the user asks for a link to Accounting,\nRoll Forward, Pivot Tables, Cost Basis, or Trial Balances — stop and tell them this skill does not\ncover those tabs.\n\n---\n\n## Step 1 — Resolve the org subdomain\n\nThe dashboard URL is `https:\u002F\u002F\u003Corg-subdomain>.tres.finance\u002Fledger`.\n\nResolve `\u003Corg-subdomain>` from the MCP `get_viewer` query (use the returned `orgName`). **Do not ask\nthe user.**\n\n```graphql\nquery { viewer { orgName } }\n```\n\nState the subdomain you used in your final message so the user can correct it in one shot if it is\nwrong.\n\n---\n\n## Step 2 — Collect the filters the user wants\n\nRead the filters out of the user's request in plain English (date range, wallets, assets, tags,\nstatus, etc.). If a filter is ambiguous (e.g. \"USDC\" when the org has multiple USDC variants, or \"Q1\"\nwithout a year), ask before generating. A wrong value silently produces a broken \u002F empty view.\n\nOnly include filters the user explicitly asked for. The dashboard fills in defaults for everything\nelse — extra params just add noise.\n\n---\n\n## Step 3 — Build the URL\n\nBase path is always:\n\n```\nhttps:\u002F\u002F\u003Corg-subdomain>.tres.finance\u002Fledger\n```\n\nNo path segment after `\u002Fledger` (that is the Transactions tab).\n\nAppend `?` and the query string built from the rules below. URL-encode every value (spaces → `%20`).\nInside a single value, encode commas; between distinct array items, a comma is the literal delimiter.\n\n### 3.1 Date & pagination\n\n| Param      | Format \u002F values | Notes |\n|------------|-----------------|-------|\n| `fromDate` | `YYYY-MM-DD` | UTC date |\n| `toDate`   | `YYYY-MM-DD` | UTC date |\n| `dateType` | `Month to date`, `Year to date`, `Last 30 days`, `Last month`, `Before this month`, `Custom date`, `All time`, `Year`, `Quarters` | URL-encode spaces. **Omit** if `Last 30 days` (default). For an arbitrary `fromDate`\u002F`toDate` range, use `Custom date`. |\n| `page`     | integer | Omit if `1`. |\n| `pageSize` | integer | Omit if `20` (default). |\n\nIf `dateType=All%20time`, `fromDate` \u002F `toDate` are ignored — do not include them.\n\n### 3.2 Multi-select array filters (comma-joined IDs)\n\n| Param | What goes in it |\n|-------|-----------------|\n| `internalAccounts` | numeric database ID of org-owned wallets |\n| `tags` | wallet group IDs, or `no-label` for unlabeled |\n| `thirdPartyAccounts` | raw address string of an external account (sender\u002Freceiver identifier on a sub-transaction — not necessarily a named contact in the system) |\n| `customNameLabelTags` | contact group IDs |\n| `addresses` | raw unidentified address strings |\n| `assetClasses` | asset class enum IDs (e.g. `CRYPTO`, `FIAT`, `NFT`) |\n| `assets` | asset IDs |\n| `activities` | tag IDs uppercase (e.g. `SPAM`, `STAKING`), or `no-label` |\n| `automations` | automation IDs |\n| `platforms` | platform names **lowercased** (e.g. `ethereum`, `bitcoin` — NOT the uppercase enum) |\n| `actions` | financial action enum names (e.g. `SEND`, `RECEIVE`) |\n| `functions` | decoded function names |\n| `applications` | application IDs |\n| `protocols` | protocol IDs |\n| `methodIds` | 4-byte hex method IDs (`0xa9059cbb`) |\n| `transactionHash` | tx hash(es) |\n| `transactionView` | `readyPending` (default), `onlyReady`, `onlyPending`, `onlyDeleted` |\n| `transactionType` | any of `isManual`, `onlyPlug` |\n| `filterByBookmark` | bookmark types **lowercased** |\n| `missingCounterMatchedTransfers` | `all` (default), `false` (has counter transfer), `true` (no counter transfer) |\n| `balanceFactor` | `1` (Inflow), `-1` (Outflow). Typically a single value. |\n| `amountAsset` | single asset ID (pair with `amountBetween`) |\n\nIf you do not know the exact ID for a multi-select value, query the BFF via the `execute` MCP tool\nfirst to look it up. Do **not** guess.\n\n### 3.3 Range filter\n\n| Param | Format | Notes |\n|-------|--------|-------|\n| `amountBetween` | `\u003Cmin>,\u003Cmax>` | Either side may be empty: `100,500` (range), `100,` (≥100), `,500` (≤500). The single comma is required. |\n\n### 3.4 Boolean filters (include only when `true`)\n\n`showSpam`, `missingFiat`, `failedTransactions`, `nonTaxableType`, `missingCostBasis`,\n`internalTransactions`, `ignoreFee`\n\nExample: `?showSpam=true&missingFiat=true`. Never emit `=false` — `false` is the default.\n\n### 3.5 Notes \u002F radio-with-input\n\n| Param | Values |\n|-------|--------|\n| `commentContains` | `1` = has notes, `-1` = no notes, `0` = show all (omit), or any text string to search note content |\n\n### 3.6 Other singles\n\n| Param | Format |\n|-------|--------|\n| `savedFilters` | saved-filter ID (single value) |\n| `description` | single string |\n| `globalSearch` | single string |\n\n---\n\n## Step 4 — Validate before sending\n\nWalk the URL through this checklist. If any rule fails, fix it before handing it over.\n\n1. Path is exactly `\u002Fledger`. No tab suffix, no `?id=...`.\n2. `fromDate` \u002F `toDate` paired with `dateType=Custom%20date` (or `dateType` omitted), never with\n   `Last%2030%20days` or `All%20time`.\n3. No `=false` on any boolean.\n4. Multi-select values are **comma-joined**, never repeated keys (`?platforms=ethereum,bsc`, never\n   `?platforms=ethereum&platforms=bsc`).\n5. `platforms` values are **lowercased** (`ethereum`, not `ETHEREUM`). All other enum IDs match the\n   schema (`SPAM`, not `Spam`; `CRYPTO`, not `crypto`).\n6. `amountBetween` always has exactly one comma, even when one side is open.\n7. If `activities` includes `SPAM`, also set `showSpam=true` so the link is self-contained.\n8. If `transactionHash` is set, the dashboard ignores any date filter — warn the user when you also\n   see a date in their request.\n9. Spaces are URL-encoded (`Custom date` → `Custom%20date`).\n10. Only filters the user asked for are included.\n\n---\n\n## Step 5 — Hand it over\n\nSend the URL on its own line so it is easy to copy. Briefly state which filters are encoded (and which\nsubdomain you used) so the user can sanity-check before forwarding to the customer.\n\nExample handoff:\n\n> Built for org `\u003Csubdomain>`: filters are platform=ethereum, activities=SPAM, fromDate\u002FtoDate Apr\n> 2026 (Custom date), showSpam=true.\n>\n> https:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?fromDate=2026-04-01&toDate=2026-04-30&dateType=Custom%20date&platforms=ethereum&activities=SPAM&showSpam=true\n\n---\n\n## Worked examples\n\n**Last month's Ethereum SPAM transactions:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?fromDate=2026-04-01&toDate=2026-04-30&dateType=Custom%20date&platforms=ethereum&activities=SPAM&showSpam=true\n```\n\n**All-time view of two specific wallets:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?dateType=All%20time&internalAccounts=12345,67890\n```\n\n**USD-only large transfers ≥ 50k:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?assetClasses=FIAT&amountBetween=50000,&amountAsset=USD\n```\n\n**Failed transactions missing fiat in Q1 2026:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?fromDate=2026-01-01&toDate=2026-03-31&dateType=Custom%20date&failedTransactions=true&missingFiat=true\n```\n\n**A specific saved filter:**\n\n```\nhttps:\u002F\u002F\u003Csubdomain>.tres.finance\u002Fledger?savedFilters=12345\n```\n\n---\n\n## Rules\n\n- **This skill is for general, ad-hoc filtered views** the user describes in plain English. To pin a\n  single just-created transaction so a pending\u002Fbackdated row shows immediately, set `transactionHash`\n  with `dateType=All%20time`.\n- **Never hand-craft a ledger URL outside this skill** — use it whenever the user asks for a ledger \u002F\n  dashboard \u002F filter link.\n- **Never include `=false`** on a boolean filter.\n- **Never repeat a key** (`?x=a&x=b`) — comma-join into one value.\n- **Never use display names** where the dashboard expects enum IDs.\n- **Always validate** against the Step 4 checklist before responding.\n- **Always state** the subdomain and filters used in your handoff message.\n",{"name":5,"description":7},"main","163301d1904c0a994539f5226ce0fcd65b8652bf","tres-finance-plugin\u002Fskills\u002Ftres-ledger-link",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-ledger-link",{"tool":63,"command":64},"bunx","bunx skills add anthropics\u002Fclaude-plugins-community --skill tres-ledger-link",{"tool":66,"command":67},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-plugins-community --skill tres-ledger-link","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-community\u002Fblob\u002Fmain\u002Ftres-finance-plugin\u002Fskills\u002Ftres-ledger-link\u002FSKILL.md",true,[],[72,107,130,155,178,201],{"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,83,86],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[32,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"tres wallets upload","upload","typing","ingestion","Wallet","chain","creation","xlsx","selection","MCP","confirmation","connect","collection","preview","api","batch","guides","on-chain","request",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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",[],[114,89,115,116,117,118,92,119,28,120,121,122,123,124,39,125,126,127,128,129],"tres upload tx header validation","validation","bulk","do","import","parsing","manual","trigger","fix","missing","general","use","workflow","csv","contacts","with",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"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",[136],{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},[138,139,140,141,142,97,143,144,145,146,147,148,149,150,151,152,153,117,154,28],"tres tx story","Story","show","memory","hex","when","show me","analysis","analyze","me","diagram","generate","flow","asset","blockchain","STRING","visualize",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"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",[161],{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},[163,164,165,42,140,166,97,143,167,168,169,102,170,171,172,173,174,175,176,177],"tres settings management","settings","management","get","configure","ask","commit","change","organization","update","read","write","sync","mcp graphql","flags",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":186,"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",[184,185],{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[187,188,189,140,190,92,191,97,192,193,194,195,196,146,197,36,198,199,171,200],"tres rollup rules","Rules","rollup","gas","up","impact","reduce","Connector","review","consolidate","create","delete","data-driven","activity",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":209,"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",[207,208],{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[195,210,189,211,212,213,214,215,39,216,97,192,143,101,217,194,37,218,197,219],"tres rollup review","standalone","never","mode","issues","design","new","candidate","valid","catch"]