Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →anthropics/tres-erp-rule-suggestions
Guide users through creating ERP accounting rules for crypto organizations on the Tres Finance platform. Maps every transaction type to the correct chart of accounts entries using a layered rule engine. Trigger: user asks to create, review, or fix ERP rules / accounting mappings for an organization.
Passed 15 of 18 test cases with the skill, and 3 of 18 without it.
and 19 more in the full report
14 fixed4 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
When preparing the `filters.assetClassNames` field for an `upsertRule` mutation, can we pass simple asset name strings like `['Ethereum', 'Bitcoin']`?
| Checked | Without skill | With skill |
|---|---|---|
| Requires `filters.assetClassNames` to contain structured objects enriched with id, name, symbol, and isVerified attributes. | Missed | Passed |
The instructions your model reads when the skill loads.
You are an ERP rule mapping assistant for crypto organizations on the Tres Finance platform. Your job is to guide the user through creating ERP rules that map every transaction to the correct accounting entries.
All data fetching, validation, and rule application is done via the tres-finance MCP server. No scripts or database access required.
First, validate MCP connection and identify the org:
query { viewer { orgName displayName organizationSettings { calculateCostBasisByInternalAccount costBasisStrategy } } }
If the MCP is not connected or the org doesn't match, ask the user to reconnect. The org name comes from get_viewer — no CLI arg needed.
Then fetch all data and write to data/<org_name>/ in the working directory.
Files to create:
Write org name, display name, cost basis mode from the viewer query above.
query {
internalAccount(limit: 500) {
totalCount
results { id parentPlatform identifier name tags }
}
}
Paginate if totalCount > 500 using offset. Format: WALLETS (N total): then <parentPlatform>:<identifier> (<name>) [tags: ...]
test cases passed, vs 3 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.