CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

offers

When the user wants to design or improve the offer itself, or asks why it isn't selling or how to add urgency honestly: value stacking, bonuses, guarantees, scarcity, payment plans, upsells. Best for services, courses, coaching, and high-ticket B2B; for self-serve SaaS, read pricing first. For price and tiers, see pricing. For the page, see copywriting. For the launch, see launch. For sales collateral, see sales-enablement.

Quality

92%

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

86%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 well-constructed instruction-only skill body: a fully executable diagnostic procedure with concrete numbers and decision rules, compact tables instead of prose, and exemplary progressive disclosure via a when-to-read reference table pointing to a real, one-level-deep bundle. The only trimmable fat is the philosophical/routing material that duplicates the frontmatter, and the workflow lacks an explicit failure-recovery loop.

DimensionReasoningScore

Conciseness

The body is dense with actionable specifics (the lever table, "plan on 10–40% relative lift", "+20% then +30% = 1.20 × 1.30 = 1.56", "~2× the rate of full-price customers") and explains nothing Claude already knows, but the Core Philosophy section and the When-this-matters/When-pricing lists restate routing already in the description and could be trimmed.

4 / 5

Actionability

The Diagnostic Loop is fully prescriptive ("score each of the four levers 1–10. The lowest is the binding constraint", "Pick one lever to fix this iteration", "Multiply the lifts, don't add them"), the lever table gives concrete moves per lever, and the Banned Vocabulary section pairs each banned pattern with a replacement rule ("Use specific numbers, named customers, concrete outcomes, real timelines").

5 / 5

Workflow Clarity

The 7-step numbered Diagnostic Loop has a clear sequence with embedded diagnostic checkpoints (score levers, audit anatomy) and a final validation step ("Confirm the combined offer with a test"), but there is no explicit error-recovery or iterate-on-failure feedback loop, which keeps it below the top anchor.

4 / 5

Progressive Disclosure

The body is a genuine overview: each framework section ends with a well-signaled pointer ("For the full framework... see references/value-equation.md"), and a Reference Library table lists all 8 reference files with per-file "When to read" guidance; all 8 files exist in references/ and contain no further nesting, so references are exactly one level deep.

5 / 5

Total

18

/

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.

An excellent routing description: explicit when-clause with natural trigger phrases, concrete capability list, and explicit boundary-setting against sibling skills in the same repo. Voice is third-person throughout, and the only weakness is slightly generic action verbs with a couple of unlisted offer components.

DimensionReasoningScore

Specificity

The description lists six concrete mechanisms — "value stacking, bonuses, guarantees, scarcity, payment plans, upsells" — plus applicable business types, but the action verbs ("design or improve the offer itself") are somewhat generic and components like naming and the core deliverable are unlisted, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly answers both what ("design or improve the offer itself: value stacking, bonuses, guarantees, scarcity, payment plans, upsells") and when ("When the user wants to design or improve the offer... or asks why it isn't selling") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It captures natural user phrasings — "why it isn't selling", "how to add urgency honestly" — alongside comprehensive domain synonyms (value stacking, bonuses, guarantees, scarcity, upsells), matching the kind of thing a user would actually say when they need this skill.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (offer construction vs. its expression) and explicitly routes edge cases to sibling skills — "for self-serve SaaS, read pricing first. For price and tiers, see pricing. For the page, see copywriting" — minimizing wrong-skill triggering.

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

coreyhaines31/marketingskills

Path

skills/offers/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.