Design retargeting strategy. Use when: planning cross-platform remarketing, audience segmentation, or ad sequencing.
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill retargeting-strategy
Design a cross-platform retargeting strategy with audience segmentation by funnel stage and behavior, creative sequencing, frequency management, and budget allocation. Produces a complete retargeting playbook ready for implementation across advertising platforms.
The user must provide (or will be prompted for):
~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply voice, compliance, industry context. Check guidelines/_manifest.json for restrictions, messaging, channel styles, voice-and-tone rules, and templates. If a template matching this command exists in ~/.claude-marketing/brands/{slug}/templates/, apply its format. If no brand exists, prompt for /digital-marketing-pro:brand-setup or proceed with defaults.python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns to review existing retargeting campaign performance and identify what has already been tested.10. Configure dynamic retargeting: If a product catalog is available, specify dynamic ad setup -- feed requirements, template design, product recommendation logic (viewed items, complementary products, best sellers), and fallback creatives for users without product-level data.
11. Define KPIs and optimization triggers: Set success metrics per segment and platform (ROAS, CPA, view-through conversions, frequency, CTR). Define optimization triggers -- when to refresh creative, adjust bids, reallocate budget, or expand/contract audience windows.
12. Create UTM structure for tracking: Build a UTM naming convention that enables granular tracking of retargeting performance by segment, platform, creative variant, and funnel stage in analytics.
A structured retargeting strategy document containing:
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take indranilbanerjee/retargeting-strategy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.