find-services_skill

Overview

This skill helps discover and shortlist third-party services using the OpenSpend CLI marketplace search. It is discovery-only: it does not set up payments, install tooling, or perform purchases. Results are limited, justified, and prepared for follow-up validation or handoff to a payment/setup flow when requested.

How this skill works

The skill verifies that the OpenSpend CLI is available and checks the current session without changing system configuration. It translates user intent into a precise capability query, runs a search with a default limit of five results, and returns each service with a concise reason why it matches the request. If authentication is required, it asks for explicit confirmation before attempting a login and otherwise stops and offers a handoff to setup steps.

When to use it

• You need 3–5 candidate providers for a specific capability to evaluate discovery options.
• You want concise, justified matches from the OpenSpend marketplace for vendor shortlisting.
• You need a neutral discovery run without payment, installs, or environment changes.
• You want a small, testable list to validate before committing to paid plans.
• You need to convert a high-level requirement into precise marketplace search terms.

Best practices

• Provide clear capability terms and success criteria to produce precise search queries.
• Confirm before any authenticated CLI actions; discovery prefers existing CLI sessions.
• Start with small validation calls for each shortlisted service before scaling usage.
• Capture request/response examples and define expected success criteria for each provider.
• Request explicit approval before moving to any payment or setup flow; this skill will not perform payments.

Example use cases

• Find reliable data-enrichment APIs for customer record validation and get 3–5 candidate vendors with reasons they match.
• Discover payment gateway integrations compatible with your region and capture providers to validate with test transactions later.
• Shortlist logging or observability service providers that meet throughput and retention needs for a proof-of-concept.
• Compare image-processing APIs for a specific capability (e.g., OCR accuracy on receipts) with concise match explanations and recommended validation calls.
• Identify backup or archive service providers with matching compliance or retention features for further evaluation.