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, then the Paddle CLI, fall back to a Node SDK seed script, or dictate dashboard steps as a last resort.

Quality

83%

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

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.

The body is exceptionally actionable and workflow-safe: executable code for all four methods, explicit validation steps, and fallback/error-recovery loops throughout. Its weaknesses are duplication between the main sections and "Common pitfalls", and the absence of any progressive disclosure — all method detail is inlined in a single large file rather than split into one-level-deep references.

Suggestions

Split each method's full walkthrough (MCP, CLI, SDK, dashboard) into references/method-*.md files, keeping SKILL.md as a routing overview with the method-selection logic and modeling checklist inline.

Move the tax-category table and the MCP/CLI tool-convention blockquotes into a reference file loaded only when relevant, shrinking the always-loaded body.

De-duplicate "Common pitfalls" entries that repeat earlier sections verbatim (currency units, trials on one-time prices, camelCase/snake_case), keeping pitfalls for issues not already stated.

DimensionReasoningScore

Conciseness

The body is dense with Paddle-specific operational detail (zero-decimal currencies, CLI exit codes, camelCase vs snake_case boundaries, permission scopes) and wastes almost no tokens on concepts Claude already knows. It is not 5 because the "Common pitfalls" section restates several points already made earlier (amount units, trials on one-time prices, case conventions), which could be trimmed.

4 / 5

Actionability

Every method ships copy-paste-ready code or commands — complete MCP `execute` payloads, CLI commands with `--json` bodies and `--jq` filters, a full runnable TS seed script, and click-by-click dashboard steps — covering recurring, one-time, paid-trial, and regional-override cases, with exact error codes and scopes. Fully executable with no gaps; not 4 because examples cover the common cases comprehensively.

5 / 5

Workflow Clarity

Clear sequence: confirm modeling decisions with the user first ("Do not guess"), pick the highest-ranked available method, per-method numbered steps, and a dedicated "Verify" section with explicit validation (confirm entities exist, confirm IDs match, suggest next step). Feedback loops are present — fallback to the next method on failure, exit-code-specific error handling (5 = permissions, 7 = validation), and forbidden-key recovery guidance. Matches the 5 anchor.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so ~290 lines live entirely inline: four complete method walkthroughs, a nine-row tax-category table, and two long tool-convention blockquotes. Section structure within the file is good, but per-method detail that would load one level deep in references/ is inlined, matching anchor 3 ("content that should be separate is inline") rather than 4's "most content is appropriately placed" for a skill of this size.

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

The description is specific, action-oriented, and clearly distinct from sibling Paddle skills, with good natural keyword coverage. Its main weakness is the absence of an explicit "Use when..." trigger clause, leaving the invocation condition only weakly implied by the dependency framing.

Suggestions

Add an explicit trigger clause, e.g. "Use when starting a Paddle integration and the catalog doesn't yet exist, or when the user asks to set up or add Paddle products and prices."

Include common synonyms users would naturally say — "catalog", "setup", "billing", "subscriptions" — to broaden trigger-term coverage.

Consider naming the sibling skills it supports (checkout-web, pricing-pages, sandbox-testing, webhooks) in the description so the dependency claim doubles as a routing signal.

DimensionReasoningScore

Specificity

"Create the Paddle products and prices" plus the full fallback ladder ("try MCP tools first, then the Paddle CLI, fall back to a Node SDK seed script, or dictate dashboard steps") lists multiple concrete actions in third person, comprehensively covering the skill's scope. Not 4: no meaningful capability is left out; not applicable below since nothing is generic.

5 / 5

Completeness

The "what" is clear ("Create the Paddle products and prices that other Paddle skills depend on"), but there is no "Use when..." clause or equivalent explicit trigger guidance — "that other Paddle skills depend on" states a dependency, not when to invoke the skill. Per the judging guideline, a missing explicit trigger caps this at 3; it is not 4 because the 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Natural terms users would say are present ("Paddle", "products", "prices", "MCP", "CLI", "Node SDK", "dashboard"), but common synonyms and phrasings like "catalog", "setup", "billing", or "subscriptions" are missing. Between the 4 and 5 anchors: good coverage, a few natural terms absent.

4 / 5

Distinctiveness Conflict Risk

"Paddle products and prices" carves out a clear niche and explicitly positions this as the setup skill other Paddle skills (checkout-web, pricing-pages, etc.) depend on, minimizing overlap with those closely related skills. Clear distinct triggers; not 4 because no minor overlap risk is identifiable.

5 / 5

Total

17

/

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

providers/claude/plugin/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.