cypher-pay
Auto-provision a virtual Visa card to complete an online purchase. Use when user asks to buy something and needs payment, or explicitly mentions cypher-pay/agent-pay. Handles onboarding (email OTP + KYC — once ever), token generation (once per device), funding, card creation, 3DS, and card lifecycle.
90
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly communicates what the skill does (auto-provisions virtual Visa cards with full lifecycle management) and when to use it (buying something, needing payment, or mentioning specific product names). It lists concrete sub-capabilities and includes both natural user language and product-specific trigger terms, making it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: auto-provision a virtual Visa card, onboarding (email OTP + KYC), token generation, funding, card creation, 3DS, and card lifecycle. These are detailed, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (auto-provision a virtual Visa card, handle onboarding, token generation, funding, card creation, 3DS, card lifecycle) and 'when' (explicit 'Use when user asks to buy something and needs payment, or explicitly mentions cypher-pay/agent-pay'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'buy something', 'needs payment', 'cypher-pay', 'agent-pay', 'online purchase', 'Visa card'. Covers both natural language ('buy something') and product-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — virtual Visa card provisioning and payment processing is very specific and unlikely to conflict with other skills. The product names 'cypher-pay' and 'agent-pay' further distinguish it. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity for a complex multi-step financial automation. The branching logic, validation checkpoints, and security rules are well-defined. The main weaknesses are its length (could split reference sections into separate files) and some unnecessary content like the SDK reference section that doesn't serve the CLI-driven agent use case.
Suggestions
Move the 'Operations reference' and 'SDK Reference' sections to separate files (e.g., REFERENCE.md, SDK.md) and link to them from the main skill to reduce token footprint.
Remove the SDK Reference section entirely — it targets developers building custom integrations, not the agent executing CLI commands, and adds ~15 lines of irrelevant content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) and includes some sections that could be trimmed — the SDK reference section at the end is unnecessary for a CLI-driven agent workflow, and some explanatory text (e.g., 'This is a CONSUMER automation flow') adds context but could be more concise. However, most content earns its place given the complexity of the multi-path flow. | 2 / 3 |
Actionability | Every step includes exact CLI commands with concrete flags and arguments, expected JSON output shapes, and clear branching logic. Commands are copy-paste ready with real examples (e.g., `agent-pay submit-application` with all flags shown). The decision tables and exit code references make it fully executable. | 3 / 3 |
Workflow Clarity | The multi-step flows are clearly sequenced with explicit validation checkpoints (verify token works, poll for KYC approval, wait-for-txn before cancelling, 3DS handling). Error recovery is addressed (stale token → delete and re-auth, timeout → freeze instead of cancel). The branching logic via the enrollment/KYC table is well-structured with clear feedback loops. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but it's a monolithic document that could benefit from splitting the operations reference and onboarding paths into separate files. The SDK reference section at the end feels tacked on and could be a separate reference file. However, the logical flow from session detection → onboarding → purchase is well-structured within the single file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- CypherD-IO/agent-pay
- Commit
04bf5f2
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.