ops-marketing
Marketing command center. Email campaigns (Klaviyo), paid ads (Meta/Google), analytics (GA4), SEO, and social media metrics. One dashboard for all marketing channels.
Profile →npx skills add davepoon/buildwithclaude --skill ops-marketing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Orchestrates a marketing command center that pulls metrics from Klaviyo (email), Meta Ads, GA4, SEO via Search Console, and social channels, offering a unified dashboard and several sub-commands to manage and view data across channels.
How it works
- Defines a runtime context with preferences, daemon health, and secrets resolution before running channel queries.
- Supports a range of tools including Bash, Read, Write, Grep, Glob, Agent, TeamCreate, SendMessage, AskUserQuestion, WebFetch, WebSearch to perform data gathering and interactions.
- Provides sub-command routing to route user input to specific sections such as email/klaviyo, ads/meta, meta-manage, google-ads, analytics/ga4, seo/gsc, social, and others.
- For Klaviyo, executes REST API calls to fetch subscriber counts, recent campaigns, active flows, and key metrics, with a prescribed output format.
- For Meta Ads, fetches account spend, campaign breakdown, ROAS via action_values, and top ads, with a defined output format.
- For meta-manage, supports create-campaign, target, creative, rules, audiences, and advantage with credential checks and interactive prompts (AskUserQuestion).
- Includes credential resolution blocks for Klaviyo, Meta Ads, GA4, Google Search Console, and Google Ads, detailing environment and Doppler fallback steps.
When to use it
Use the full marketing dashboard command when no specific sub-command is provided or when a dashboard view is requested.
What it can touch
- Klaviyo API endpoints via REST calls
- Meta Graph API endpoints
- GA4 Data API
- Google Search Console endpoint
- Google Ads API (with token refresh and header setup)
- Local shell and curl/jq as instructed
Caveats
- Credential resolution requires configured keys or Doppler secrets; missing META_TOKEN or GA4 properties will halt certain actions. See credential blocks for specifics.
- Some commands require additional environment values (e.g., META_PAGE_ID for ad creative creation). If missing, the agent reports instructions to configure them.
- Uses interactive questions via AskUserQuestion for some actions (e.g., create-campaign, target, creative) to gather required inputs before API calls.
# OPS ► MARKETING COMMAND CENTER ## Runtime Context Before executing, load available context: 1. **Preferences**: Read `${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` - `timezone` — display all timestamps correctly - `klaviyo_private_key`, `meta_ads_token`, `meta_ad_account_id`, `ga4_property_id`, `google_search_console_site` — check userConfig keys bef
What does the ops-marketing skill do?
Marketing command center. Email campaigns (Klaviyo), paid ads (Meta/Google), analytics (GA4), SEO, and social media metrics. One dashboard for all marketing channels.
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill ops-marketing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.