CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paddle-catalog-setup

Create the Paddle products and prices that other Paddle skills depend on — try MCP tools first, fall back to a Node SDK seed script, or dictate dashboard steps as a last resort.

62

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/catalog-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

An exceptionally actionable, well-sequenced skill: every method path (MCP, SDK, dashboard) has executable guidance, explicit fallbacks, and a verification stage. The weaknesses are repetition between the main sections and the pitfalls section, and the absence of any reference files for bulk lookups like the tax category table.

Suggestions

De-duplicate the pitfalls section: the zero-decimal currency rule and the camelCase/snake_case convention are restated in full after already being covered — shorten each pitfall to a one-line pointer.

Move the tax category table and the MCP conventions blockquote into a references/ file (e.g. references/tax-categories.md) so SKILL.md stays a lean overview with well-signaled, one-level-deep references.

The paid-trial SDK limitation is stated in both "Trial type" and Method 2 — keep the full explanation in one place and cross-reference it.

DimensionReasoningScore

Conciseness

The body is mostly high-value Paddle-specific detail Claude would not know (zero-decimal currencies, MCP execute caps, trial types, error codes), but several blocks are repeated in full: the zero-decimal currency rule and the camelCase/snake_case MCP convention each appear both in the main sections and again in "Common pitfalls", and the paid-trial SDK limitation is stated twice. This matches anchor 3 — mostly efficient but could be tightened — rather than anchor 4's 'minor instances'.

3 / 5

Actionability

Fully executable throughout: a complete MCP `execute` payload, a copy-paste TypeScript SDK seed script with its run command (`npx tsx scripts/seed-paddle-catalog.ts`), click-by-click dashboard steps, and concrete failure strings (`400 bad_request`, `forbidden`, `product_tax_category_not_approved`) with remediations. Variants cover the common cases — recurring, one-time, free/paid/cardless trials, and regional price overrides — matching anchor 5's copy-paste-ready coverage.

5 / 5

Workflow Clarity

The method-selection hierarchy ("Pick the highest-ranked method that's available"), per-method numbered steps, explicit fallback on failure ("fall back to the next method rather than retrying"), and a dedicated "Verify" section (list products, confirm IDs match, suggest next step) provide a clear sequence with explicit validation and error-recovery loops, matching anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist; all content is inline in a single ~270-line SKILL.md. Section organization is good, but bulk reference material — the 9-row tax category table and the MCP conventions blockquote — is inlined rather than split into a one-level-deep reference file, matching anchor 3's 'some structure... content that should be separate is inline' rather than anchor 4's mostly-appropriate placement.

3 / 5

Total

16

/

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 with a distinctive vendor-anchored niche and an unusually useful method-fallback chain. Its main weakness is the missing explicit "Use when..." trigger clause, which caps completeness at 3 and leaves triggering to inference from context.

Suggestions

Add an explicit trigger clause, e.g. "Use when starting a Paddle integration and the catalog is empty, or when the user asks to create/add Paddle products, prices, or plans."

Include natural synonyms such as "catalog", "plans", and "subscriptions" so users phrasing the request those ways still trigger the skill.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Create the Paddle products and prices", "try MCP tools first", "fall back to a Node SDK seed script", "dictate dashboard steps" — including the full method-fallback chain. It sits below anchor 5 because the actions are compressed (mechanisms named without detail) and supporting scope like tax categories, trials, or verification is absent.

4 / 5

Completeness

The "what" is clear (create Paddle products and prices via three escalating methods), but "when" is only weakly implied by "that other Paddle skills depend on" — there is no explicit "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Paddle", "products", "prices", "Node SDK", and "dashboard" are natural terms a user setting up a Paddle integration would say, matching anchor 4's 'good keyword coverage; a few natural terms missing'. Common variations like "catalog", "plans", "subscriptions", or "billing" are missing, so it does not reach anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Create the Paddle products and prices that other Paddle skills depend on" carves out a distinct one-time catalog-setup niche versus sibling skills (checkout-web, pricing-pages, sandbox-testing, webhooks), and the vendor name "Paddle" makes false triggering on unrelated skills very unlikely — matching anchor 5's clear niche with minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

PaddleHQ/paddle-agent-skills

Path

skills/catalog-setup/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.