CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./providers/cursor/plugin/skills/catalog-setup/SKILL.md

The canonical home for this skill is paddle-catalog-setup in PaddleHQ/paddle-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-engineered, highly actionable skill body: executable code for all three methods, an explicit verify phase, and genuine error-recovery loops. The weaknesses are repetition of the casing and currency-unit rules across sections, and a monolithic single-file structure where the pitfalls and dashboard details could be offloaded to reference files.

Suggestions

Split the pitfalls list (and optionally the dashboard walkthrough) into a references/ file (e.g. references/pitfalls.md), keeping a one-line pointer in SKILL.md to cut the always-loaded token cost.

De-duplicate the camelCase/snake_case convention and the JPY/KRW/CLP zero-decimal-currency rules — state each once and have the pitfalls section cross-reference rather than restate them.

Consider moving the full SDK template to a scripts/ bundle file so the body only carries the MCP example inline.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout — no explanations of what Paddle or billing intervals are, and every section is task-focused. Not a 5 because some material is repeated verbatim in two places: the camelCase/snake_case convention and the zero-decimal-currency (JPY/KRW/CLP) rule each appear in both the method sections and the pitfalls list, and the same catalog example is shown twice across Methods 1 and 2.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance for every method: complete MCP `execute` payloads, a runnable TypeScript seed script with install and run commands (`npm install @paddle/paddle-node-sdk`, `npx tsx scripts/seed-paddle-catalog.ts`), click-by-click dashboard steps, and concrete verification calls. One-time, regional-override, and trial variants are all covered with real code.

5 / 5

Workflow Clarity

Clear sequence with explicit validation: confirm modeling decisions with the user first ("Do not guess"), pick the highest-ranked available method with fallback-on-failure instructions ("If a method fails midway... fall back to the next method rather than retrying"), a dedicated Verify section with three concrete checks, and error-recovery loops for `forbidden`/`unauthorized` failures. The dashboard method even closes the loop by having the user report IDs back.

5 / 5

Progressive Disclosure

No bundle files exist and the entire ~245-line skill is inlined in SKILL.md with no internal reference files. The section structure is clear, but the ~10-item pitfalls list, the tax category table, and the full dashboard walkthrough are reference-grade content that loads on every invocation. Not a 4 because content that clearly belongs in a separate file (pitfalls) is inlined with no offloading to references/.

3 / 5

Total

17

/

20

Passed

Description

66%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 strong, specific description that states what it does and the three methods it uses, with natural domain keywords. Its main weakness is the missing explicit 'Use when...' trigger clause — the activation condition must be inferred from 'that other Paddle skills depend on'.

Suggestions

Add an explicit trigger clause, e.g. "Use when starting a Paddle integration and the catalog is empty, or when adding new products or prices."

Include common synonyms users would say — "catalog", "setup", "billing plans" — to broaden natural trigger coverage.

Mention the environment dimension (sandbox vs production) since it is a core decision point and helps distinguish this from runtime Paddle skills.

DimensionReasoningScore

Specificity

"Create the Paddle products and prices" plus "try MCP tools first, fall back to a Node SDK seed script, or dictate dashboard steps" names several concrete actions and three concrete methods. Not a 5 because it omits other capabilities the skill actually covers (tax category selection, regional price overrides, sandbox-vs-production choice), leaving minor gaps in coverage.

4 / 5

Completeness

The "what" is clear and specific (create Paddle products and prices via MCP, SDK script, or dashboard), but the "when" is only implied by "that other Paddle skills depend on" — there is no explicit "Use when..." clause or equivalent trigger guidance, which caps completeness at 3. Not a 4 because the usage condition (starting a Paddle integration with an empty catalog) must be inferred rather than stated.

3 / 5

Trigger Term Quality

"Paddle", "products", "prices", "MCP", "Node SDK seed script", and "dashboard" are terms a user would naturally say when needing catalog setup. Not a 5 because common synonyms like "catalog", "setup", "billing", or "subscriptions" are absent, so a few natural trigger phrases are missing.

4 / 5

Distinctiveness Conflict Risk

"Paddle products and prices" carves out a clear niche (catalog setup) distinct from sibling skills like checkout-web or webhooks. Not a 5 because it explicitly references "other Paddle skills", creating minor overlap risk with closely related Paddle skills a user might actually want.

4 / 5

Total

15

/

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