| name | find-services |
| description | Find and shortlist third-party services using OpenSpend CLI marketplace search. Use when asked to discover providers for a capability, compare options, and return a justified recommendation for discovery tasks only. |
find-services
Use OpenSpend CLI to discover external services.
This skill is discovery-only and does not set up payments, install tooling, or perform purchases.
Scope and safety boundaries
- Do not run install or update commands as part of this skill.
- Do not configure
@coinbase/payments-mcp in this skill.
- Do not request or store API keys, wallet secrets, or session tokens.
- If authentication is required to execute search, ask the user before running login commands.
- If the user asks for payment setup or paid invocation flows, hand off to
setup-services.
Credentials and environment
- Preferred path: run search with existing CLI session only.
- Optional credentialed path: OpenSpend user login via
openspend auth login with explicit user confirmation.
- Required environment variables: none for discovery by default.
Workflow
- Verify CLI availability and session state without changing system configuration.
command -v openspend
openspend version
openspend whoami
If openspend is missing or whoami fails:
- Stop search flow.
- Ask the user for confirmation before setup/login.
- Hand off setup/auth steps to
setup-services.
If user confirms login only, run:
openspend auth login -y
Only run login after user confirms.
-
Translate user intent into a precise search query with explicit capability terms.
-
Run search with a default limit of 5.
openspend search "<capability query>" --limit 5 --json
Output shape
When asked to "find a reliable service", produce:
- Up to 5 services in returned order
- A concise explanation of why each service matches the requested capability
- No additional ranking commentary
Recommended service usage
After presenting service options, include a short "recommended way to use" note with:
- Start with a small validation call before scaling usage
- Capture request/response examples and expected success criteria
- If paid calls are needed, request explicit user approval before moving to payment setup via
setup-services
If payment is needed, do not perform payment configuration in this skill.
