agentleFS
bex-cobex-co/bex/.claude/skills/stripe-directory/SKILL.md

stripe-directory

Skill578 starsChanged 6 days agoApache-2.0View on GitHub

Use when the user wants to find businesses, software, service providers, or partners for a specific industry, workflow, pain point, capability, or job to be done. Also use when the agent needs to programmatically purchase or consume a service. Use Stripe Directory to build a short relevant shortlist, even if the user does not mention Stripe Directory explicitly.

  • Installs packages

5 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use connect-required-verification-information and stripe-pay.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StripeSkill

    connect-required-verification-information

    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.

    Also in 4 projects that use this

  • StripeSkill

    stripe-pay

    Helps users send funds to another Stripe business, transfer money to a Stripe Profile handle or network ID, or ask whether an agent can pay a Stripe business. Use Stripe Directory to find or verify a recipient when the user doesn't provide an exact Stripe Profile handle or network ID.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user wants to _use/buy_ a service, also pass --mpp-supported in at least one search to find results you can pay for programmatically …

    line 30
  2. Distinctive:

    Prefer results whose description/site clearly match the target workflow.

    line 35
  3. Distinctive:

    Prefer more trust signals over fewer: Projects provider, Link enabled, Marketplace app, Stripe Verified.

    line 36
  4. Distinctive:

    Always report the exact queries (and filters) you ran so the user can keep iterating.

    line 48
  5. Distinctive:

    Use the payer the user selected.

    line 69
  6. Distinctive:

    Never invent results or skip the price/approval gate.

    line 75

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stripe Directory Search

Turn a vague market need into a short, relevant shortlist with stripe directory search. Use this even when the user never says “Stripe Directory” — any request to find vendors, tools, partners, or providers for a vertical, workflow, pain point, or job-to-be-done.

Most requests are discovery — find and compare services. That is the core job below. Some services are also MPP-supported (MPP = Machine Payment Protocol), meaning you (the agent) can pay their HTTP 402 (Payment Required) endpoint and consume them directly. When the user actually wants to use or buy a service, present those results and offer to purchase — see “Purchasing” at the end.

Process

  1. Clarify only what’s missing: buyer/vertical, job-to-be-done, must-have capability, geography (only if it matters).
  2. Search iteratively: stripe directory search "<query>" --format json

    • Short noun phrases, one angle per query; run 1-3, then broaden/narrow on results.
    • Angles to cover: vertical → workflow → pain point → adjacent. Two examples:
      • services/trades: vertical (electrician software, electrical contractor) → workflow (field service management, dispatch invoicing estimates) → pain point (job scheduling, quote automation) → adjacent (home services automation, contractor crm).
      • SaaS/software: vertical (b2b saas billing, developer tools) → workflow (subscription management, usage-based metering) → pain point (failed payment recovery, revenue recognition) → adjacent (analytics dashboards, customer onboarding).
    • Hard constraints → try filter flags if available: --countries-supported=US, --has-stripe-app=true, --link-supported=true, --stripe-projects-supported=true, --mpp-supported. Note: as of directory v0.3.0 the server ignores filter flags — only --limit (max 10) and --page affect results (stripe directory search --help → “Filter flags have no server-side equivalent yet and are ignored”). Keep queries narrow via the search term itself; re-check --help before relying on filters.
    • If the user wants to use/buy a service, also pass --mpp-supported in at least one search to find results you can pay for programmatically (even if currently server-ignored, it documents intent for when the server honors it).
    • Sparse niche? Raise --limit (max 10) and try the next --page before concluding it’s empty.
  3. Dedupe & score using display_name, description, url, username as evidence.

    • Prefer results whose description/site clearly match the target workflow.
    • Prefer more trust signals over fewer: Projects provider, Link enabled, Marketplace app, Stripe Verified. For buy/use intent, also prefer MPP-supported results.
    • Thin description but strong brand/domain match → keep in a weaker bucket, don’t discard.
  4. Return a shortlist, not a dump — 5-10 strong matches, grouped:

    • direct / adjacent / needs manual review
    • Each entry: name · why it matched · URL (· which query surfaced it, when useful).
    • Projects providers: offer the follow-up. The JSON gives the exact commands under each result’s projects.catalog_command / projects.install_command (stripe projects catalog <provider>, stripe projects add <provider>).
    • MPP-supported results: note they’re purchasable and include mpp.slug / mpp.url.
  5. Be honest about weak results — if sparse or generic, say so and adjust: broaden, narrow, or try synonyms rather than padding with noise.

Always report the exact queries (and filters) you ran so the user can keep iterating.

Purchasing (only when the user wants to buy or consume a service)

MPP-supported results are payable directly. Don’t drive to purchase unprompted. When the user wants to buy, present the full menu of payment methods and ask which they’d like to use before doing anything:

"Which payment method would you like to use?

  • Link CLI — Stripe-native, test mode available (recommended)
  • Tempo — crypto wallet
  • Privy Agent Wallet CLI — crypto wallet
  • mppx — debug-only fallback"

Once the user picks, silently run which <tool> 2>/dev/null to check if it’s installed. If not installed, offer to install it (for example, npm i -g @stripe/link-cli for Link CLI) and wait for confirmation before proceeding.

Always show the price and get explicit user approval before any money moves; prefer a no-charge test path first.

Short version:

  1. Resolve the real callable endpoint from the result’s mpp.slug / mpp.url. mpp.url is often the mpp.dev landing form (https://mpp.dev/services#<slug>) — resolve the raw endpoint on mpp.dev if so. Read the HTTP 402 challenge to confirm the amount: curl -s -D - -o /dev/null <endpoint_url> (look for WWW-Authenticate).
  2. Use the payer the user selected.
    • link-cli (Stripe-native Shared Payment Token, has a test mode, no crypto wallet, US Link accounts only; npm i -g @stripe/link-cli): auth login → mpp decode --challenge "<value>" (get network_id) → spend-request create --credential-type shared_payment_token --network-id <id> --amount <cents ≤50000> --context "<100+ chars>" --request-approval (blocks for approval) → mpp pay <endpoint_url> --spend-request-id <approved_id>.
    • Tempo: tempo wallet login / services / request.
    • Privy: @privy-io/agent-wallet-cli.
    • mppx: debug-only fallback.

Never invent results or skip the price/approval gate.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.