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
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/catalog-setup/SKILL.mdQuality
Discovery
67%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 strong in specificity and distinctiveness, clearly articulating a concrete multi-step fallback strategy for creating Paddle products and prices. Its main weaknesses are the lack of an explicit 'Use when...' clause and limited natural trigger terms that users might employ when requesting this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when setting up Paddle for the first time, bootstrapping a catalog, or when other Paddle skills report missing products or prices.'
Include additional natural trigger terms users might say, such as 'set up Paddle catalog', 'initialize Paddle products', 'bootstrap Paddle', or 'seed Paddle data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: creating Paddle products and prices, trying MCP tools first, falling back to a Node SDK seed script, and dictating dashboard steps as a last resort. These are specific, actionable steps. | 3 / 3 |
Completeness | Clearly answers 'what' (create Paddle products and prices with a prioritized fallback strategy) but lacks an explicit 'Use when...' clause. The phrase 'that other Paddle skills depend on' implies when, but doesn't explicitly state trigger conditions. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Paddle products', 'prices', 'MCP tools', 'Node SDK', 'seed script', and 'dashboard steps'. However, it misses common user-facing trigger terms — a user might say 'set up Paddle catalog', 'initialize products', or 'bootstrap Paddle' which aren't covered. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — it targets a very specific niche (creating Paddle products/prices as a prerequisite for other Paddle skills) with a clear prioritized approach (MCP → SDK → dashboard). Unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with excellent workflow clarity, providing three complete methods with proper fallback logic and verification steps. Its main weakness is verbosity — concepts are repeated across sections (amount units, casing conventions, environment differences), and some explanatory content could be trimmed or offloaded to supporting files. The skill would benefit from being more concise while preserving its strong executable examples and clear decision tree.
Suggestions
Reduce repetition: amount unit explanations, camelCase/snake_case conventions, and environment warnings each appear in multiple sections — state them once in a 'Key conventions' block and reference it.
Move the 'Common pitfalls' section and tax category table to separate bundle files (e.g., PITFALLS.md, TAX_CATEGORIES.md) to reduce the main file length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is thorough and well-structured, but it's verbose in places — the 'What you're modeling' section explains product/price relationships Claude already knows, the tax category table could be more compact, and the 'Common pitfalls' section repeats information already stated in the methods (e.g., amount units, camelCase vs snake_case). Several points are stated two or three times across sections. | 2 / 3 |
Actionability | Excellent actionability across all three methods. The MCP execute payloads are copy-paste ready with correct parameter shapes, the Node SDK seed script is fully executable TypeScript with proper imports and error handling, and the dashboard steps are click-by-click specific. Variants for one-time prices and regional overrides are also provided as executable snippets. | 3 / 3 |
Workflow Clarity | The skill has a clear decision tree (MCP → SDK → Dashboard) with explicit fallback triggers, numbered steps within each method, and a dedicated 'Verify' section with specific validation commands. The feedback loop for failures (e.g., 'if forbidden, fall back to next method'; 'if validation fails, regenerate API key') is well-defined. The instruction to confirm details with the user before creating anything adds an important checkpoint. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but it's a long monolithic file (~250 lines of dense content). The common pitfalls section, tax category table, and regional pricing examples could be split into referenced files. The 'Related docs' section at the end provides good external references, but the skill itself would benefit from offloading some detail to bundle files. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- PaddleHQ/paddle-agent-skills
- Commit
86596b3
- 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.