Trigger on-chain data collection (a "Commit") in Tres Finance for wallets that have already been onboarded. Use this skill whenever the user wants to collect data, pull balances, sync wallets, refresh on-chain data, run a commit, trigger a commit, or "collect" anything in Tres. This is the second step of the Tres onboarding flow — it sits between wallet upload (tres-wallets-upload) and balance validation (tres-asset-balance-validation). Always trigger this skill for any request that mentions "co
SkillScore65Maintained
Automatic
◆Finance & Accounting pack
Last verified 9/28/2026
What it changes
Passed 12 of 18 test cases with the skill, and 4 of 18 without it.
Without skill22%
With skill65%
Checks it passed that the model alone missed
Informs the user that the Tres MCP is not connected.
Explains that skipping transactions leaves the ledger empty.
Suggests balance validation against DeBank as the next step.
and 9 more in the full report
10 fixed5 passed either way8 still failing0 broke
Pass-rate lift
+43 pp
Tokens
+134%
Agent turns
0%
Response time
-42%
Model gemini-3.6-flashMeasured 9/28/2026v115 of 23 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
I am ready to trigger the Tres Finance commit mutation directly. I want balances only across specific account IDs. Should the GraphQL mutation variables use snake_case like balances_only and internal_account_ids or camelCase like balancesOnly and internalAccountIds?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies that GraphQL variable names must use camelCase formatting.
Passed
Passed
Explains that snake_case variable names will be rejected by the Tres GraphQL API.
Missed
Passed
case-06 · gemini-3.6-flash · 9/28/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md354 linessingle file
Tres Finance — Data Collection (Commit)
Overview
Commit is the step that pulls on-chain data into Tres Finance for the wallets
already onboarded to the org. It runs the platform's data-collection pipeline for
each wallet and either:
Full data collection — collects the full transaction history and current
balances. Used for a complete onboarding or historical backfill.
Balances only — collects only the current asset balances (no transactions).
Much faster; useful when the user just wants an up-to-date snapshot or is
preparing for a quick balance validation.
This skill is the second step of the customer onboarding flow:
Upload wallets (tres-wallets-upload) — register the wallets in Tres.
Collect data (this skill) — run the commit so Tres actually fetches the
on-chain state.
Validate balances (tres-asset-balance-validation) — cross-check the
collected balances against DeBank.
When to Use
Trigger this skill whenever the user wants to:
Run a commit / trigger a commit / kick off data collection