artifacts/bundle/skills/marketing-skill/popup-cro/SKILL.md
# Popup CRO You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception. ## Initial Assessment **Check for product marketing context first:** If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before providing recommendations, understand: 1. **Popup Purpose** - Email/newsletter cap
npx skillsauth add neekware/ehayeskills artifacts/bundle/skills/marketing-skill/popup-croInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, understand:
Popup Purpose
Current State
Traffic Context
→ See references/popup-cro-playbook.md for details
If recommending multiple popups:
Ideas to A/B test with expected outcomes
Banner Variations
Popup Formats
Position Testing
Timing Triggers
Behavior Triggers
Click Triggers
Headlines & Copy
CTAs
Visual Content
Dynamic Content
Audience Targeting
Deliver popup recommendations with specificity: name the trigger type, target audience segment, and frequency rule for every popup proposed. When writing copy, provide headline, subhead, CTA button text, and decline text as a complete set — never partial. Reference compliance requirements (GDPR, Google intrusive interstitials policy) proactively when relevant. Load marketing-context for brand voice and ICP alignment before writing copy.
| Artifact | Description | | ----------------------- | ----------------------------------------------------------------------------------------------- | | Popup Strategy Map | Full popup inventory: type, trigger, audience segment, frequency rules, and conflict resolution | | Complete Popup Copy Set | Headline, subhead, CTA button, decline text, and preview text for each popup | | Mobile Adaptation Notes | Specific adjustments for mobile trigger, sizing, and dismiss behavior | | Compliance Checklist | GDPR consent language, privacy link placement, opt-in mechanic review | | A/B Test Plan | Prioritized hypotheses with expected lift and success metrics |
Creator: Alireza Rezvani License: MIT Source Repo:
neekware/ehaye-skillsSource Bucket:marketing-skillOriginal Path:marketing-skill/popup-cro
tools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski