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 billing in a Next.js app or asks about handling Paddle cancel flows in Server Actions.'
Consider briefly clarifying the 'canceled vs scheduledChange distinction' for selection purposes — e.g., 'Explains when a subscription is immediately canceled vs scheduled for end-of-period cancellation.'
| 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 details), 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 this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely specific niche: Paddle subscription cancellation in Next.js Server Actions. The combination of Paddle + Next.js + subscription cancellation + specific implementation details makes it highly 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, actionable skill with a complete, executable Server Action and clear workflow sequencing including security checks and validation. The temporal model explanation (canceled vs scheduledChange) and common pitfalls section add genuine value. Minor weaknesses are slight verbosity in the introductory sections and the pitfalls list, and the content could benefit from better progressive disclosure if bundle files were available.
Suggestions
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.
Consider condensing the 'Common pitfalls' section by removing points that are already clearly handled in the code comments (e.g., the auth check and ownership check pitfalls repeat what steps 1-2 demonstrate).
| 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, copy-paste ready TypeScript with clear inline comments explaining each step. The env vars, DB schema expectations, and SDK call are all concrete and specific. The verification steps are also actionable with specific expected outcomes. | 3 / 3 |
Workflow Clarity | The Server Action itself is a clearly sequenced 5-step workflow (auth → ownership check → cancel → revalidate → return DTO) with explicit validation at each step. The 'Verify the integration' section provides a clear 6-step testing checklist with expected outcomes and error cases. The temporal sequence of webhook events (steps 1-3) is clearly laid out. | 3 / 3 |
Progressive Disclosure | The skill references related skills (subscription-sync, webhooks) and external docs, which is good. However, with no bundle files, the cross-references to subscription-sync and webhooks are unverifiable. The content is somewhat long (~180 lines) and the 'Common pitfalls' section could potentially be split into a separate reference file, but the inline approach is reasonable for a single-file skill. | 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
86596b3
- 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.