uni-stripe
Stripe payments via uni CLI. Use when user wants to check balance, create payment links, manage customers, invoices, refunds, or subscriptions. Requires STRIPE_SECRET_KEY or run 'uni stripe auth'.
93
93%
Does it follow best practices?
Impact
Pending
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 well-crafted skill description that clearly communicates its purpose and when to use it. It uses third person voice, lists specific capabilities, includes natural trigger terms, and has an explicit 'Use when' clause. The additional authentication note adds helpful context without cluttering the core description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'check balance, create payment links, manage customers, invoices, refunds, or subscriptions' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Stripe payments via uni CLI' with specific capabilities) and when ('Use when user wants to check balance, create payment links, manage customers, invoices, refunds, or subscriptions') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Stripe', 'payments', 'balance', 'payment links', 'customers', 'invoices', 'refunds', 'subscriptions' - good coverage of common payment-related terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets Stripe payments via uni CLI. The combination of 'Stripe', 'uni CLI', and payment-specific actions makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted CLI reference skill that excels at conciseness and actionability. Every section provides immediately executable commands with realistic examples. The main weakness is the lack of validation guidance for destructive operations like refunds and subscription cancellations, which could benefit from confirmation steps or error handling notes.
Suggestions
Add a brief note about confirming refund/cancellation operations or checking status after execution (e.g., 'Verify refund status: uni stripe refunds re_xxx')
Consider adding error handling guidance for common failure cases (invalid IDs, insufficient balance, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Stripe is or how payment processing works. Every line is actionable command syntax with minimal but sufficient context. | 3 / 3 |
Actionability | Fully executable commands throughout. Every section provides copy-paste ready CLI commands with realistic examples including IDs, amounts, and flags. No pseudocode or vague descriptions. | 3 / 3 |
Workflow Clarity | Commands are clearly organized by domain (payments, customers, invoices, etc.), but lacks validation checkpoints for potentially risky operations like refunds or subscription cancellations. No feedback loops for error handling. | 2 / 3 |
Progressive Disclosure | For a CLI reference skill of this scope (~80 lines), the flat structure with clear section headers is appropriate. Content is well-organized by feature area with no need for external file references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- shockz09/uni-cli
- Commit
f1dfc90
- 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.