Claude Plugins Community Marketplace

The tres-invoice-bill-matching skill provides an end-to-end workflow for matching TRES ledger transactions to ERP invoices or bills (Accounts Payable/Accounts Receivable). Once matched, the user can optionally sync the matched entry to a connected ERP such as Xero, QuickBooks Online (QBO), or NetSuite.

Triggering the skill: Trigger this skill when a user expresses intent to match, link, close, reconcile, or sync an invoice/bill against a blockchain transaction.

Example trigger phrases:

• "match this invoice to a transaction"
• "close invoice INV-123"
• "link this tx to a bill"
• "pay this invoice from this transaction"
• "find the invoice/bill for this hash"

When NOT to trigger:

• For general transaction explanations (use tres-tx-story).
• For ingesting explorer links into the ledger (use tres-explorer-tx-to-ledger).
• For ERP connection setup (use tres-settings-management).

The tres-erp-rule-suggestions skill is a user-invocable guide designed to help crypto organizations on the Tres Finance platform create, review, or fix ERP accounting rules. It maps transaction types to the correct chart of accounts entries using a layered rule engine.

Trigger: The skill is activated when a user asks to create, review, or fix ERP rules or accounting mappings for an organization.

Data Access: All data fetching, validation, and rule application are performed via the tres-finance MCP server. No direct database access or external scripts are required.

name: tres-erp-rule-suggestions
description: >
  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.
user_invocable: true

The tres-rollup-rules skill is a data-driven discovery tool used to analyze sub-transaction patterns in TRES Finance. It identifies repetitive transaction groups and proposes 'rollup rules' to consolidate them into single aggregated entries (daily or monthly) for cleaner ERP integration.

Key Concepts:

• Rollup Rule Definition: A rule is uniquely identified by four dimensions: internalAccount (wallet) + asset KEY + platform + balanceFactor (direction). You can also add optional discriminating filters like fees, methodIds, subtxType, amount bounds, or counterparties.
• Non-destructive: Rollups do not delete data; original raw sub-transactions remain visible in a Rollup Breakdown report.
• Discovery Flow: The skill follows a pipeline of confirming scope, inventorying existing data/rules, and performing core analysis to find candidates.
• Compatibility: Requires the TRES Finance MCP connector.

When building the subTransactions array for the createManualTransactionWithSubTransactions mutation, follow these direction and action rules:

Key Rules:

• Token transfers: One sub-transaction per event. thirdPartyIdentifier is the counterparty address.
• Gas fee: Always create a GAS sub-transaction if the user is the sender. Set thirdPartyIdentifier to the fixed value "Native".
• Internal transfers: If the user owns both the sender and receiver addresses, create two sub-transactions (one OUTFLOW, one INFLOW) with their respective belongsToIds, plus a GAS sub-transaction for the sender.
• Fiat values: Do not pass fiatValue unless explicitly requested; the system handles pricing automatically.

The exported workbook contains two specific tabs designed for different stages of the contact building process:

1. Contacts (Import-Ready)

This sheet matches the TRES contacts import template exactly. It is intended for the user to fill out and then upload back into TRES using the contacts import skill.

2. Address details (Enrichment)

This is a reference tab used to help users prioritize which addresses to label. It contains activity statistics and inferred network information.

Sorting: Both tabs are sorted by Total USD (inflow + outflow) in descending order so that the most active counterparties appear first.