tres-ledger-link — Claude Code skill: build TRES ledger links
tres-ledger-link turns a plain-language request into a shareable TRES Finance ledger URL with the filters already applied.
MIT ★ 4,931 updated 2026-10-24
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tres-finance-plugin@claude-communityWhat tres-ledger-link does
Ask in plain words and you get back a link to the Transactions tab of your TRES Finance ledger. Dates, wallets, assets, tags, status and amounts land in the query string, so whoever opens the URL sees the same filtered view.
The subdomain is resolved through an MCP query (viewer { orgName }) instead of a question to you. Values that need database IDs are fetched with the execute MCP tool; nothing is guessed. Ambiguous input, like several USDC variants or a quarter with no year, gets a follow-up before the URL is built. Then the pieces are assembled by rule: comma-joined arrays, lowercase platforms, dateType=Custom%20date whenever fromDate and toDate appear, one comma inside amountBetween.
A validation pass runs before handoff, so =false flags and repeated keys do not survive. None of this works without the TRES MCP tools attached, because there is no org name to resolve. It covers the Transactions tab only; Accounting, Roll Forward, Pivot Tables, Cost Basis and Trial Balances are out.
What it helps with
- build a filtered ledger link to send a customer
- encode a date range as
fromDate/toDatewithdateType=Custom%20date - join several platforms into a single
platformsvalue - express an open-ended amount range in
amountBetween - check the URL against the rules before sending
Example prompts for the agent
- Build a ledger link for April 2026, ethereum only, staking activity
- Make a filter URL for the wallet group
no-labelwith amounts above 100 - Send the customer a link to these transactions with spam hidden
How to install tres-ledger-link
1Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install tres-finance-plugin@claude-communityThis installs the whole tres-finance-plugin plugin with all its skills
2Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill tres-ledger-link -a claude-code3Manually: put the files in place
~/.claude/skills/tres-ledger-link/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/tres-ledger-link/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill tres-ledger-link -a codex2Manually: put the files in place
.agents/skills/tres-ledger-link/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill tres-ledger-link -a cursor2Manually: put the files in place
.cursor/skills/tres-ledger-link/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/claude-plugins-community tres-finance-plugin/skills/tres-ledger-link2Manually: put the files in place
.github/skills/tres-ledger-link/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill tres-ledger-link -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/claude-plugins-community --path tres-finance-plugin/skills/tres-ledger-linkManually: put the files in place
.devin/skills/tres-ledger-link/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about tres-ledger-link
How do I install tres-ledger-link in Claude Code?
Through the plugin marketplace: run /plugin marketplace add anthropics/claude-plugins-community, then /plugin install tres-finance-plugin@claude-community. The skill ships inside the tres-finance-plugin plugin.
What does tres-ledger-link do?
It builds a URL for the Transactions tab of a TRES Finance dashboard with the requested filters in the query string: dates, wallets, assets, tags, status, amount. You can forward that link to a customer or keep it for later.
Which TRES Finance tabs are out of scope?
Accounting, Roll Forward, Pivot Tables, Cost Basis and Trial Balances. The skill handles the Transactions tab alone and stops when asked for anything else.
Source text
SKILL.md · MIT
---
name: tres-ledger-link
description: >
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
<customer> a link to <some filtered view>". Scoped to the Transactions tab only (not Accounting,
Roll Forward, Pivot Tables, Cost Basis, or Trial Balances).
---
# Generate Dashboard Ledger Link
Your job is to produce a working TRES Finance dashboard URL that opens the **Transactions tab of the
ledger** with a precise filter set applied, so the user can share it with a customer (or use it
themselves).
This skill is scoped to the **Transactions tab only**. If the user asks for a link to Accounting,
Roll Forward, Pivot Tables, Cost Basis, or Trial Balances — stop and tell them this skill does not
cover those tabs.
---
## Step 1 — Resolve the org subdomain
The dashboard URL is `https://<org-subdomain>.tres.finance/ledger`.
Resolve `<org-subdomain>` from the MCP `get_viewer` query (use the returned `orgName`). **Do not ask
the user.**
```graphql
query { viewer { orgName } }
```
State the subdomain you used in your final message so the user can correct it in one shot if it is
wrong.
---
## Step 2 — Collect the filters the user wants
Read the filters out of the user's request in plain English (date range, wallets, assets, tags,
status, etc.). If a filter is ambiguous (e.g. "USDC" when the org has multiple USDC variants, or "Q1"
without a year), ask before generating. A wrong value silently produces a broken / empty view.
Only include filters the user explicitly asked for. The dashboard fills in defaults for everything
else — extra params just add noise.
---
## Step 3 — Build the URL
Base path is always:
```
https://<org-subdomain>.tres.finance/ledger
```
No path segment after `/ledger` (that is the Transactions tab).
Append `?` and the query string built from the rules below. URL-encode every value (spaces → `%20`).
Inside a single value, encode commas; between distinct array items, a comma is the literal delimiter.
### 3.1 Date & pagination
| Param | Format / values | Notes |
|------------|-----------------|-------|
| `fromDate` | `YYYY-MM-DD` | UTC date |
| `toDate` | `YYYY-MM-DD` | UTC date |
| `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`/`toDate` range, use `Custom date`. |
| `page` | integer | Omit if `1`. |
| `pageSize` | integer | Omit if `20` (default). |
If `dateType=All%20time`, `fromDate` / `toDate` are ignored — do not include them.
### 3.2 Multi-select array filters (comma-joined IDs)
| Param | What goes in it |
|-------|-----------------|
| `internalAccounts` | numeric database ID of org-owned wallets |
| `tags` | wallet group IDs, or `no-label` for unlabeled |
| `thirdPartyAccounts` | raw address string of an external account (sender/receiver identifier on a sub-transaction — not necessarily a named contact in the system) |
| `customNameLabelTags` | contact group IDs |
| `addresses` | raw unidentified address strings |
| `assetClasses` | asset class enum IDs (e.g. `CRYPTO`, `FIAT`, `NFT`) |
| `assets` | asset IDs |
| `activities` | tag IDs uppercase (e.g. `SPAM`, `STAKING`), or `no-label` |
| `automations` | automation IDs |
| `platforms` | platform names **lowercased** (e.g. `ethereum`, `bitcoin` — NOT the uppercase enum) |
| `actions` | financial action enum names (e.g. `SEND`, `RECEIVE`) |
| `functions` | decoded function names |
| `applications` | application IDs |
| `protocols` | protocol IDs |
| `methodIds` | 4-byte hex method IDs (`0xa9059cbb`) |
| `transactionHash` | tx hash(es) |
| `transactionView` | `readyPending` (default), `onlyReady`, `onlyPending`, `onlyDeleted` |
| `transactionType` | any of `isManual`, `onlyPlug` |
| `filterByBookmark` | bookmark types **lowercased** |
| `missingCounterMatchedTransfers` | `all` (default), `false` (has counter transfer), `true` (no counter transfer) |
| `balanceFactor` | `1` (Inflow), `-1` (Outflow). Typically a single value. |
| `amountAsset` | single asset ID (pair with `amountBetween`) |
If you do not know the exact ID for a multi-select value, query the BFF via the `execute` MCP tool
first to look it up. Do **not** guess.
### 3.3 Range filter
| Param | Format | Notes |
|-------|--------|-------|
| `amountBetween` | `<min>,<max>` | Either side may be empty: `100,500` (range), `100,` (≥100), `,500` (≤500). The single comma is required. |
### 3.4 Boolean filters (include only when `true`)
`showSpam`, `missingFiat`, `failedTransactions`, `nonTaxableType`, `missingCostBasis`,
`internalTransactions`, `ignoreFee`
Example: `?showSpam=true&missingFiat=true`. Never emit `=false` — `false` is the default.
### 3.5 Notes / radio-with-input
| Param | Values |
|-------|--------|
| `commentContains` | `1` = has notes, `-1` = no notes, `0` = show all (omit), or any text string to search note content |
### 3.6 Other singles
| Param | Format |
|-------|--------|
| `savedFilters` | saved-filter ID (single value) |
| `description` | single string |
| `globalSearch` | single string |
---
## Step 4 — Validate before sending
Walk the URL through this checklist. If any rule fails, fix it before handing it over.
1. Path is exactly `/ledger`. No tab suffix, no `?id=...`.
2. `fromDate` / `toDate` paired with `dateType=Custom%20date` (or `dateType` omitted), never with
`Last%2030%20days` or `All%20time`.
3. No `=false` on any boolean.
4. Multi-select values are **comma-joined**, never repeated keys (`?platforms=ethereum,bsc`, never
`?platforms=ethereum&platforms=bsc`).
5. `platforms` values are **lowercased** (`ethereum`, not `ETHEREUM`). All other enum IDs match the
schema (`SPAM`, not `Spam`; `CRYPTO`, not `crypto`).
6. `amountBetween` always has exactly one comma, even when one side is open.
7. If `activities` includes `SPAM`, also set `showSpam=true` so the link is self-contained.
8. If `transactionHash` is set, the dashboard ignores any date filter — warn the user when you also
see a date in their request.
9. Spaces are URL-encoded (`Custom date` → `Custom%20date`).
10. Only filters the user asked for are included.
---
## Step 5 — Hand it over
Send the URL on its own line so it is easy to copy. Briefly state which filters are encoded (and which
subdomain you used) so the user can sanity-check before forwarding to the customer.
Example handoff:
> Built for org `<subdomain>`: filters are platform=ethereum, activities=SPAM, fromDate/toDate Apr
> 2026 (Custom date), showSpam=true.
>
> https://<subdomain>.tres.finance/ledger?fromDate=2026-04-01&toDate=2026-04-30&dateType=Custom%20date&platforms=ethereum&activities=SPAM&showSpam=true
---
## Worked examples
**Last month's Ethereum SPAM transactions:**
```
https://<subdomain>.tres.finance/ledger?fromDate=2026-04-01&toDate=2026-04-30&dateType=Custom%20date&platforms=ethereum&activities=SPAM&showSpam=true
```
**All-time view of two specific wallets:**
```
https://<subdomain>.tres.finance/ledger?dateType=All%20time&internalAccounts=12345,67890
```
**USD-only large transfers ≥ 50k:**
```
https://<subdomain>.tres.finance/ledger?assetClasses=FIAT&amountBetween=50000,&amountAsset=USD
```
**Failed transactions missing fiat in Q1 2026:**
```
https://<subdomain>.tres.finance/ledger?fromDate=2026-01-01&toDate=2026-03-31&dateType=Custom%20date&failedTransactions=true&missingFiat=true
```
**A specific saved filter:**
```
https://<subdomain>.tres.finance/ledger?savedFilters=12345
```
---
## Rules
- **This skill is for general, ad-hoc filtered views** the user describes in plain English. To pin a
single just-created transaction so a pending/backdated row shows immediately, set `transactionHash`
with `dateType=All%20time`.
- **Never hand-craft a ledger URL outside this skill** — use it whenever the user asks for a ledger /
dashboard / filter link.
- **Never include `=false`** on a boolean filter.
- **Never repeat a key** (`?x=a&x=b`) — comma-join into one value.
- **Never use display names** where the dashboard expects enum IDs.
- **Always validate** against the Step 4 checklist before responding.
- **Always state** the subdomain and filters used in your handoff message.
© Nadav Gilliam · MIT · anthropics/claude-plugins-community