CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

popups

When the user wants to create or improve popups, modals, slide-ins, sticky bars, and banners, or asks whether one will help or annoy and when to show it: exit intent, email capture, scroll and time triggers, announcements. For forms and pages outside popups, see cro.

Quality

78%

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/popups/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 rich, domain-knowledge-heavy body with genuinely specific CRO data and an explicit output format, but it is long and partially redundant, reads as a reference manual rather than a sequenced workflow, and keeps everything inline instead of splitting stable detail into reference files. The description is in much stronger shape than the body.

Suggestions

Merge the "Task-Specific Questions" section into "Initial Assessment" and cut bullets that restate common knowledge (easy dismiss, don't trap users, basic accessibility tenets) to reduce token spend.

Frame the body as an explicit ordered workflow (assess context, select type and trigger, draft copy, set frequency and compliance rules, produce the Output Format deliverable) with a final check that compliance and frequency rules are covered before emitting the recommendation.

Move the Experiment Ideas and Common Popup Strategies sections into one-level-deep reference files (e.g., references/experiments.md, references/strategies.md) and link them from a lean overview, since this material is lookup material rather than needed on every invocation.

DimensionReasoningScore

Conciseness

Mostly dense, useful bullets (benchmarks, copy formulas, trigger numbers), but the ~450-line body includes redundant question lists ("Initial Assessment" bullets vs the "Task-Specific Questions" section), ~90 lines of brainstorm experiment bullets, and reminders Claude already knows ("Easy to dismiss", "Don't trap or trick", generic accessibility tenets). Not 2 because the bulk is genuine domain expertise rather than padded explanation.

3 / 5

Actionability

Concrete guidance throughout: copy templates ("Get [result] in [timeframe]", decline options), specific numbers (30-60s delay, 25-50% scroll depth, 400-600px width, 2-5% benchmarks), and an explicit Output Format defining the deliverable. Not 5 because several sections stay abstract ("Address common objections", "Respect user choice") without worked examples.

4 / 5

Workflow Clarity

A clear starting step (read product-marketing context, assess purpose/state/traffic) and an implicit sequence (assess, choose trigger/type, design, copy, frequency, compliance, output) exist, but the process is never framed as an ordered procedure and there are no validation checkpoints (e.g., confirm compliance before finalizing the recommendation). Not 2 because the Initial Assessment section does sequence the intake; not 4 because checkpoints are absent.

3 / 5

Progressive Disclosure

No bundle files exist, so the entire knowledge base (experiment ideas, per-industry strategies, type-by-type playbooks) is inlined in a single ~450-line SKILL.md. Section headers and separators keep it navigable, but content that clearly belongs in one-level-deep reference files is inline, with no references to signal.

3 / 5

Total

13

/

20

Passed

Description

87%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.

A well-crafted description: third-person voice, explicit when-phrase with concrete triggers, broad format synonym coverage, and an explicit boundary clause to prevent mis-triggering against the sibling cro skill. The only gap is that a few natural synonyms (overlay, lightbox, interstitial) and the measurement/analysis side of the skill are unmentioned.

DimensionReasoningScore

Specificity

Names concrete actions ("create or improve") across a comprehensive list of formats (popups, modals, slide-ins, sticky bars, banners) and triggers (exit intent, scroll and time triggers). Not 5 because the action verbs stop at create/improve with no analysis or measurement capability stated; well past the 1-2 actions of anchor 3.

4 / 5

Completeness

Explicitly answers both questions: what ("create or improve popups, modals...") and when ("When the user wants to... or asks whether one will help or annoy and when to show it") with concrete trigger phrases. The when-clause is fully explicit rather than merely present, matching anchor 5 over anchor 4.

5 / 5

Trigger Term Quality

Strong natural keywords and synonyms users would actually say ("popups, modals, slide-ins, sticky bars, and banners", "exit intent", "email capture", "announcements"). Falls between anchors 4 and 5: coverage is good but common variants like "overlay", "lightbox", or "interstitial" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (popup/modal optimization) with an explicit boundary clause ("For forms and pages outside popups, see cro") that disambiguates from the sibling CRO skill. Minimal conflict risk with unrelated skills.

5 / 5

Total

18

/

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/popups/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.