CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-pricing

When the user wants to price an AI product, choose a charge metric, design pricing tiers, or optimize margins. Also use when the user mentions 'AI pricing,' 'usage-based pricing,' 'consumption pricing,' 'outcome pricing,' 'BYOK,' 'bring your own key,' 'per-seat pricing,' 'pricing tiers,' 'AI margins,' 'cost per token,' or 'pricing model.' This skill covers pricing strategy, packaging, and margin management for AI-native products. Do NOT use for technical implementation, code review, or software architecture.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, information-dense body: actionable decision frameworks, concrete pricing templates with real vendor examples, and well-signaled one-level-deep references that verifiably cover their claimed topics. Main improvement areas are moving dated statistics and vendor deep dives into references, and making the end-to-end pricing workflow explicit as one sequenced procedure.

Suggestions

Move dated market statistics ('126% growth in credit-model adoption', '27% to 41% of B2B companies, Growth Unhinged 2025') into references/implementation-guide.md or a timestamped section, so the main body does not go stale.

State the full workflow as one explicit numbered procedure (discovery questions, choose charge metric, match archetype, set tiers, design hybrid, validate with win/loss data) instead of leaving the sequence implicit in section order.

Move vendor pricing deep dives (GitHub Copilot tier evolution, Salesforce Agentforce credit math) into references/implementation-guide.md and consolidate both reference pointers into a single clearly-headed 'Further reading' section.

DimensionReasoningScore

Conciseness

The body is dense and table-driven, with nearly every line carrying domain-specific data Claude cannot be assumed to know (real price points, margin bands, vendor examples). Minor deductions: dated market statistics sit inline ('126% growth in credit-model adoption from end of 2024 to end of 2025', '27% to 41% of B2B companies... Growth Unhinged 2025') rather than in a reference, and a few sentences restate inferable points ('Per-seat works for copilots because the value unit is the empowered human'). Fits anchor 4 (efficient with minor trimmable over-explanation) rather than 3, since padding is limited.

4 / 5

Actionability

Fully actionable for an instruction-only skill: an ASCII charge-metric decision tree, tier templates with concrete price ranges, a 5-step outcome-pricing design table, a STEP 1-4 hybrid design recipe, worked user-query examples with expected results, and cause/fix troubleshooting entries. Specific numbers throughout ('1-500: $0.99, 501-2000: $0.79', 'overage at 1.2-2x your unit cost').

5 / 5

Workflow Clarity

Strong sequencing elements exist (the 'Before Starting' discovery checklist, the metric decision tree, the STEP 1-4 hybrid design procedure, troubleshooting as a feedback mechanism), but the overall end-to-end flow (discover context, pick metric, match archetype, design tiers, build hybrid) is implied by section order rather than stated as one explicit ordered procedure, and validation checkpoints like 'revalidate with win/loss and willingness-to-pay' appear only inside troubleshooting. Anchor 4 fits; not 5 because explicit checkpoints and feedback loops are not woven through the main workflow.

4 / 5

Progressive Disclosure

Both referenced bundle files exist, are one level deep, and are clearly signaled with explicit topic lists ('For hybrid pricing, BYOK, margin management, tier design, GTM impact, migration... read references/implementation-guide.md'; 'For checklists, benchmarks, and discovery questions read references/quick-reference.md'), and spot-checks confirm they cover the claimed topics. Minor gaps: substantial vendor deep dives (GitHub Copilot tier evolution, Salesforce credit math) are inlined in SKILL.md where the reference pattern suggests they belong, and the quick-reference pointer is oddly placed after Troubleshooting rather than in a structured 'further reading' section. Anchor 4, not 5, because content split is good but not clean.

4 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

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, well-structured description: explicit what/when, rich natural trigger terms with synonyms, and clear negative boundaries. The only minor gap is that a few sizable body topics (hybrid model design, pricing migration) are not reflected in the action list.

DimensionReasoningScore

Specificity

Lists several concrete actions ('choose a charge metric, design pricing tiers, or optimize margins') plus a domain-coverage clause ('pricing strategy, packaging, and margin management for AI-native products'), but omits significant body topics like hybrid model design and pricing migration — minor gaps that fit anchor 4 rather than the comprehensive coverage of anchor 5.

4 / 5

Completeness

Explicitly answers both 'when' ('When the user wants to price an AI product... Also use when the user mentions...') and 'what' ('This skill covers pricing strategy, packaging, and margin management for AI-native products'), with concrete trigger phrases and an explicit exclusion clause ('Do NOT use for technical implementation, code review, or software architecture').

5 / 5

Trigger Term Quality

Comprehensive natural trigger list including synonyms and both abbreviation and spelled-out forms ('BYOK,' 'bring your own key,' 'usage-based pricing,' 'consumption pricing,' 'outcome pricing,' 'per-seat pricing,' 'cost per token,' 'pricing model') — users would naturally say these when they need this skill.

5 / 5

Distinctiveness Conflict Risk

Clear niche (AI product pricing) with distinct, unambiguous triggers and an explicit negative-trigger clause that prevents firing for technical implementation or code review tasks — minimal conflict risk with other skills.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/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.