最近新增
刚加入收藏的新技能，抢先试用。
stripe-best-practices
valentin20sluis
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
stripe-apps
valentin20sluis
Build, modify, or review Stripe Apps and extensions using the relevant documentation and reference guides. Use for custom Stripe Dashboard UI, stripe-app.yaml, @stripe/ui-extension-sdk, @stripe/extensibility-sdk, script extensions, extension interfaces, custom workflow actions, and apps that authenticate to Stripe or react to events. Also use when deciding whether a Stripe extension can support the user's billing or workflow requirements.
metronome
valentin20sluis
Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome.
connect-required-verification-information
valentin20sluis
Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.
connect-recommend
valentin20sluis
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.
xemu
koenhendriks
Control the xemu Xbox emulator for SSX 3 reference comparisons - boot it with the ISO, restore saved snapshots (character select, race briefing, race start) in about a second, press controller buttons, pause/resume and take lossless screenshots without stealing the user's focus. Use whenever our recompiled build's output needs checking against real Xbox behaviour (lighting, colours, geometry, menus, race scenes).
routine-dead-code-removal
bex-co
Autonomous maintenance routine that deletes provably unreachable code
routine-abstraction-police
bex-co
Autonomous maintenance routine that finds imports crossing a stated
routine-abstraction-improver
bex-co
Autonomous maintenance routine that flattens over-engineered
qa-find-bugs-mcp
bex-co
Hunt bugs in the Beancount.io remote MCP server by driving the real POST /api-gateway/mcp endpoint with JSON-RPC and real MCP clients, checking transport, discovery, credential boundaries, tool and resource results, the result envelope and prompts against REST/GraphQL controls, reproducing failures, tracing root causes, and deduplicating findings. Use for MCP QA or an agent-endpoint bug hunt. Skip ordinary code review, bug implementation, browser, native-mobile, and CLI QA.
qa-find-bugs-dashboard
bex-co
Exercise the running Beancount.io dashboard with headless Playwright, use QA_EMAIL and QA_PASSWORD for login, reproduce bugs, trace fixes to source, and deduplicate findings. Use for dashboard QA or a browser bug hunt. Skip ordinary code review, bug implementation, and native-mobile QA (use qa-find-bugs-mobile).
qa-find-bugs-cli
bex-co
Hunt bugs in the Beancount.io bea CLI by running real commands against isolated synthetic ledgers, checking output and file effects, reproducing failures, tracing root causes, and deduplicating findings. Use for CLI QA or a terminal bug hunt. Skip ordinary code review, bug implementation, ledger bookkeeping, and browser or native-mobile QA.
pm-brainstorm
bex-co
Propose milestones and tasks for the repository's public .pm adoption board — decompose a topic through the TPM adoption lens, size and gate the work, and emit a text-only proposal for /pm to materialize. Use only when the user explicitly invokes $pm-brainstorm or asks to brainstorm, plan, or break down roadmap work for the .pm board. Do not use to write board files (that is pm) or for ordinary code edits.
pm
bex-co
Arrange the repository's public .pm adoption board — show status, create workstreams, capture inbox notes, promote notes into milestones, add tasks, mark work done, park blocked work with its unblock condition, and drop work that should no longer be done. Use only when the user explicitly invokes $pm or asks to update, arrange, or check the .pm board. Do not use for proposing or brainstorming new work (that is pm-brainstorm) or for ordinary code edits.
mobile-release
bex-co
Summarize mobile changes since the previous release, bump the Beancount mobile version, prepare localized release notes and listings, and release to the Apple App Store and Google Play. Use for $mobile-release or requests to cut a mobile store release. Skip ordinary code shipping, OTA-only updates, release-status questions, and requests to create or edit this skill.
mermaid
bex-co
Create concise, syntax-verified Mermaid architecture diagrams. Use when the user asks to diagram a repository component, document, system, dependency flow, or supplied description in Mermaid.
loopx
bex-co
Autonomously drain a .pm workstream item by item — triage every pending milestone, task, and inbox note, then implement and ship it, close it as already done, block it with an unblock condition, or delete it as invalid, and keep going until nothing actionable remains (do not stop early to ask the user to resume). Use when the user explicitly invokes $loopx or asks to loop, drain, or work through a whole workstream's backlog (e.g. $loopx w1). Sequential, not interval-based; do not use for a timed poll, a single task, or ordinary code edits.
beancount-trade
bex-co
Record a described stock, fund, or crypto trade or investment event in a local Beancount ledger through bea — a buy, a sell with its booking-produced gain, a crypto swap, a cash or reinvested dividend, staking or airdrop receipts, a split, a transfer between the user's own accounts, or an RSU/ESPP vest — with correct lots and cost basis, proposed first and written only after confirmation. Skip options contracts and their lifecycle (beancount-options), broker statement files (beancount-import), statement comparison (beancount-reconcile), performance questions (beancount-ask), everyday one-off entries (beancount-add), tax treatment, and ledgers hosted on Beancount.io.
beancount-reconcile
bex-co
Reconcile one account in a local Beancount ledger against a CSV or PDF statement. For a PDF statement, read this SKILL.md before the PDF helper's guide to establish account comparison, duplicate review and confirmation rules, then use the helper for extraction. Report missing entries, duplicates, amount mismatches and date drift; confirm missing-entry writes and a passing period-end balance assertion through bea. Use for checking whether an account matches its statement. Skip bulk imports, single manual entries (beancount-add), analytics, multi-account close orchestration, edits to existing entries, and ledgers hosted on Beancount.io.
beancount-property
bex-co
Record buying, holding, and selling a home or rental property in a local Beancount ledger through bea — the property as a priced lot, its mortgage liability, escrow, and closing costs split exactly as the closing statement states; each mortgage payment's split read from the loan statement and tied to its printed new balance; rent and deposits per property; and a sale whose gain the booking produces — proposed first and written only after confirmation. Skip paying rent as a tenant (beancount-add), bank or loan statement files (beancount-import), statement comparison (beancount-reconcile), tax treatment and depreciation advice, and ledgers hosted on Beancount.io.
beancount-options
bex-co
Record a described options trade or lifecycle event as validated transactions in a local Beancount ledger through bea, after review and confirmation. Use for single-leg or multi-leg opens, closes, rolls, assignment, exercise and expiration, including pasted broker confirmations. Skip options education, pricing/greeks, tax planning, analytics, broker statement imports, other manual entries (beancount-add), share, fund, and crypto trades and realized-gains reports (beancount-trade), ledger option settings such as operating_currency, and ledgers hosted on Beancount.io.
beancount-migrate
bex-co
Migrate full transaction history from Mint, Monarch, QuickBooks Online or another category-tagged finance-app export into a fresh local Beancount ledger, including requests to create a new ledger and bring in that history. Read this SKILL.md before beancount-init's guide to establish source mappings, transfer pairing and source reconciliation; use init for scaffolding within the migration. Confirm account/category mappings, pair transfers, preserve source IDs, write through bea and reconcile source counts and balances. Skip empty-ledger setup with no history (beancount-init), ongoing bank imports (beancount-import), populated-ledger merges, investment lot reconstruction, and ledgers hosted on Beancount.io.
beancount-importer-author
bex-co
Write or repair a reusable Beangulp importer from a sample bank export for a local ledger, with reviewed golden files and a passing test harness. Use when a source needs a tested Python importer or its format changed, e.g. "write a beangulp importer for my bank's CSV" or "my importer broke after the bank renamed its columns". Wire the confirmed runner through bea ingest; keep generate/test in the authoring project. Skip one-off imports, reconciliation, finance-app migration, ledger writes, and ledgers hosted on Beancount.io.
beancount-import
bex-co
Record bank/card transactions in an existing local Beancount ledger from CSV, OFX/QFX, QIF or PDF statements, including PDF-only banks with no CSV export. For a PDF ledger import, read this SKILL.md before the PDF helper's guide to establish account, deduplication and confirmation rules, then use the helper for extraction. Import broker activity CSVs or holdings/cost-basis exports as lot-carrying entries or opening lots. Read this guide before beancount-trade for these files; skip described trades (beancount-trade). Normalize signs, suggest categories from existing accounts, review duplicates and confirm before bea writes; PDF statements must tie out and end with a balance assertion. Skip standalone PDF extraction/OCR, summarization or editing without a ledger import; account-versus-statement comparisons (beancount-reconcile), full finance-app migrations, reusable importer authoring, individual options trades, single manual entries (beancount-add), ledger option settings, and ledgers hosted on Beancount.io.