CtrlK
BlogDocsLog inGet started
Tessl Logo

popup-cro

When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.

52

Quality

58%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/popup-cro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

27%

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

This skill reads more like a comprehensive textbook chapter on popup optimization than a concise, actionable skill for Claude. Its main strengths are thorough coverage of popup types, copy formulas, and a clear output format template. However, it is far too verbose, explains many concepts Claude already knows, lacks executable code examples, and dumps everything into a single monolithic file rather than using progressive disclosure.

Suggestions

Cut the content by at least 50%: remove the Core Principles section (obvious truths), trim the Experiment Ideas section to a brief list or move to a separate EXPERIMENTS.md file, and eliminate explanations of concepts like GDPR basics and accessibility fundamentals that Claude already knows.

Split content into multiple files: keep SKILL.md as a concise overview with the assessment flow and output format, then create separate files like TRIGGERS.md, COPY-FORMULAS.md, and EXPERIMENTS.md for detailed reference material.

Add concrete, executable examples: include actual HTML/CSS/JS snippets for common popup implementations, or at minimum provide complete copy examples with before/after comparisons rather than just formula templates.

Add explicit workflow with validation: create a numbered step-by-step process from assessment through delivery with checkpoints like 'Confirm trigger strategy matches traffic context before writing copy' and 'Verify mobile experience before finalizing design.'

DimensionReasoningScore

Conciseness

At ~350+ lines, this skill is extremely verbose. It explains many concepts Claude already knows (what exit intent is, what GDPR requires, basic accessibility principles, what a modal is). Sections like 'Core Principles' state obvious truths ('Too early = annoying interruption'). The experiment ideas section is a massive list of generic A/B test suggestions that don't add actionable value. Much of this could be cut by 60%+ without losing useful guidance.

1 / 3

Actionability

The skill provides structured frameworks (copy formulas, output format templates, trigger strategies) and some concrete examples of copy, but lacks executable code, specific implementation snippets, or copy-paste ready popup HTML/CSS/JS. It's more of a comprehensive reference guide with checklists than actionable step-by-step instructions. The output format section provides a useful template structure.

2 / 3

Workflow Clarity

There's a reasonable flow from initial assessment → principles → design → measurement → output, and the output format section provides clear deliverable structure. However, there are no explicit validation checkpoints, no feedback loops for iterating on popup performance, and the 'Initial Assessment' questions don't clearly sequence into the design process. The workflow is implicit rather than explicit.

2 / 3

Progressive Disclosure

This is a monolithic wall of text with no bundle files to reference. All content is inline in a single massive file—trigger strategies, design best practices, copy formulas, compliance, measurement, experiment ideas—all crammed into one document. The related skills section at the bottom references other skills but doesn't offload any of its own content. The experiment ideas section alone could be a separate reference file.

1 / 3

Total

6

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description with excellent trigger term coverage and explicit boundary-setting that distinguishes it from related skills. The 'when' guidance is thorough with both positive triggers and cross-references to adjacent skills. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., designing, A/B testing, configuring display rules) rather than just 'create or optimize.'

Suggestions

Add more specific concrete actions beyond 'create or optimize' — e.g., 'design exit-intent triggers, write modal copy, configure display timing and targeting rules, optimize lead capture flows.'

DimensionReasoningScore

Specificity

The description names the domain (popups, modals, overlays, etc.) and mentions 'create or optimize' as actions, but doesn't list multiple specific concrete actions like 'design exit-intent triggers, A/B test modal copy, configure display rules, optimize lead capture forms.' The actions remain somewhat general.

2 / 3

Completeness

Clearly answers both 'what' (create or optimize popups, modals, overlays, slide-ins, banners for conversion) and 'when' (explicit trigger terms listed, plus boundary conditions distinguishing it from form-cro and page-cro). The 'Use when' equivalent is present via 'When the user wants to...' and 'Also use when...'

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'popups,' 'modals,' 'overlays,' 'slide-ins,' 'banners,' 'exit intent,' 'popup conversions,' 'modal optimization,' 'lead capture popup,' 'email popup,' 'announcement banner,' and 'overlay.' These are terms users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with explicit boundary-setting: 'For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.' This cross-referencing actively reduces conflict risk with related skills and carves out a clear niche.

3 / 3

Total

11

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
freekmurze/dotfiles
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.