CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/clerk-pack/skills/clerk-cost-tuning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 concrete, executable code and a clear step sequence, but it is weakened by content duplicated against an orphaned reference file, missing validation checkpoints on a batch cleanup operation, and a reference that is present but never linked from the body.

Suggestions

Link references/implementation-guide.md from the body (e.g., a '## Implementation guide' section) and move the duplicated pricing table and detailed strategies into it so SKILL.md stays a lean overview.

Add a validation/confirmation checkpoint to the Step 5 cleanup workflow (e.g., require explicit confirmation or a dry-run count before acting on inactive users) to satisfy the feedback-loop expectation for batch operations.

Fix the 'Next Steps' pointer to clerk-reference-architecture, which does not exist as a bundle file, or remove it to avoid a dead reference.

DimensionReasoningScore

Conciseness

The body is mostly efficient tables and executable code, but the pricing table and several optimization strategies (defer auth, caching, monitoring) are duplicated in references/implementation-guide.md, so tokens are spent on content that already lives in the bundle.

2 / 3

Actionability

Provides fully executable TypeScript with imports — middleware, caching, a monitoring endpoint, a cleanup script, and a cost estimator — that is copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced, but there are no validation or verification checkpoints, and the inactive-user cleanup (Step 5) is a batch operation without a confirm-before-acting feedback loop, which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

A reference file (references/implementation-guide.md) exists but is never linked or signaled from the body, and detailed content that belongs in that reference is instead inlined in SKILL.md; 'Next Steps' even points to a non-existent clerk-reference-architecture.

2 / 3

Total

9

/

12

Passed

Description

90%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.

A strong description: it states what the skill does, gives an explicit 'Use when' trigger, and lists natural trigger phrases scoped to a distinctive Clerk niche. The only weakness is that the headline actions ('optimize', 'understand') are somewhat abstract.

DimensionReasoningScore

Specificity

Names the domain ('Clerk costs') and two actions ('Optimize', 'understand pricing'), but 'optimize' and 'understand' are abstract rather than concrete actions, so it does not reach the 'multiple specific concrete actions' bar of a 3.

2 / 3

Completeness

Clearly answers both what ('Optimize Clerk costs and understand pricing') and when with an explicit 'Use when planning budget, reducing costs, or understanding Clerk pricing model' clause plus trigger phrases.

3 / 3

Trigger Term Quality

Lists natural phrases a user would actually say — 'clerk cost', 'clerk pricing', 'reduce clerk cost', 'clerk billing', 'clerk budget' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

A narrow Clerk-specific niche with distinct Clerk-prefixed triggers makes it unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.