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.

60

Quality

71%

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 ./skills/catalog-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is highly actionable with executable code for every method and a clear, validated workflow including fallbacks and verification. It is somewhat verbose and monolithic — the inline code templates and Common pitfalls could be externalized into reference files to improve token efficiency and progressive disclosure.

Suggestions

Move the full MCP and SDK code templates into reference files (e.g. references/seed-script.ts, references/mcp-execute-examples.js) and keep the body to minimal snippets plus links, to reduce token load and improve progressive disclosure.

Trim the Common pitfalls section to items not already covered inline (amount units, camelCase/snake_case, and trial-on-one-time are restated) to improve conciseness.

Extract the tax-category table and currency-unit rules into a reference file referenced once, since they are reference material rather than core workflow steps.

DimensionReasoningScore

Conciseness

Mostly efficient with executable examples and a focused tax table, but the Common pitfalls section repeats material already stated inline (amount units, camelCase vs snake_case, trial on one-time) adding notable padding.

2 / 3

Actionability

Provides complete, copy-paste-ready code for all three methods (MCP execute payload, TS seed script, dashboard click-steps) plus concrete verify commands and exact field names.

3 / 3

Workflow Clarity

Clear ranked method-selection sequence with explicit fallback on failure, a dedicated Verify section with checkpoints, and error-recovery guidance (forbidden/unauthorized → regenerate key).

3 / 3

Progressive Disclosure

Well-organized into clear sections with one-level-deep external doc links, but no bundle files are used and the body is a long monolith (~240 lines) that mixes overview, full code templates, and a large pitfalls list inline rather than splitting detail into references.

2 / 3

Total

10

/

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 distinctive, clearly scoping a one-time Paddle catalog-setup task with a ranked method fallback. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness, and trigger terms could better match natural user phrasing.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when setting up a new Paddle integration that still needs products and prices created.'

Surface more natural user phrasings as trigger terms, such as 'Paddle catalog', 'set up Paddle billing', or 'Paddle subscription plans'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create the Paddle products and prices', 'try MCP tools first, fall back to a Node SDK seed script, or dictate dashboard steps' — naming three distinct methods.

3 / 3

Completeness

Clearly answers 'what' (create Paddle products and prices via three methods) but the 'when' is only implied by naming the dependency on other Paddle skills — there is no explicit 'Use when...' trigger clause.

2 / 3

Trigger Term Quality

Includes relevant terms ('Paddle products and prices', 'MCP tools', 'Node SDK seed script', 'dashboard') but lacks the common phrasings a user would naturally say like 'set up Paddle', 'Paddle catalog', or 'Paddle billing'; missing common variations.

2 / 3

Distinctiveness Conflict Risk

A clearly defined niche (Paddle catalog setup with a ranked three-method fallback) that is unlikely to conflict with the sibling skills it names (checkout-web, pricing-pages, etc.).

3 / 3

Total

10

/

12

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.

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