CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

popup-cro

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

Quality

73%

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/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 an efficient, well-structured, and highly actionable strategy reference for an instruction-only skill — no code absence penalty applies since the guidance is concrete and specific. Its main gaps are minor: a couple of filler sections, no worked example, and no progressive split of detailed material into reference files.

DimensionReasoningScore

Conciseness

The body is a dense, checklist-style reference with concrete heuristics and no explanations of concepts Claude already knows. Minor trimmable filler exists (the vacuous "When to Use" section saying only "This skill is applicable to execute the workflow or actions described in the overview" and the "You are an expert" roleplay preamble), keeping it just below the lean-efficiency anchor of a 5.

4 / 5

Actionability

Concrete, specific guidance throughout: numeric heuristics (30-60 second triggers, 25-50% scroll depth, 2-5% benchmarks, 7-30 day cooldowns), templated copy patterns ("Get [result] in [timeframe]"), a mandatory close-behavior spec, and a required output format. It is not a 5 because no fully worked end-to-end example of a complete popup recommendation is provided — guidance is directional rather than copy-paste complete.

4 / 5

Workflow Clarity

A clear required sequence is present: Initial Assessment (Required) establishes context first, then trigger/type/copy/design/frequency decisions, compliance checks, and a required Output Format acting as a completion checklist, supplemented by Questions to Ask. This is advisory (non-destructive, non-batch) work, so the missing-validation cap does not apply; it stays at 4 rather than 5 because no verification or feedback step (e.g., how to sanity-check a recommendation against benchmarks) exists.

4 / 5

Progressive Disclosure

Scored against the actual bundle structure: no reference files exist, and the single ~345-line body is well organized into twelve numbered sections with clear headers and cross-references to sibling skills (form-cro, page-cro) for boundary navigation. It is not a 5 because at this length some self-contained sections (copy framework examples, compliance details, popup type requirements) could be split into one-level-deep reference files to keep SKILL.md a leaner overview.

4 / 5

Total

16

/

20

Passed

Description

61%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 concise and names a distinct, well-bounded domain with a good enumeration of popup variants, but it lacks any explicit "Use when..." trigger guidance, which caps its completeness and weakens automatic skill selection. Adding a trigger clause with common user phrases would lift it substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions popups, exit intent, opt-in forms, newsletter capture, or wants to improve popup conversion rates."

Add natural trigger synonyms such as "exit intent", "opt-in", "email capture", and "newsletter popup" to broaden keyword coverage for user queries.

Expand the action list beyond "Create and optimize" to mention concrete capabilities like trigger strategy, copywriting, and frequency capping.

DimensionReasoningScore

Specificity

The description names the domain with strong synonym coverage ("popups, modals, overlays, slide-ins, and banners") and 1-2 concrete actions ("Create and optimize"), matching the anchor for a domain plus 1-2 actions that is not comprehensive. It stops short of listing several specific actions such as trigger design, copywriting, or frequency capping that would justify a 4.

3 / 5

Completeness

The "what" is clear (create and optimize popups and similar elements to increase conversions), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The scope boundary ("without harming user experience or brand trust") adds context but does not substitute for a when-to-use trigger.

3 / 5

Trigger Term Quality

Natural keywords users would actually say are present ("popups", "modals", "banners", "conversions"), giving good coverage. Common variations like "exit intent", "opt-in", "newsletter signup", or "email capture" are missing, so it falls short of the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The popup/modal/banner optimization niche is mostly distinct with specific object types named, creating clear trigger separation from generic skills. Minor overlap risk remains with closely related CRO skills (the body itself references form-cro and page-cro), which keeps it below a 5.

4 / 5

Total

14

/

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.

Validation — 15 / 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

Path

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