CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

91%

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

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

Excellent content: lean, dense, immediately actionable design guidance with templates, checklists, a defined output format, and an input-gathering fallback. The two residual gaps are the implicit (rather than explicit) workflow ordering and the absence of any reference-file split for the longer checklist/template sections.

Suggestions

Make the workflow explicit: add a short numbered 'How to use this skill' sequence (gather inputs → pick layout A–D → apply strategies → write copy → run checklists → return output format).

Move the SEO/AEO checklist and copywriting templates into a one-level-deep references file (e.g. references/copy-and-seo.md) to keep SKILL.md a tighter overview.

Add a brief decision cue for choosing between layouts (e.g. 'if value metric is usage → B; two personas → C') to sharpen the workflow's checkpoints.

DimensionReasoningScore

Conciseness

The body is almost entirely terse, high-signal bullets ('Bullets describe outcomes, not internal features'; 'keep math obvious; keep a safe default (median customer)') with zero padding and no explanation of concepts Claude already knows. Every line carries pricing-page-specific guidance that earns its tokens.

5 / 5

Actionability

For an instruction-only skill, the guidance is directly executable: copy-paste headline formulas ('{Outcome} for {audience}—without {pain}'), concrete plan-description examples, named FAQ questions, a UI checklist with specific item counts ('Key limits visible (3–6 max)'), and a defined output format enumerating five deliverables. No vague directives remain.

5 / 5

Workflow Clarity

A clear implicit sequence runs intake ('Before you design/write: Gather (ask if missing)') → core structure → layout choice ('pick one') → strategies → copy templates → checklists → 'Output format' deliverables, with fallback behavior ('Quick questions (if user gives you only “make a pricing page”)'). It stops short of anchor 5 because the sequence is carried by section order rather than explicit numbered steps or decision checkpoints; no validation loop is needed since the skill is non-destructive.

4 / 5

Progressive Disclosure

Single-file skill with no external bundle (references/, scripts/, assets/ absent) and a clean header hierarchy (before-you-design → structure → layouts → strategies → copy → checklists → SEO → pitfalls → output) that is easy to navigate. At ~210 lines it is not trivially small — the SEO/AEO checklist and copywriting templates are the most obvious candidates for one-level-deep reference files — so it fits anchor 4 (good structure, minor organization gaps) rather than 5.

4 / 5

Total

18

/

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.

A strong description: third-person, explicit 'Use when' trigger with enumerated sub-triggers, and concrete deliverables. The only weakness is that the parenthetical is a topic list rather than a list of distinct actions, leaving minor specificity and synonym gaps ('pricing table', 'plans', 'subscription tiers').

Suggestions

Add natural synonyms users might say, e.g. 'pricing table', 'plan tiers', or 'subscription pricing', to strengthen trigger coverage.

Convert one or two parenthetical topics into action verbs (e.g. 'design plan tiers and CTAs, write objection-handling FAQs') to sharpen the 'what'.

DimensionReasoningScore

Specificity

The description names concrete actions ('designing or rewriting a high-converting SaaS pricing page') and enumerates seven sub-areas ('structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments') plus three artifact types ('checklists, templates, and common pitfalls'). The listed items are topics/areas rather than distinct executable actions, so it falls just below the comprehensive anchor of 5.

4 / 5

Completeness

Both 'what' (design/rewrite high-converting pricing pages; includes checklists, templates, pitfalls) and 'when' ('Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments)') are explicitly stated with concrete trigger phrases. It is not the anchor-4 case because the when-clause enumerates specific trigger areas rather than being generic.

5 / 5

Trigger Term Quality

Natural user phrases are well covered: 'pricing page', 'SaaS', 'copywriting', 'SEO/AEO', 'FAQs', 'layout'. Common variations like 'pricing table', 'plans page', or 'subscription tiers' are missing, which keeps it just below the comprehensive-synonyms anchor of 5 but clearly above the sparse anchor of 3.

4 / 5

Distinctiveness Conflict Risk

A clear niche (SaaS pricing page design) with distinct triggers ('high-converting', 'plan design', 'pricing page') that would not plausibly route to another skill. Minimal overlap risk with generic web-design or copywriting skills since the scope is narrowly and explicitly priced.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MengTo/Skills

Path

agent-skills/web-design/pricing-page/SKILL.md

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.