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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clerk-cost-tuning78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-structured description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is the lack of specific concrete actions - it says 'optimize costs' but doesn't specify how (e.g., analyzing MAU, comparing tiers, auditing feature usage). The explicit trigger phrase list is a strong pattern that aids skill selection.
Suggestions
Add 2-3 specific concrete actions like 'analyze MAU usage patterns', 'compare pricing tiers', or 'identify cost-saving opportunities from unused features' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk costs/pricing) and mentions actions like 'optimize costs' and 'understand pricing', but lacks specific concrete actions like 'analyze MAU usage', 'compare pricing tiers', or 'identify unused features'. | 2 / 3 |
Completeness | Clearly answers both what (optimize Clerk costs, understand pricing) and when (planning budget, reducing costs, understanding pricing model) with explicit trigger phrases listed separately. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clerk cost', 'clerk pricing', 'reduce clerk cost', 'clerk billing', 'clerk budget'. These are realistic terms users would naturally use when seeking this help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Clerk (a specific authentication service) with distinct triggers. Unlikely to conflict with generic cost optimization or other SaaS pricing skills due to the explicit 'Clerk' qualifier throughout. | 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 skill provides highly actionable, executable code for Clerk cost optimization with five concrete strategies. However, it's verbose for a skill file, includes time-sensitive pricing data that will become stale, and lacks validation checkpoints for verifying cost changes took effect. The content would benefit from being split into an overview with references to detailed strategy files.
Suggestions
Move detailed strategy implementations to separate files (e.g., STRATEGIES.md) and keep SKILL.md as a concise overview with links
Add validation steps after implementing cost changes (e.g., 'Verify in Clerk Dashboard > Usage that session count decreased')
Move the pricing table to a separate PRICING.md file or add a note that pricing should be verified at clerk.com/pricing since it changes
Remove the 'What Counts as MAU?' section - Claude understands this concept and it's explained in Clerk's docs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., 'What Counts as MAU?' section explains basic concepts) and could be tightened. The pricing table with time-sensitive information (2024) and verbose code comments add bulk, though most content is relevant. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready. Each strategy includes concrete, working implementations with clear patterns for session optimization, guest users, feature gating, batching, and monitoring. | 3 / 3 |
Workflow Clarity | The checklist provides a clear sequence of actions, but lacks explicit validation checkpoints or feedback loops. For cost optimization involving billing changes, there should be verification steps to confirm changes took effect before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the skill is quite long (~250 lines) with all strategies inline. The detailed code examples for each strategy could be split into separate reference files, with SKILL.md providing an overview and links. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.