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.

60

Quality

70%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/popup-cro/SKILL.md

The canonical home for this skill is popup-cro in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 strategy guide with concrete triggers, benchmarks, and required assessment/output checkpoints. It is efficient and clearly navigable, with only minor redundancy and a filler 'When to Use' line holding it back from the top band.

Suggestions

Remove or replace the generic 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.') with concrete applicability criteria.

Eliminate the redundancy between section 1 'Initial Assessment' and section 12 'Questions to Ask', which cover the same context-gathering questions.

Add an explicit validation/feedback checkpoint in the workflow (e.g., 'Before outputting, confirm the popup passes accessibility, frequency-cap, and Google interstitial checks') to push workflow clarity toward 5.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet-point guidance that assumes Claude's competence and avoids explaining what popups are, matching 'efficient; minor instances of over-explanation that could be trimmed'; not a 5 because the 'Questions to Ask' section duplicates 'Initial Assessment' and the vague 'When to Use' filler line adds little.

4 / 5

Actionability

Concrete specific guidance throughout — e.g., "30–60 seconds of active engagement", "25–50% scroll depth", "Email popup: 2–5%", and example headline patterns like "Get [result] in [timeframe]" — matches 'mostly executable guidance; concrete examples with minor gaps'; not a 5 because, being instruction-only, it lacks copy-paste-ready templates/code that would fully cover common cases.

4 / 5

Workflow Clarity

A clear sequenced flow from 'Initial Assessment (Required)' through trigger/copy/design/compliance to 'Output Format (Required)' with required checkpoints, matching 'clear sequence with most checkpoints present; minor validation gaps'; not a 5 because there is no explicit validate-then-fix feedback loop, though the destructive-ops cap does not apply to this strategy skill.

4 / 5

Progressive Disclosure

The body is well-organized into 12 numbered sections with a 'Related Skills' pointer to siblings and no nested references, matching 'good structure; most content appropriately placed; minor organization gaps'; not a 5 because all content is inline in one ~350-line file with no one-level-deep reference split, though the bundle directories are empty so there is nothing to reference.

4 / 5

Total

16

/

20

Passed

Description

66%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 specific and uses natural third-person language with good synonym coverage, but it omits any explicit 'Use when…' trigger guidance, which caps its completeness and limits its trigger utility.

Suggestions

Append an explicit 'Use when…' clause naming trigger phrases (e.g., 'Use when designing or optimizing popups, modals, slide-ins, banners, exit-intent overlays, or conversion-rate optimization for interruption UI').

Add the natural abbreviation 'CRO' and common phrases like 'exit intent', 'newsletter popup', and 'conversion rate' to broaden trigger-term coverage.

Differentiate from sibling skills by noting the boundary (e.g., 'for the form inside the popup, use form-cro') directly in the description.

DimensionReasoningScore

Specificity

"Create and optimize popups, modals, overlays, slide-ins, and banners" lists two concrete verbs applied to five specific artifact types with a stated outcome, matching the 'lists several specific actions; minor gaps' anchor; not a 5 because only two distinct verbs are used versus the multi-verb 5 anchor.

4 / 5

Completeness

It clearly states what ("Create and optimize popups, modals, overlays, slide-ins, and banners") but has no "Use when…" trigger clause, so per the judging guideline completeness is capped at 3; the trailing purpose clause only weakly implies when.

3 / 5

Trigger Term Quality

"popups, modals, overlays, slide-ins, and banners" plus "conversions" give good natural-term coverage with synonyms for interruption UI patterns, matching the 'good keyword coverage; a few natural terms missing' anchor; not a 5 because terms like "CRO", "conversion rate", "exit intent", and "newsletter popup" are absent.

4 / 5

Distinctiveness Conflict Risk

The popup/modal CRO niche is clearly distinct from generic skills, matching 'mostly distinct; minor overlap risk with closely related skills'; not a 5 because without explicit trigger phrases it could overlap with related CRO skills (page-cro, form-cro, banner skills).

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.