clerk-cost-tuning
Optimize Clerk costs and understand pricing. Use when planning budget, reducing costs, or understanding Clerk pricing model. Trigger with phrases like "clerk cost", "clerk pricing", "reduce clerk cost", "clerk billing", "clerk budget".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clerk-pack/skills/clerk-cost-tuning/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with strong trigger terms, clear 'when' guidance, and a distinct niche. Its main weakness is that the 'what' portion is somewhat vague — it says 'optimize costs and understand pricing' without listing specific concrete actions or capabilities the skill provides.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Analyzes MAU usage, compares pricing tiers, identifies cost-saving opportunities, and explains Clerk's billing model.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk costs/pricing) and some actions ('optimize costs', 'understand pricing'), but doesn't list specific concrete actions like 'analyze MAU usage', 'compare pricing tiers', or 'identify unused features'. | 2 / 3 |
Completeness | Clearly answers both 'what' (optimize Clerk costs and understand pricing) and 'when' (planning budget, reducing costs, understanding pricing model) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms users would actually say: 'clerk cost', 'clerk pricing', 'reduce clerk cost', 'clerk billing', 'clerk budget'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Clerk pricing/billing optimization is unlikely to conflict with other skills. The 'Clerk' qualifier and specific billing/cost trigger terms make it clearly distinguishable. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable code examples covering Clerk pricing optimization from multiple angles. Its main weaknesses are moderate verbosity (some sections restate information or include unnecessary framing) and the lack of explicit validation/confirmation steps in the user cleanup workflow. The content would benefit from being slightly more concise and splitting detailed code into referenced files.
Suggestions
Add explicit validation/confirmation steps to the inactive user cleanup script (Step 5) — e.g., a dry-run flag, confirmation prompt, or batch-size limit before any destructive action.
Remove the 'Prerequisites' and 'Output' sections which add little value — the prerequisites are self-evident or explained in Step 1, and the output section just restates the steps.
Consider splitting detailed code examples (caching patterns, cleanup script) into separate referenced files to improve progressive disclosure and reduce the main file length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'Prerequisites' (understanding of MAU is explained in Step 1 anyway), the 'Output' section which just restates what was covered, and some comments in code that are slightly verbose. The error handling table and cost estimation example add value though. | 2 / 3 |
Actionability | Every step includes fully executable TypeScript code with realistic file paths and imports. The middleware configuration, caching patterns, monitoring endpoint, cleanup script, and cost estimation function are all copy-paste ready with concrete examples. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from understanding pricing through optimization and monitoring. However, the cleanup script (Step 5) involves a potentially destructive operation (deleting/managing users) but lacks explicit validation checkpoints or confirmation steps — it only logs suggestions rather than enforcing a review-before-action pattern. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's a fairly long monolithic document (~150 lines of content). Some sections like the detailed caching patterns or the cleanup script could be split into referenced files. The reference to 'clerk-reference-architecture' at the end is good but there are no bundle files to support it. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c3a6ad
- 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.