CtrlK
BlogDocsLog inGet started
Tessl Logo

pricing-page

Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments). Includes checklists, templates, and common pitfalls.

70

Quality

85%

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.

The body is a well-structured, actionable design brief that assumes Claude's competence and gives copy-paste templates plus a concrete output spec. Its only gaps are minor repetition and the absence of error-recovery feedback loops, which are less critical for a non-destructive design task.

DimensionReasoningScore

Conciseness

Dense, list-driven, and free of padding about what SaaS or pricing pages are, with a couple of minor repetitions (CTA rules and checklists restate points) that keep it just below fully lean.

4 / 5

Actionability

Provides copy-paste-ready templates (headline formulas, plan-description examples, ❌/✅ bullet rewrites, CTA verb lists, checklists) and an explicit output format that cover the common cases concretely.

5 / 5

Workflow Clarity

Clear sequence from 'Before you design/write' through 'Core structure', strategies, copywriting, and an 'Output format', plus UI/SEO checklists; no destructive/batch ops so no validation cap, but no error-recovery feedback loops, capping it below 5.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with no nested references; at ~210 lines some material (template library, SEO/AEO detail) could arguably move to reference files, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

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

The description is strong: it explicitly states both the capability and the trigger condition, and occupies a well-defined niche. The only weakness is moderate trigger-term coverage and slightly abstract leading verbs.

DimensionReasoningScore

Specificity

Lists several concrete action areas in the parenthetical ('structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments'), but the leading verbs 'designing or rewriting' remain somewhat abstract, so it falls just below comprehensive.

4 / 5

Completeness

Explicitly answers both what ('designing or rewriting a high-converting SaaS pricing page') and when ('Use when designing or rewriting...') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural triggers like 'SaaS pricing page', 'FAQs', 'SEO/AEO', but misses common synonyms such as 'subscription page', 'plans page', or 'tier comparison', leaving a few natural terms out.

4 / 5

Distinctiveness Conflict Risk

'high-converting SaaS pricing page' carves a clear, narrow niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/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.