dataslayer-marketing-skills

Subagent that extracts content performance data from GA4 and Search Console via Dataslayer MCP. Returns structured findings only, no interpretation or recommendations.

Subagent that extracts organic search data from Search Console and GA4 via Dataslayer MCP. Returns structured findings only, no interpretation or recommendations.

Subagent that extracts paid media data from Google Ads, Meta Ads, and LinkedIn Ads via Dataslayer MCP. Returns structured findings only, no interpretation or recommendations.

Subagent that extracts subscription health and retention data from Stripe (and optionally internal database) via Dataslayer MCP. Returns structured findings only, no interpretation or recommendations.

Internal development tool that performs a comprehensive quality audit of all marketing skills and agents. Reviews description overlap, format consistency, feature adoption, and structural patterns. Use when the user says "audit skills", "skill quality review", "check skill health", "are my skills consistent", "monthly skill review", or before releasing a new version of the skills repo.

Use this skill when the user wants a strategic, cross-functional analysis that connects paid, organic, content, and retention into one unified view. This is NOT a weekly summary — it is a decision engine that finds the hidden connections between channels. Activate when the user says "full marketing review", "how is everything doing", "weekly brain", "give me the full picture", "marketing intelligence report", "what should I focus on this week", "retention and acquisition together", "connect the dots across channels", or any request that implies synthesizing all marketing dimensions into one strategic recommendation. Do NOT use for simple weekly overviews or single-channel questions — those belong to ds-channel-report or the individual channel skills. This skill launches parallel subagents. Works best with Dataslayer MCP connected. Also works with manual data.

Use this skill when the user wants a quick, factual weekly or periodic overview of marketing metrics across channels. This is a lightweight report with numbers and anomalies — no subagents, no strategic synthesis. Activate when the user says "weekly report", "how did we do this week", "give me a marketing summary", "cross-channel report", "what happened with our marketing", "channel performance", "marketing digest", "weekly metrics", or asks for a combined view of organic and paid results. Do NOT use when the user wants strategic recommendations or cross-channel connections — that belongs to ds-brain. Works best with Dataslayer MCP connected. Also works with manual data.

Use this skill when the user wants to identify accounts at risk of churning, understand why users are cancelling, or find early warning signals before churn happens. Activate when the user says "churn analysis", "who might cancel", "accounts at risk", "why are people leaving", "usage drop", "inactive accounts", "retention analysis", "predict churn", or asks about subscription health, cancellation patterns, or which users are disengaged. Works best with Dataslayer MCP connected (Stripe + analytics). Also works with manual data.

Use this skill when the user wants to understand how their blog or content is performing in terms of traffic, engagement, and conversions. Activate when the user says "how is our blog doing", "which posts are driving trials", "content performance", "is our content working", "what should we write next", "which articles bring the most signups", "content audit", "blog SEO", "content SEO performance", or asks about the relationship between content and registrations or conversions. Works best with Dataslayer MCP connected (GA4 + Search Console). Also works with manual data.

Internal development tool that tests whether skill descriptions trigger correctly for different user inputs. Reads test cases from a YAML file and evaluates each one by matching the input against all skill descriptions. Use when the user says "run triggering eval", "test skill descriptions", "check triggering accuracy", "eval skills", or after editing a skill description to verify it still triggers correctly.

Internal development tool that validates all SKILL.md and agent .md files against the Claude Code spec. Checks frontmatter completeness, field validity, allowed-tools presence, line count, hardcoded paths, and description quality. Use when the user says "lint skills", "validate skills", "check skill quality", "run the linter", "are my skills valid", or before shipping changes to the skills repo.

Use this skill when the user wants to audit, review, or diagnose their paid media campaigns. Activate when the user says "audit my campaigns", "check my Google Ads", "why is my CPA high", "review my paid media", "what's wrong with my ads", "analyze my campaigns", or asks about campaign performance on Google Ads, Meta, LinkedIn Ads, TikTok Ads, or any other paid channel. Works best with Dataslayer MCP connected. Also works with manual data.

Use this skill when the user wants to generate a professional PDF report for a client or for internal use. Activate when the user says "generate a PDF report", "create a client report", "export to PDF", "make a report for my client", "monthly report PDF", "branded report", or any request that implies a downloadable, shareable, professional document with marketing performance data. Works best with Dataslayer MCP connected. Also works with manual data. Reads branding config from dataslayer-config.json if present.

Use this skill when the user wants to review organic search performance, identify SEO opportunities, or diagnose ranking drops. Activate when the user says "SEO report", "how is our organic doing", "check Search Console", "why did we lose rankings", "find quick wins for SEO", "which queries should we target", "impressions dropped", "CTR is low", or any question about organic traffic, rankings, or search visibility. Works best with Dataslayer MCP connected (Search Console + GA4). Also works with manual data.