Finance Claude Skills
1 219 finance skills from 209 authors. They deal with money: trading, payments, accounting and crypto. Half of them fit into 1 824 tokens or less — that is what one costs your context window when the agent loads it. 285 ship runnable scripts rather than instructions alone. 32 of them cannot work without an MCP server, most often rube. We also found 166 copies of these same skills sitting in other people's repositories — counted once here, not 166 times.
1 219 unique 209 authors 1 updated this month 87 from vendors
> Receive and verify PayPro Global IPN (Instant Payment Notification) webhooks. Use when setting up a PayPro Global IPN handler, debugging the SIGNATURE (SHA256) or HASH (MD5) verification, or handling order and subscription events like OrderCharged, OrderRefunded, and SubscriptionChargeSucceed. Payloads are form-encoded (application/x-www-form-urlencoded), not JSON.
> Receive and verify PayPal webhooks. Use when setting up PayPal webhook handlers, debugging certificate-based signature verification, or handling payment events like PAYMENT.CAPTURE.COMPLETED, PAYMENT.SALE.COMPLETED, BILLING.SUBSCRIPTION.CREATED, or CHECKOUT.ORDER.APPROVED.
> Receive and verify Picqer webhooks. Use when setting up Picqer webhook handlers, debugging X-Picqer-Signature verification, or handling warehouse and order events like orders.completed, picklists.closed, or products.stock_changed.
> Receive and verify Praxis (Praxis Tech / Cashier payment orchestration) webhooks. Use when setting up a Praxis webhook endpoint, verifying the gt-authentication SHA-384 signature, signing the acknowledgement with the external-request-signature header, or handling Payment Notification (transaction_status pending, approved, rejected, error) and Subscription Notification events.
> Receive and verify Quoter webhooks. Use when setting up Quoter webhook handlers, debugging the MD5 hash verification, or handling Quote, Person, and Payment create/update events posted as x-www-form-urlencoded.
> Receive and verify Razorpay webhooks. Use when setting up Razorpay webhook handlers, debugging X-Razorpay-Signature verification, or handling payment events like payment.captured, payment.failed, order.paid, refund.processed, or subscription.charged.
> Receive and verify Recurly webhooks. Use when setting up Recurly webhook handlers, verifying the recurly-signature header (HMAC-SHA256), securing the endpoint with HTTP Basic Auth, or handling subscription and billing events like new_subscription_notification, updated_subscription_notification, successful_payment_notification, and failed_payment_notification.
> Receive and verify Revolut Merchant webhooks. Use when setting up Revolut webhook handlers, debugging Revolut-Signature verification, or handling order and payment events like ORDER_COMPLETED, ORDER_AUTHORISED, or ORDER_PAYMENT_DECLINED.
> Receive and verify Solidgate webhooks. Use when setting up Solidgate webhook handlers, debugging signature verification with the merchant and signature headers, or handling payment events like card_gate.order.updated, card_gate.chargeback.received, subscription.updated.v2, or alt_gate.order.updated.
> Receive and verify Square webhooks. Use when setting up Square webhook handlers, debugging Square signature verification, or handling payment and commerce events like payment.created, payment.updated, refund.created, invoice.payment_made, or order.updated.
> Receive and verify Stripe webhooks. Use when setting up Stripe webhook handlers, debugging signature verification, or handling payment events like payment_intent.succeeded, customer.subscription.created, or invoice.paid.
> Receive and verify Svix webhooks (the Standard Webhooks scheme used by many providers). Use when setting up a Svix webhook handler, debugging svix-id / svix-timestamp / svix-signature verification, handling secret rotation with for events like invoice.paid, user.created, or message.sent.
> Receive and verify Tebex webhooks. Use when setting up Tebex webhook handlers, debugging X-Signature verification, completing the validation.webhook handshake, or handling events like payment.completed, payment.refunded, and recurring-payment.renewed.
> Receive and verify Token.io webhooks. Use when setting up Token.io webhook handlers, debugging Ed25519 signature verification, subscribing to webhook config via PUT /webhook/config, or handling open banking / A2A payment events like PAYMENT_STATUS_CHANGED, REFUND_STATUS_CHANGED, VRP_STATUS_CHANGED, and Webhooks — it signs the raw body with an ASYMMETRIC Ed25519 signature in the token-signature header, verified with your member's Ed25519 public key.
> Receive and verify Treezor webhooks. Use when setting up Treezor webhook handlers, debugging signature verification, or handling BaaS banking events like payin.create, payout.update, cardtransaction.create, wallet.create, or user.kycreview.
> Receive and verify Utila webhooks. Use when setting up Utila webhook handlers, debugging x-utila-signature RSA/PSS verification, or handling Utila digital-asset events like TRANSACTION_CREATED, TRANSACTION_STATE_UPDATED, WALLET_CREATED, WALLET_ADDRESS_CREATED, and TRANSACTION_AML_SCREENING_RESULT_READY.
> Receive and verify WeChat Pay (APIv3) webhook notifications. Use when setting up WeChat Pay webhook handlers, debugging Wechatpay-Signature RSA-SHA256 verification, decrypting the AEAD_AES_256_GCM encrypted resource, or handling payment and refund events like TRANSACTION.SUCCESS, REFUND.SUCCESS, and REFUND.CLOSED.
> Receive and verify Xero webhooks. Use when setting up Xero webhook handlers, debugging x-xero-signature verification, passing Xero's Intent to Receive (ITR) validation, or handling accounting events like CONTACT/CREATE, INVOICE/UPDATE, CREDITNOTE, and SUBSCRIPTION changes.
> Receive and verify Zero Hash webhooks. Use when setting up Zero Hash webhook handlers, debugging x-zh-hook-signature verification, or handling crypto settlement, payment, and balance events like trade_status_changed and payment_status_changed.
> Receive and acknowledge Zift (Zift Payments / payment gateway) webhook notifications. Use when setting up a Zift webhook receiver, understanding why there is no signature/HMAC header to verify, returning the required events like billing.subscription-created, processing.chargeback, and processing.return.
Comprehensive guidance for integrating Jupiter APIs (Swap, Lend, Perps, Trigger, Recurring, Tokens, Price, Portfolio, Prediction Markets, Send, Studio, Lock, Routing). Use for endpoint selection, integration flows, error handling, and production hardening.
Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, game clients, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it when the vulnerability is already understood and the remaining task is exploitation; use pwn instead. Do not use it for pure web workflows, log or disk forensics, or standalone crypto problems unless reversing the implementation is the real blocker.
Analyzing fund portfolios including AUM extraction, holdings counts, and portfolio composition
Fuzzy string matching for fund names and stock CUSIPs using thefuzz library.
Compare holdings between two quarters or find top holders of a specific stock.
Search for fund accession numbers and stock CUSIPs using fuzzy matching.
Techniques for parsing TSV/JSON files for financial reporting data (13F).
Logical patterns for comparing 13F holdings across quarters to determine net change.
Find which funds hold a specific stock and rank them by holding value
Analyze individual fund holdings, AUM, and portfolio composition from 13-F data
Fuzzy search for hedge funds or stocks by name in SEC 13F filings; handles cases where rank 1 is skipped due to amendment filtering.
Complete workflow for finding top stock increases/decreases between Q2 and Q3 for a specific fund.
Find top fund managers holding a specific stock (by CUSIP) using a fixed version of the holding_analysis workflow.
Robust stock analysis and holder identification, bypassing file path issues in default scripts.
Robust data cleaning and formatting for financial datasets in D3.js.
How to calculate a fund's actual AUM and total unique stock count for modern SEC 13F data.
How to accurately identify stocks that "received increased investment" by checking both share count and dollar value change.
How to find top fund managers heavily invested in a particular stock across all data quality issues.
Inspect the actual holdings dataset to understand its schema, field names, and data patterns before applying filters. Use this to identify the correct field name that distinguishes equity securities from bonds, options, warrants, and other non-stock instruments.
Remove non-equity securities (bonds, options, warrants, preferred shares, funds) from holdings data, keeping only common stock positions. Use the correct security type field identified from the raw data structure inspection.
Retrieve and load the complete holdings dataset for a specific fund using its accession_number. Use this to access position-level details needed for AUM, stock count, and comparative analysis.
Find the CUSIP identifier for a specific security (e.g., Palantir) by searching across all holdings data or a security master file. Use this when you need to locate a specific stock across multiple fund positions.
Use Node.js file system operations to recursively copy the entire `/root/data/indiv-stock/` directory (including all subdirectories and files) to `/root/output/data/indiv-stock/` to preserve the original directory structure for the web app
Create and manage a D3 tooltip element that displays on hover for non-ETF stocks with dynamic positioning based on mouse movement
Load CSV data and verify all stock entries contain the required `ticker` field with non-empty string values before using in selection matching logic
Use INDEX-MATCH with two conditions (series code and year) to retrieve values from a source data table. Apply this when you need to pull specific data points based on multiple criteria from an unstructured data range.
How to compare fund holdings between Q2 and Q3 to find top stocks with increased investment by dollar value
How to analyze a fund's AUM and stock count using accession_number, with proper filtering of options and deduplication. Covers Q1 (AUM) and Q2 (stock count).