AGENT SKILL

tres-report-analyzer

Analyze any TRES Finance report XLSX and produce an automatic findings summary. Trigger this skill whenever a user uploads a .xlsx file that came from TRES Finance and asks to "analyze", "summarize", "review", "check", "audit", "look at", "what does this show", "any issues", "anything interesting", or "walk me through" the report. Also trigger when the user uploads an Excel file and mentions TRES, reconciliation, balances, transactions, cost basis, roll forward, or ERP sync. The skill identifies the report type from the file structure, runs targeted analysis based on report-specific logic, and produces a clear findings summary highlighting anomalies, key metrics, and action items.

使用场景电子表格
License 许可
Apache-2.0
最近更新
2026-11-12
Stars
★ 4.9k
Forks
363

01 前言 Front Matter

name
tres-report-analyzer
description
Analyze any TRES Finance report XLSX and produce an automatic findings summary. Trigger this skill whenever a user uploads a .xlsx file that came from TRES Finance and asks to "analyze", "summarize", "review", "check", "audit", "look at", "what does this show", "any issues", "anything interesting", or "walk me through" the report. Also trigger when the user uploads an Excel file and mentions TRES, reconciliation, balances, transactions, cost basis, roll forward, or ERP sync. The skill identifies the report type from the file structure, runs targeted analysis based on report-specific logic, and produces a clear findings summary highlighting anomalies, key metrics, and action items.

02 资源文件 3

03 SKILL.md 正文

TRES Report Analyzer

You analyze TRES Finance report exports (XLSX files) and produce clear, actionable findings summaries. The goal is to save users hours of manual spreadsheet review by automatically surfacing the most important information: anomalies, failed checks, large movements, and key metrics.

How it works

  1. Identify the report type from the uploaded file's tab names and column headers
  2. Run the analysis script which performs report-specific checks
  3. Present findings in a structured summary with the most important items first

Step 1: Identify the report type

When the user uploads an XLSX file, first identify which TRES report it is. Use the tab names as the primary signal:

Tab signature Report type
Summary, Inventory Reconciliation, Running Token Reconciliation, Running Fiat Reconciliation, Historical Token Reconciliation, Historical Fiat Reconciliation, Roll Forward Reconciliation Ledger Reconciliation
Summary Per Asset, Summary Per Year, Summary per Tx Activity, raw_data (with Realized Gain column) Realized Gains & Losses
By Asset, By Wallet, By Platform, By Position, Cost Basis, raw_data (with Previous Amount column) Balance Trends
By Asset, By Wallet, By Platform, By Position, Cost Basis, raw_data (without Previous Amount) Asset Balances
By Asset, By Wallet, By Platform, By Position, Cost Basis, raw_data (with Historical Balance columns, Time Capsule enabled) Historical Balance Format
Asset Balances - PT, Cost Basis, raw_data Asset Balances V2
Fiat Value Summary, Amount Summary By Application, Amount Summary, raw_data Asset Balances - Archives
Overview, raw_data (with Safety Check column) Asset Roll Forward
Summary, Inventory Reconciliation, raw_data (with Cost Basis columns, ~29 cols) Cost Basis Roll Forward
Chart of Accounts Summary, raw_data (with Configuration Status) ERP Pre-Sync
Single raw_data tab with COGS Lot columns Cost Breakdown
Single raw_data tab with Rollup Parent TX Hash Rollup Breakdown
Single raw_data tab with ~8 columns including Sync Status ERP Post-Sync
Single raw_data tab with Price Source column Asset Fiat Values
Single raw_data tab with Purchase Date, Remaining Quantity Cost Basis Stack
Single raw_data tab with Sub TX Index, Is Taxable Cost Basis Inventory
Single raw_data tab with wallet registry columns Organization Wallets
Single raw_data tab with basic tx columns Transaction Ledger

If you cannot identify the report type, tell the user and ask them to confirm which report it is.

Step 2: Run the analysis

Use the Python script at scripts/analyze_report.py to extract data from the XLSX file. Run it like this:

python /path/to/skill/scripts/analyze_report.py "/path/to/uploaded/file.xlsx" --output /path/to/output.json

The script outputs a JSON file with extracted metrics. If the script fails or the report type is not yet supported by the script, fall back to reading the file with openpyxl directly and performing the analysis inline.

What to analyze per report type

Read references/analysis-playbook.md for the detailed analysis checklist for each report type. The general pattern is:

For reconciliation reports (Ledger Reconciliation, Asset Roll Forward, Cost Basis Roll Forward):

  • Check columns: how many pass vs. fail?
  • Which assets/wallets have the largest discrepancies?
  • What is the total slippage or gap amount?
  • Are there patterns (same wallet, same asset, same platform)?

For balance reports (Asset Balances, Historical Balance Format, V2, Archives, Balance Trends):

  • Total portfolio value
  • Top holdings by fiat value
  • Any zero-balance or negative-balance entries?
  • For Balance Trends: largest movers (biggest absolute change)
  • Unverified tokens or missing prices

For transaction reports (Transaction Ledger, Realized Gains & Losses, Cost Breakdown):

  • Total transaction count and date range
  • Largest transactions by fiat value
  • Total realized gains/losses (if applicable)
  • Classification breakdown (how many of each type)
  • Any unclassified transactions?

For cost basis reports (Cost Basis Stack, Cost Basis Inventory, Cost Basis Roll Forward):

  • Total cost basis and unrealized gains
  • Lots with largest unrealized losses (tax-loss harvesting candidates)
  • Age of lots (any very old lots?)
  • Impairment amounts if applicable

For ERP reports (Pre-Sync, Post-Sync):

  • Configuration status breakdown (how many ready vs. misconfigured)
  • Missing account mappings
  • Failed syncs and error patterns
  • Debit/credit balance check

Step 3: Present findings

Structure your response as follows. Keep it concise -- the user wants insights, not a data dump.

Format

Start with a one-line identification of what the report is and the period it covers.

Then present findings in order of importance:

  1. Red flags (if any): failed checks, large discrepancies, missing data, failed syncs
  2. Key metrics: total value, count, gains/losses -- the headline numbers
  3. Notable items: largest transactions, top holdings, biggest movers -- things worth knowing
  4. Action items (if any): specific things the user should investigate or fix

End with a brief note about what the user can ask as a follow-up (e.g. "I can drill into any specific asset or wallet if you want a closer look").

Style rules

  • Use actual numbers from the data, not vague descriptions
  • Round large numbers sensibly ($1,234,567.89 -> $1.23M)
  • No em-dashes or en-dashes (use -- instead)
  • Keep the total response under 500 words unless the user asks for more detail
  • If there are many findings, prioritize the top 5 and mention "N more items" the user can ask about

04 同仓库更多 Skills

anthropics
anthropics/claude-plugins-community

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/Excel) 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".

财务电子表格Skill与智能体开发
★ 4.9k
anthropics
anthropics/claude-plugins-community

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.

★ 4.9k
anthropics
anthropics/claude-plugins-community

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.

Skill与智能体开发
★ 4.9k
anthropics
anthropics/claude-plugins-community

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/disable platforms, balance diff, commit strategy, cost basis, ERP, pricing, sync boundaries, or any setting read/write 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".

Skill与智能体开发
★ 4.9k
anthropics
anthropics/claude-plugins-community

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/pending rules, use the tres-rollup-review skill instead.

财务Skill与智能体开发
★ 4.9k
anthropics
anthropics/claude-plugins-community

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.

财务Skill与智能体开发
★ 4.9k