Stripe Directory Vendor Finder
Turn a vague market need into a focused shortlist of vendors, providers, or partners.
The skill limits its declared tool access to Bash(stripe directory *) and requires displaying price, selecting a payment method, and obtaining explicit approval before purchases, with a test-mode preference. However, discovery and purchasing involve external services, third parties, and possible money movement; data flows, credential handling, least-privilege boundaries, rollback, and result-authenticity checks are not fully specified, so points are deducted.
The workflow and command examples are broadly consistent and include iterative search, pagination, HTTP 402 challenge inspection, and tool availability checks. There are no committed tests for this skill, compatibility matrix, or clear handling of malformed input, network failures, unavailable providers, or payment errors; dependencies on the Stripe CLI, payment tools, and external endpoints remain unverified, so the static score is conservative.
The intended scenarios, search angles, filters, result groupings, and purchase trigger are reasonably clear. Non-fit boundaries, input/output contracts, and exclusion conditions for semantic triggering are incomplete; there is no Chinese-language guidance or mainland-China reachability assessment, and core functionality depends on external Stripe services, so points are deducted.
The SKILL.md has clear search/purchasing sections, examples, progressive disclosure, and confirmation rules. Repository context supplies an MIT license, security-reporting path, and synchronization/update information, but the skill lacks independent versioning, changelog, named maintenance responsibility, dependency installation guidance, and troubleshooting FAQs, so points are deducted.
The skill can turn a market need into a short vendor list and specifies deduplication, grouping, query reporting, and purchase-related fields, giving the discovery task a directly usable intended output. However, no representative output or skill-specific tests are provided; quality depends on directory data and judgment, while purchasing still requires later user choices and local environment setup, so the static score remains limited.
The skill provides concrete CLI commands, fields, and approval steps, while the README, license, security policy, and CI offer limited repository traceability. It lacks dedicated tests, sample outputs, independent reproduction records, or third-party corroboration, and the shown CI does not cover the stripe-directory key paths, so points are deducted.
- Before use, verify that the Stripe CLI, network access, and directory data source are available; search results should not be treated as verified vendors.
- For every purchase, recheck the resolved endpoint, 402 amount, recipient, and payment scope, and retain a manual recovery path for failures.
- Do not authorize production payment credentials without documenting credential, logging, and request-data flows.
- Mainland-China network reachability and payment-tool availability are not verified by the supplied material.
What it does & when to use it
This is one standalone Agent Skill in Stripe AI for finding businesses, software, service providers, and partners relevant to an industry, workflow, pain point, or job to be done. It runs iterative searches through the Stripe Directory CLI and returns a short list grouped into direct matches, adjacent options, and items needing manual review. For MPP-supported services, it can support programmatic consumption when the user explicitly wants to buy or use a service. The repository is MIT-licensed and contains 24 skills; this profile covers only Stripe Directory.
It identifies the buyer, vertical, job to be done, required capability, and any relevant geography, then runs commands such as stripe directory search "<query>" --format json, optionally with country, Stripe app, Link, Projects, or MPP filters. It deduplicates and scores results using names, descriptions, URLs, usernames, and Stripe-related trust signals, then produces a 5-10 item shortlist grouped as direct, adjacent, or needs manual review. When the user wants to purchase or consume a service, it presents payment methods, verifies the HTTP 402 price, and proceeds with the selected payer only after explicit approval.
- A product team needs software, service providers, or partners for a defined industry.
- An operations lead wants vendor candidates for workflows such as dispatch, invoicing, subscription management, or customer onboarding.
- A researcher needs recommendations tied to a concrete business pain point rather than a generic marketplace dump.
- A developer wants to consume an MPP-supported service programmatically after reviewing the payment method and price.
Pros & cons
- Breaks vague demand into vertical, workflow, pain-point, and adjacent search angles.
- Returns a curated shortlist grouped by relevance instead of an unfiltered dump.
- Uses signals including Projects, Link, Marketplace, Stripe Verified, and MPP support.
- Provides a documented purchase flow for MPP services with payment-method and price approval gates.
- Requires the `stripe directory` CLI command and network access.
- The source provides no test suite, detailed error behavior, or search-quality metrics.
- Manual installations do not auto-update.
- Purchasing may involve external payment tools and always requires explicit approval; service pricing is not specified in the source.
How to install
This skill is distributed as part of the Stripe AI collection. The README documents manual installation with npx skills add https://docs.stripe.com. Manually installed skills do not auto-update; the README recommends npx skills update -y for updates. The repository also documents official plugin installation routes for Claude Code, Codex, and Cursor.
How to use
Give the agent a concrete discovery request, such as “Find usage-based billing software for US B2B SaaS,” and include the vertical, workflow, must-have capability, and relevant geography. The skill runs stripe directory search and returns a shortlist. If you want to buy or consume a service, state that explicitly; then choose a payment method and approve the displayed price before any money moves. The source does not fully document every service-specific execution detail.