CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paddle-subscription-sync

Mirror Paddle subscription and customer state into your database via webhooks — schema, upsert pattern, status semantics, scheduled changes, and access gating.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-sequenced skill: executable code end-to-end, a genuine ordering-correctness mechanism, explicit verification steps, and a pitfalls section full of real failure modes. The main improvements are trimming known-boilerplate and rationale sections, and splitting reference material (Supabase setup, backfill detail) into bundle files.

Suggestions

Move the Supabase createServerClient boilerplate and the backfill/MCP details into a reference file (e.g. references/backfill.md), keeping SKILL.md a lean overview with one-level-deep pointers.

Consolidate the out-of-order/last_event_at explanation (currently given in the schema section, the handler notes, and the pitfalls) into one authoritative spot, and trim the 'Why mirror state at all?' section to a sentence.

Add a short failure-recovery note to the verification section (what to inspect if rows don't land or status doesn't flip, e.g. check the destination's Usage type and event subscription list).

DimensionReasoningScore

Conciseness

The bulk is dense, non-obvious domain knowledge (the last_event_at ordering guard, status semantics table, scheduled-change lifecycle, pitfalls) that earns its tokens. However, the ~50-line Supabase createServerClient boilerplate, the 'Why mirror state at all?' rationale section, and the out-of-order guard being explained three times (schema notes, process-event notes, pitfalls) are minor over-explanation that could be trimmed. Fits 'Efficient; minor instances of over-explanation' (4) rather than 5, where every token earns its place, and clearly above 3, which requires more pervasive padding.

4 / 5

Actionability

Fully executable throughout: complete SQL DDL and upsert functions with the ordering guard, typed TypeScript webhook handlers, customer-mapping and query helpers, a runnable MCP backfill snippet, and a cron reconciliation route — copy-paste ready and covering the common cases (Supabase and non-Supabase, MCP and SDK backfill). Matches 'Fully executable; copy-paste ready code or commands'.

5 / 5

Workflow Clarity

The sequence is clear (schema → clients → user mapping → event handlers → status semantics → scheduled changes → querying → backfill) with an explicit 6-step verification checklist, and the batch backfill is validated (ordering guard, 'run it once before flipping access gating', 50-call-cap handling with an SDK fallback), so the destructive/batch cap does not apply. It falls short of 5 only because the verification steps say what to confirm but give no failure-recovery path (e.g. what to check if the row never lands), a minor validation gap.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so this scores the body structure itself: clear section headers, easy linear navigation, and clearly signaled cross-references to sibling skills ('webhooks', 'checkout-web', 'subscription-cancel', 'sandbox-testing') and external docs. Not 5 because some inlined content — the Supabase client boilerplate and the backfill/MCP details — is a natural candidate for one-level-deep reference files in a ~450-line body; not 3 because what is inline is mostly the core deliverable rather than content that clearly belongs elsewhere.

4 / 5

Total

17

/

20

Passed

Description

75%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, distinctive, well-scoped description in third-person voice with comprehensive capability enumeration. Its one real weakness is the missing explicit 'Use when...' trigger clause, which caps completeness at 3 and leaves natural synonyms like 'sync' and 'billing' unstated.

Suggestions

Add an explicit trigger clause, e.g. 'Use when syncing Paddle subscriptions or customers into your database, processing Paddle subscription webhooks, or gating feature access by subscription status.'

Include the synonym 'sync' in the description itself (it currently appears only in the skill name), plus 'billing'/'Paddle billing' as natural user phrasings.

Mention the initial backfill/reconciliation use case in the description so users adding this to an app with existing Paddle data find the skill.

DimensionReasoningScore

Specificity

The description names the domain and enumerates multiple concrete capabilities — "Mirror Paddle subscription and customer state into your database via webhooks — schema, upsert pattern, status semantics, scheduled changes, and access gating" — with comprehensive coverage of the skill's scope. It matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' rather than the level-4 anchor, which requires minor gaps in coverage.

5 / 5

Completeness

The 'what' is clear and concrete (mirror subscription/customer state into a database via webhooks, covering schema, upserts, status semantics, scheduled changes, access gating), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when' is only weakly implied via 'via webhooks'. Per the judging guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms are present ("Paddle", "subscription", "customer", "webhooks", "database", "mirror"), but common synonyms users would say are missing — notably "sync" (which appears only in the skill name, not the description), "billing", and "Paddle API". This fits 'Good keyword coverage; a few natural terms missing' (4), not 5, which requires synonyms/extensions coverage; it is clearly above 3, where relevant keywords are present but whole variations are absent.

4 / 5

Distinctiveness Conflict Risk

"Paddle subscription and customer state ... via webhooks" carves out a clear niche with provider-specific triggers; it is unlikely to fire for the wrong skill. This matches 'Clear niche with distinct triggers; minimal conflict risk' rather than 4, which expects minor overlap with closely related skills (e.g. a generic webhook-ingestion or billing skill).

5 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

PaddleHQ/paddle-agent-skills

Path

skills/subscription-sync/SKILL.md

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.