paddle-subscription-cancel
Cancel a Paddle subscription from a Next.js Server Action — auth, ownership check, safe `effectiveFrom` default, revalidation, and the `canceled` vs `scheduledChange` distinction.
87
80%
Does it follow best practices?
Impact
100%
1.09xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/subscription-cancel/SKILL.mdQuality
Discovery
82%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 description excels at specificity and distinctiveness, clearly identifying a narrow technical task with precise implementation details (auth, ownership check, effectiveFrom, canceled vs scheduledChange). Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The description reads almost like a checklist of implementation concerns rather than a skill selection guide.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user needs to implement subscription cancellation with Paddle in a Next.js app, or asks about handling Paddle cancel flows, effectiveFrom defaults, or the canceled vs scheduledChange distinction.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: cancel a Paddle subscription, auth, ownership check, safe effectiveFrom default, revalidation, and the canceled vs scheduledChange distinction. These are highly specific implementation details. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (cancel a Paddle subscription from a Next.js Server Action with specific implementation concerns), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'cancel', 'Paddle', 'subscription', 'Next.js', 'Server Action', 'effectiveFrom', 'scheduledChange', 'canceled'. These are terms a developer would naturally use when seeking help with this task. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely specific niche: Paddle subscription cancellation via Next.js Server Actions. The combination of Paddle + Next.js + subscription cancellation is highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 a complete, executable Server Action and excellent workflow clarity including validation checkpoints and a clear async event timeline. Its main weakness is moderate verbosity — the common pitfalls section, while valuable, is lengthy and partially redundant with the inline code comments. Progressive disclosure is adequate but could benefit from bundle structure to offload detailed reference material.
Suggestions
Tighten the 'Common pitfalls' section by consolidating related points (e.g., merge the auth/ownership items) and removing explanations already covered by the code comments.
Trim the 'When to use this skill' section to 2-3 sentences — the cross-references to other skills are useful but the framing is verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and well-structured, but includes some unnecessary verbosity — the 'When to use this skill' section over-explains context, the 'Common pitfalls' section is thorough but could be tightened (some points repeat what the code comments already convey), and the table explaining effectiveFrom values is slightly padded. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The full Server Action is complete, executable TypeScript with clear inline comments explaining each step. The env vars, DB schema expectations, and SDK call are all concrete and copy-paste ready. The verification steps are specific and testable. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced: auth → ownership check → SDK call → revalidation → slim DTO return. The 'What the user sees vs what the database stores' section explicitly maps the async event timeline. The 'Verify the integration' section provides a clear validation checklist including negative test cases (logged out, forged ID). | 3 / 3 |
Progressive Disclosure | The skill references related skills (subscription-sync, webhooks) and external docs, which is good. However, with no bundle files, all content is inline in a single file that runs quite long (~180 lines). The common pitfalls and verification sections could potentially be separated, and the cross-references to other skills are mentioned but not linked with file paths. | 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
- PaddleHQ/paddle-agent-skills
- Commit
62438cd
- 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.