302 skills · sorted by relevance
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.
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.
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.
Build Solana apps with guidance for wallet connections, on-chain programs, testing, and deployment. Also covers balance and transaction lookups, troubleshooting, and migrating older code, with review steps before signing or sending transactions.
Build JavaScript or TypeScript apps that interact with NEAR. This skill guides token transfers, smart contract calls, account and key management, transaction signing, and message authentication through near-api-js v7 examples.
Integrate Jupiter Lend on Solana to query lending markets, rates, and user positions, then build deposits, withdrawals, borrowing, and repayment transactions. Separate SDKs, or code libraries, cover data access and transactions, including combined collateral and debt operations.
Design and debug Solana applications using MagicBlock. The skill covers fast transaction execution, state delegation and settlement, private payments, price feeds, randomness, and temporary permissions, with guidance on routing transactions and validating integrations.
Match blockchain transactions in TRES to customer invoices or vendor bills in a connected ERP accounting system. Review ranked candidates, choose the payment account, and approve linking, optional fiat value adjustments, and synchronization to Xero, QuickBooks Online, or NetSuite.
Retrieve company filings from the SEC, the US securities regulator, using Python. Extract financial statements, insider transactions, and institutional holdings to research companies and compare financial data across reporting periods.
Investigate unusual transactions, sensor spikes, rare failures, and other suspicious records. The skill helps compare anomaly detection methods and thresholds, prepare records for human review, and plan checks for false alarms and missed anomalies.
Triggered by "tidy up", "clean up transactions", "categorize uncategorized", "organize my transactions"
The English summary is being prepared. Showing the original description.
Monitor blockchain mempools for pending transactions, gas analysis, and MEV opportunities. Use when analyzing pending transactions, optimizing gas prices, or researching MEV. Trigger with phrases like "check mempool", "scan pending txs", "find MEV", "gas price analysis", or "pending swaps".
The English summary is being prepared. Showing the original description.
Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "which database should I use", "SQL or NoSQL", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", "my queries are slow at scale", or "data is inconsistent across replicas". Also trigger when choosing a datastore, designing data pipelines, or debugging distributed-system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.
The English summary is being prepared. Showing the original description.
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running workflows.
The English summary is being prepared. Showing the original description.
Read and write YNAB budgets: list budgets, accounts, balances, transactions, and categories; record transactions. Trigger phrases: ynab, budget, my budget, spending.
The English summary is being prepared. Showing the original description.
Read-only Ramp corporate spend: transactions, cards and card limits, users, departments. No spend actions by design. Trigger phrases: ramp, corporate spend, expense transactions, card spend limits.
The English summary is being prepared. Showing the original description.
View Mercury bank accounts and transactions. Read-only by design. Trigger phrases: mercury, mercury balance, mercury transactions.
The English summary is being prepared. Showing the original description.
View Paddle transactions and customers. Read-only by design. Trigger phrases: paddle, paddle transactions, paddle customers.
The English summary is being prepared. Showing the original description.
Use when you need to write or review programmatic JDBC with Spring — including JdbcClient (Spring Framework 7+) as the default API, JdbcTemplate only where batch/streaming APIs require JdbcOperations, NamedParameterJdbcTemplate for legacy named-param code, parameterized SQL, RowMapper mapping to records, batch operations, transactions, safe handling of generated keys, DataAccessException handling, read-only transactions, streaming large result sets, and @JdbcTest slice testing. This should trigger for requests such as Review Java code for Spring JDBC (JdbcTemplate, JdbcClient, NamedParameterJdbcTemplate); Apply best practices for Spring JDBC data access in Java code; Detect and fix SQL injection risks in JDBC code; Improve transaction boundaries or exception handling for JDBC operations; Review JdbcClient usage in Spring Framework 7. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Use when you need data access with Micronaut Data — @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers. For raw java.sql access without generated repositories, use @511-frameworks-micronaut-jdbc. This should trigger for requests such as Review or implement Micronaut Data repositories and entities; Add transactions, pagination, or projections in Micronaut persistence layer; Model Micronaut Data entities and repositories; Review Micronaut Data transactions and pageable queries; Improve projections or optimistic locking with Micronaut Data. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Use when you need programmatic JDBC in Quarkus — Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services. This should trigger for requests such as Review JDBC or SQL data access in a Quarkus project; Improve transactions and parameter binding for Quarkus JDBC; Translate SQLException to domain exceptions or stream large result sets; Fix CDI self-invocation bypassing @Transactional in Quarkus; Review Agroal DataSource usage in Quarkus JDBC. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Use when you need MongoDB persistence in Quarkus — including Panache Mongo entities/repositories, document design, indexes, transactions where applicable, and error handling. This should trigger for requests such as Add MongoDB in Quarkus; Review Quarkus Mongo Panache design; Improve Mongo error handling in Quarkus services; Model MongoDB documents for a Quarkus service; Configure Quarkus MongoDB clients codecs or transactions. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Provides comprehensive Drizzle ORM patterns for schema definition, CRUD operations, relations, queries, transactions, and migrations. Proactively use for any Drizzle ORM development including defining database schemas, writing type-safe queries, implementing relations, managing transactions, and setting up migrations with Drizzle Kit. Supports PostgreSQL, MySQL, SQLite, MSSQL, and CockroachDB.
The English summary is being prepared. Showing the original description.
Provides distributed transaction patterns using the Saga Pattern for Spring Boot microservices. Use when implementing distributed transactions across services, handling compensating transactions, ensuring eventual consistency, or building choreography or orchestration-based sagas with Kafka, RabbitMQ, or Axon Framework.
The English summary is being prepared. Showing the original description.