L1-partI/skill/analyzing-marketing-campaign/SKILL.md
Analyze weekly marketing campaign performance data across channels. Use when analyzing multi-channel digital marketing data to calculate funnel metrics (CTR, CVR) and compare to benchmarks, compute cost and revenue efficiency metrics (ROAS, CPA, Net Profit), or get budget reallocation recommendations based on performance rules.
npx skillsauth add https-deeplearning-ai/sc-agent-skills-files analyzing-marketing-campaignInstall 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.
Automated analysis of multi-channel marketing campaign data.
Expects campaign data in CSV format with these columns:
Calculate per channel:
Compare to user-provided benchmarks, report difference in percentage points and provide brief interpretation for each channel. If benchmarks are not provided, use these historical values:
| Channel | CTR | CVR | |---------|-----|-----| | Facebook_Ads | 2.5% | 3.8% | | Google_Ads | 5.0% | 4.5% | | TikTok_Ads | 2.0% | 0.9% | | Email | 15.0% | 2.1% |
Calculate per channel:
Compare to user-provided targets. If not provided, use these defaults:
Present results as tables with status indicators:
Funnel Analysis Table: | Channel | CTR Actual | CTR Benchmark | CTR Diff | CVR Actual | CVR Benchmark | CVR Diff |
Efficiency Analysis Table: | Channel | ROAS | Status | CPA | Status | Net Profit | Status |
Status indicators:
Follow each table with brief channel-by-channel interpretation highlighting key insights and recommended actions.
If user asks about budget reallocation, read references/budget_reallocation_rules.md for the complete decision framework including eligibility rules, performance-based actions, and constraints.
tools
Create learning paths for programming tools, and define what information should be researched to create learning guides. Use when user asks to learn, understand, or get started with any programming tool, library, or framework.
tools
Provides checklist for reviewing Typer CLI command implementations. Covers structure, Annotated syntax, error handling, exit codes, display module usage, destructive action patterns, and help text conventions. Use when user asks to review/check/verify a CLI command, wants feedback on implementation, or asks if a command follows best practices.
tools
Generate pytest tests for Typer CLI commands. Includes fixtures (temp_storage, sample_data), CliRunner patterns, confirmation handling (y/n/--force), and edge case coverage. Use when user asks to "write tests for", "test my CLI", "add test coverage", or any CLI + test request.
tools
Provides Typer templates, handles registration, and ensures consistency. ALWAYS use this skill when adding or modifying CLI commands. Use when user requests to add/create/implement/build/write a new command (e.g., "add edit command", "create search feature") OR update/modify/change/edit an existing command.