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

76%

Does it follow best practices?

Impact

100%

1.09x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/subscription-cancel/SKILL.md

Quality

Content

85%Weight 40%Scale 1-3

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

The body delivers an executable, well-sequenced Server Action with strong verification steps and clean organization, though some explanatory prose could be trimmed for token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with a complete executable action and a lean table, but explanatory prose around the SDK behavior, pitfalls, and the user-vs-database narrative repeats concepts and could be tightened without losing clarity.	2 / 3
Actionability	Provides a complete, copy-paste-ready Server Action with imports, auth, ownership check, SDK call, revalidation, and a slim DTO, plus a concrete verification checklist — fully executable guidance.	3 / 3
Workflow Clarity	The action is explicitly sequenced (authenticate, ownership check, cancel, revalidate, return DTO) and the 'Verify the integration' section provides a numbered checklist with explicit failure-mode validation (logged-out / forged ID must error and skip the SDK call).	3 / 3
Progressive Disclosure	Well-organized single-file skill with clearly signaled one-level-deep references (Related docs links, the paired subscription-sync/webhooks skills); no bundle files exist, and the body is appropriately self-contained for its scope.	3 / 3
	Total	11 / 12 Passed

Description

67%Weight 40%Scale 1-3

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

The description is specific and well-scoped to a distinct niche, but it omits an explicit 'Use when...' trigger clause and leans on technical terminology over natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when implementing a cancel-subscription button or stopping a Paddle recurring billing plan in a Next.js app').

Include natural trigger terms users would actually say, such as 'cancel subscription', 'stop billing', 'turn off renewal', or 'end recurring plan'.

Keep third person voice — currently compliant, but ensure no second-person phrasing is introduced when adding the trigger clause.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'auth, ownership check, safe `effectiveFrom` default, revalidation, and the `canceled` vs `scheduledChange` distinction' — naming specific technical components rather than vague abstractions.	3 / 3
Completeness	Clearly answers 'what does this do' (the full cancel pipeline), but has no explicit 'Use when...' trigger clause; the 'when' is only implied by the task description, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Uses relevant domain keywords ('Cancel a Paddle subscription', 'Next.js Server Action') but lacks common natural user phrasings like 'cancel billing', 'stop subscription', or 'turn off renewal' that a user might actually say.	2 / 3
Distinctiveness Conflict Risk	Highly specific niche — 'Cancel a Paddle subscription from a Next.js Server Action' — with triggers unlikely to fire for unrelated skills, clearly distinguishing it from generic subscription or Paddle skills.	3 / 3
	Total	10 / 12 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: cbd404f

Reviewed: 3 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.