Results for “transactions”

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.

The English summary is being prepared. Showing the original description.

Retrieves bank balances and transaction history through Plaid, a bank account connection service. It reports dates, merchants, and amounts, distinguishes pending from posted transactions, and summarizes spending by category or merchant on request.

• Checking balances across bank accounts
• Reviewing transaction dates, merchants, and amounts
• Summarizing spending by category or merchant

Design and review Java database code using MyBatis and MyBatis-Spring. Covers mapping query results to objects, safe SQL parameters, transactions, pagination, batch writes, and investigating slow or unnecessarily repeated queries.

• Designing mapper interfaces and XML mappings
• Reviewing dynamic SQL and parameter safety
• Checking transactions across multiple updates

Design and review Prisma database code for TypeScript backends. Use examples for schemas, queries, transactions, pagination, migrations, and connection management to identify common pitfalls in bulk operations and serverless deployments.

• Designing database models and relationships with Prisma
• Reviewing queries and pagination
• Investigating transaction and bulk update problems

Design and improve database access in Spring Boot with JPA/Hibernate, tools that map Java objects to database tables. Covers relationships, queries, transactions, and pagination, including fixes for excessive database queries.

• Designing database entities and relationships
• Fixing excessive queries when loading related data
• Reviewing transactions and change tracking

Build Kotlin database access with JetBrains Exposed, a library that maps database records to code. Apply examples for queries, transactions, reusable connections, schema migrations, and repository interfaces that separate database operations from business logic.

• Implementing database queries and updates
• Configuring reusable database connections
• Managing database schema migrations

Read balances, transactions, recurring payments, loan details, and investment holdings from financial accounts linked through Plaid. Review multiple institutions together or focus on selected accounts and dates to understand recorded spending and financial activity.

• Checking balances across linked accounts
• Reviewing spending over a chosen period
• Listing active subscriptions and recurring bills

Write TypeScript applications that read NEAR Protocol data, call contracts—programs on the blockchain—and send tokens. The skill also covers wallet connections, React integration, key management, transaction building, and testing in a local sandbox.

• Read contract data and account balances
• Implement contract calls and NEAR transfers
• Connect wallets to a React application

Build applications with embedded wallets, user sign-in, and transactions across multiple blockchains. This skill guides wallet creation, spending limits, shared approvals, and server-controlled wallets for organizations or AI agents using Privy.

• Add sign-in and embedded wallets to an app
• Set spending limits for an AI agent's wallet
• Build treasury wallets with shared approvals

Connect an AI agent to BNB Chain through MCP, a protocol for accessing external tools. Configure the server, inspect balances and transactions, transfer tokens, interact with contracts, register agents, and manage Greenfield storage.

• Configure a connection to the BNB Chain MCP server
• Look up balances, blocks, and transactions
• Transfer tokens or interact with contracts

Check AltLLM Portal credit, expiry dates, billing transactions, and usage through the local altllm CLI. Review activity by period, model, or API key, and redeem promo codes using a saved Portal session.

• Check credit, expiry dates, and available models
• Review billing transactions by type
• Compare usage by period, model, or API key

Set up a chart of accounts and rules for categorizing transactions. Use when asked how to categorize expenses/transactions, set up a chart of accounts, organize bookkeeping, or sort bank transactions into the right buckets. Produces a practical chart of accounts for the business, categorization rules with examples and edge cases, and a clean-books routine — so the books are consistent and ready for an accountant. Not tax/accounting advice.

The English summary is being prepared. Showing the original description.

Saga patterns, compensating actions, and two-phase commit for distributed transactions. Activate on: distributed transaction, saga, compensating action, two-phase commit, eventual consistency, cross-service transaction. NOT for: single-database transactions (use database-connection-pool-manager), event sourcing (use cqrs-event-sourcing-architect).

The English summary is being prepared. Showing the original description.

Saga patterns, compensating actions, and two-phase commit for distributed transactions. Activate on: distributed transaction, saga, compensating action, two-phase commit, eventual consistency, cross-service transaction. NOT for: single-database transactions (use database-connection-pool-manager), event sourcing (use cqrs-event-sourcing-architect).

The English summary is being prepared. Showing the original description.

Build or review Java services with Quarkus 3.x using patterns for REST APIs, database access with Panache, and messaging with Apache Camel. Examples cover layered code structure, validation, transactions, and asynchronous processing, where work completes separately from the main flow.

• Designing a REST API with separate service and repository layers
• Connecting services through Camel and RabbitMQ
• Reviewing Panache database access and transactions

Create investment-banking-style presentations for board discussions and M&A decisions. Organize comparable companies, past transactions, valuation ranges, and strategic options into slides that distinguish sourced figures from assumptions and explain the recommended course of action.

• Preparing board materials on strategic alternatives
• Comparing peer companies and past M&A transactions
• Presenting valuation ranges and sensitivity analysis

Manage payment administration with Stripe-compatible tools for creating and finding customers, setting up recurring subscriptions, attaching payment methods, and reviewing customer balance changes. The supplied workflows use Composio's Stripe toolkit through Rube MCP.

• Create, update, and search customer records
• Create subscriptions and check their status
• List and attach customer payment methods

Manage personal finances in Firefly III through commands. Record expenses, maintain accounts and budgets, configure recurring transactions and categorization rules, and retrieve monthly income, expense, and budget summaries for review or export.

• Record expenses and check account balances
• Set monthly budget limits
• Configure recurring payments and categorization rules

Plan microservices by defining service responsibilities, communication methods, and data ownership. Use patterns for gradual migration, distributed transactions, and failure isolation to design systems made of independently responsible services.

• Gradually splitting a monolithic system into services
• Defining service responsibilities and interfaces
• Designing event-based communication and distributed transactions

Design and implement Saga workflows across services, using compensating actions to undo completed work after failures. Define step deadlines, handle repeated messages safely, and monitor stalled order, booking, or other long-running processes.

• Coordinating orders across inventory, payment, and shipping services
• Designing compensation for failed bookings
• Investigating workflows stuck during compensation

Design long-running processes across services with Temporal, a system that preserves workflow progress. Covers separating coordination from external operations, handling retries and failures, and structuring workflows so they can resume after interruptions.

• Designing order or booking processes across services
• Building approval flows with timeouts and escalation
• Planning recovery for distributed transactions

Reconcile Stripe activity and bank transactions against invoice records using consistent fee and timing allowances. Record explained differences in the reconciliation sheet and flag unresolved transactions with supporting references for a person to review.

• Reconcile monthly invoices, Stripe activity, and bank deposits
• Check differences caused by fees or deposit timing
• Recheck previously flagged transaction mismatches

Manage payment administration with Stripe-compatible tools for creating and finding customers, setting up recurring subscriptions, attaching payment methods, and reviewing customer balance changes. The supplied workflows use Composio's Stripe toolkit through Rube MCP.

• Create, update, and search customer records
• Create subscriptions and check their status
• List and attach customer payment methods

Assess API business workflows for flaws that automated scanners can miss. The skill examines skipped steps, simultaneous transactions, authentication tokens, GraphQL, and webhooks, helping testers document weaknesses and their financial or operational impact during authorized assessments.

• Reviewing order and payment workflow integrity
• Testing concurrent coupon redemption or transfers
• Assessing JWT validation and GraphQL controls