CtrlK
BlogDocsLog inGet started
Tessl Logo

popup-cro

Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.

52

Quality

57%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/popup-cro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Scale 1-5

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

This is a well-structured strategic guide for popup CRO that covers the domain comprehensively with good section organization and clear scope boundaries. However, it reads more like a reference document than an actionable skill—it lacks concrete examples (e.g., actual popup copy before/after), has no validation checkpoints or feedback loops for iterating, and contains redundancy between sections (Initial Assessment vs Questions to Ask). The content would benefit from being more concise and more actionable.

Suggestions

Add 1-2 concrete before/after examples showing a weak popup recommendation transformed into a strong one, with actual copy, to increase actionability.

Merge the 'Questions to Ask' section into 'Initial Assessment' to eliminate redundancy and improve conciseness.

Add explicit validation/feedback steps: e.g., after launching, check metrics at 48h, if conversion rate < X% then adjust trigger/copy, re-measure.

Remove or condense truistic principles like 'If the purpose is unclear, the popup will fail' and 'A perfectly designed popup shown at the wrong moment will fail'—Claude already understands these concepts.

DimensionReasoningScore

Conciseness

The skill is reasonably organized but contains significant verbosity for an instruction-only skill. Sections like 'Core Principles' state obvious truisms ('A perfectly designed popup shown at the wrong moment will fail'), and the 'Questions to Ask' section largely duplicates the 'Initial Assessment' section. The 'Common Mistakes' section restates guidance already covered. Several sections explain concepts Claude would already know.

3 / 5

Actionability

The skill provides structured checklists and frameworks (copy patterns, trigger strategies, output format) but lacks concrete, executable examples. There are no real popup copy examples showing before/after, no specific implementation code or tool commands, and the guidance remains at a strategic/checklist level rather than providing copy-paste-ready deliverables.

3 / 5

Workflow Clarity

There is a clear sequence implied (assess → choose trigger → select type → write copy → set rules → measure), and the output format section provides structure. However, there are no explicit validation checkpoints, no feedback loops for iterating on underperforming popups, and no clear decision tree for choosing between options. The workflow is implicit rather than explicitly sequenced.

3 / 5

Progressive Disclosure

The skill appropriately references related skills (form-cro, page-cro, email-sequence, ab-test-setup) with clear scope boundaries stated upfront. The content is well-sectioned with numbered headers. However, with no bundle files provided, the references to other skills are unverifiable, and some sections (like the full popup types catalog) could potentially be split into a reference file to keep the main skill leaner.

4 / 5

Total

13

/

20

Passed

Description

61%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 identifies a clear domain (popup/modal creation and optimization) with relevant trigger terms, but lacks an explicit 'Use when...' clause that would help Claude know precisely when to select this skill. The specificity of actions could be improved by listing concrete sub-tasks beyond the generic 'create and optimize'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about creating popups, modals, exit-intent overlays, newsletter signup forms, or optimizing on-site conversion elements.'

Expand concrete actions beyond 'create and optimize' — e.g., 'Design popup layouts, configure display triggers (exit intent, scroll depth, time delay), write compelling CTA copy, and A/B test variants.'

Include additional synonyms and related terms like 'lightbox', 'dialog', 'opt-in form', 'exit intent', 'CTA' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (popups/modals/overlays) and mentions two broad actions ('create and optimize'), plus goals ('increase conversions without harming user experience or brand trust'), but doesn't list specific concrete sub-actions like A/B testing, timing configuration, exit-intent triggers, or template generation.

3 / 5

Completeness

The 'what' is reasonably clear (create and optimize popups/modals/etc.), but there is no explicit 'when' clause or trigger guidance. The absence of a 'Use when...' clause caps this at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes several natural terms users would say: 'popups', 'modals', 'overlays', 'slide-ins', 'banners', and 'conversions'. Missing some common synonyms or related terms like 'lightbox', 'dialog', 'exit intent', 'CTA', 'opt-in form', or 'newsletter signup'.

4 / 5

Distinctiveness Conflict Risk

The combination of popup/modal UI elements with a conversion optimization focus creates a fairly distinct niche. There's minor overlap risk with general UI/UX skills or broader conversion optimization skills, but the specific element types help differentiate it.

4 / 5

Total

14

/

20

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
administrakt0r/AI-Agents-Safe-Coding-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.