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.

1.09x

Quality

81%

Does it follow best practices?

Impact

100%

1.09x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, executable skill with a complete Server Action, a strong verification checklist, and clean single-file structure; only minor conciseness trims are possible.

Dimension	Reasoning	Score
Conciseness	Efficient body that assumes competence and avoids explaining Paddle/Next.js basics; minor redundancy between the 'Common pitfalls' entries and the earlier narrative keeps it just below fully lean.	4 / 5
Actionability	Provides a complete, copy-paste-ready Server Action plus the effectiveFrom decision table and a slim DTO return; specific examples cover the common cancel cases.	5 / 5
Workflow Clarity	Destructive operation with a numbered Server Action sequence (auth, ownership, cancel, revalidate) and an explicit 6-step verification checklist including negative tests (SDK NOT called when forbidden, status flips at period end).	5 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear section headers and one-level-deep, clearly signaled references (paired skills, Related docs, reference implementation); no nested references.	5 / 5
	Total	19 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that names concrete actions and occupies a clear niche, but it omits an explicit 'when to use' trigger clause, which caps its completeness.

Suggestions

Add a 'Use when...' clause to the description, e.g. 'Use when wiring a Cancel subscription button in a Next.js App Router Server Action.'

Include a natural trigger synonym such as 'unsubscribe' to broaden keyword coverage.

Consider mentioning the Next.js 15 / App Router context in the description to sharpen the trigger.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('auth, ownership check, safe effectiveFrom default, revalidation, canceled vs scheduledChange distinction'); scoped to a single cancel operation rather than a broad action menu, so not a clear 5.	4 / 5
Completeness	The 'what' is explicit but the description lacks any 'Use when...' trigger clause; per the rubric a missing explicit trigger caps completeness at 3 even though the body supplies the when.	3 / 5
Trigger Term Quality	Natural phrases like 'Cancel a Paddle subscription' and 'Next.js Server Action' appear; a few common variants (e.g. 'unsubscribe') are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	A narrow niche (Paddle + Next.js Server Action + subscription cancel) with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PaddleHQ/paddle-agent-skills
Path: skills/subscription-cancel/SKILL.md
Commit: de7fcd3

Reviewed: 20 days ago

Table of Contents

Discovery Implementation Validation

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.