本文へ移動
cccskills
無料GitHub で公開

stripe-directory

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.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/bexスター 577(GitHub 577 + cccskills 0)
連携ツールStripe

実行スコア 未検証

インストール方法を見る

含まれるファイル（1）

  • SKILL.md6.0 KB

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

bex-background-workers

無料

Sets up and configures background workers on bex for queue-based job processing. Use when the user needs to process async jobs, consume from a queue, run Celery/Sidekiq/BullMQ/Asynq/Oban workers, handle graceful shutdown with SIGTERM, wire a worker to Key Value, or choose between workers and cron jobs for background work. Trigger terms: background worker, async jobs, queue consumer, Celery, Sidekiq, BullMQ, Asynq, Oban, job processing, SIGTERM, graceful shutdown.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/bex5772026年10月29日 更新

bex-blueprints

無料

Authors and validates render.yaml Blueprints for bex infrastructure. Use when the user needs to write or edit a render.yaml, wire services together with fromDatabase/fromService/fromGroup, set up projects and environments for multi-service apps, configure preview environments, validate against the schema, or fix immutable field errors. Trigger terms: render.yaml, Blueprint, IaC, fromDatabase, fromService, envVarGroups, previews, projects, environments.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/bex5772026年10月29日 更新

bex-cli

無料

Installs and uses the bex CLI for deploys, logs, SSH, psql, Blueprint validation, and automation. Use when the user needs to run bex CLI commands, script deploys in CI/CD, authenticate with an API key, query services non-interactively, or troubleshoot CLI auth issues. Trigger terms: bex CLI, bex login, bex deploys, bex logs, bex ssh, bex psql, bex blueprints validate, bex skills, BEX_ACCESS_TOKEN, non-interactive, CI/CD deploy.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/bex5772026年10月29日 更新

bex-cron-jobs

無料

Configures and troubleshoots scheduled tasks on bex using cron job services. Use when the user needs to run something on a schedule, write a cron expression, set up a periodic job, migrate from Heroku Scheduler, choose between cron jobs and background workers, or fix a cron that isn't firing. Trigger terms: cron job, scheduled task, periodic job, cron expression, schedule, run every, timer, Heroku Scheduler migration.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/bex5772026年10月29日 更新

bex-debug

無料

Debug failed bex deployments by analyzing logs, metrics, and database state. Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes. Use when deployments fail, services won't start, or users mention errors, logs, or debugging.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/bex5772026年10月29日 更新

bex-deploy

無料

Deploy applications to bex by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on bex's cloud platform.

日本語の概要は準備中です。原文の説明を表示しています。

bex-co/bex5772026年10月29日 更新

bex-co のスキルをすべて見る

このスキルの問題を報告する