indranilbanerjee
UserAn open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable outputs.
Categories
Indexed Skills (93)
check
Run the unified pre-publish quality gate on marketing content — wraps scripts/eval-runner.py to score hallucination risk, claim substantiation (with --evidence), brand-voice fit (with --brand), structure (with --schema), content quality, and readability, plus a C2PA provenance check for AI assets in EU-targeted campaigns; returns a composite score with a PASS / WARN / BLOCKED decision and per-issue fix suggestions. Reports only — it never edits the content. Triggers on "/digital-marketing-pro:check", "is this safe to publish", "run a hallucination check on this draft", "validate this copy against the brand voice", "pre-publish quality gate". Resolves the active brand profile automatically; pairs with /digital-marketing-pro:c2pa-metadata to fix missing manifests.
client-validation-document
Produce the Part 5 Client Validation Document — the one true stop of the 12-Part engagement where unbiased v1 findings from Parts 2-4 are compiled into 12-25 evidence-cited finding blocks, each awaiting an ACCEPT / REJECT / EDIT / DEFER client decision, plus a paired JSON response template. Recorded responses feed the Part 6 Decision Matrix (engagement-state.py) to determine v2 re-runs. Triggers on "/digital-marketing-pro:client-validation-document", "prepare v1 findings for client review", "run part 5 client validation", "the one true stop", "record the client's validation responses". Requires Parts 3-4 marked completed in _engagement.json; reads the eight v1 core documents; pairs with /digital-marketing-pro:engagement-workflow and /digital-marketing-pro:four-core-documents.
continuous-improvement-loop
Run Part 12 of the engagement methodology — the continuous improvement loop that aggregates quarterly-review, customer-feedback, competitive, and operating signals into a Quarterly Product & Offering Improvement Brief for business leadership, plus fast 1-3 page ad-hoc briefs when a significant signal lands mid-quarter. Triggers on "/digital-marketing-pro:continuous-improvement-loop", "run part 12", "produce the quarterly improvement brief", "aggregate this quarter's signals", "we need a fast read on this competitor move". Flags v2.x update-back triggers but never auto-executes them. Reads monthly reports, signals.jsonl, /digital-marketing-pro:competitor-monitor outputs, and the Living Project Instruction File.
campaign-audit
Inventory and score everything currently running for a brand across paid search, paid social, email, organic, SEO, AEO/GEO, CRM, and analytics — produces a dated audit document with a 4-tier triage (healthy / quick win / strategic gap / red flag), a quick-wins backlog, and a compliance posture section. Strictly read-only: it never pauses, edits, or launches anything. Triggers on "/digital-marketing-pro:campaign-audit", "what's currently running for this brand", "audit our existing campaigns", "we just inherited this account", "where is budget leaking". Requires a validated brand profile (run validate-profile first); missing connectors degrade gracefully into findings. Feeds /digital-marketing-pro:campaign-plan and pairs with /digital-marketing-pro:performance-check.
ab-test-plan
Design a statistically rigorous A/B or multivariate test plan — If/Then/Because hypothesis, control and variant specs, required sample size per variant (absolute vs relative MDE via sample-size-calculator.py), test duration, guardrail metrics, stopping rules, and go/no-go decision criteria. Triggers on "/digital-marketing-pro:ab-test-plan", "set up an A/B test", "how long should my test run", "calculate sample size for an experiment", "is this test result significant". Reads the brand profile and past campaign-tracker results to avoid re-testing validated hypotheses; finished tests are evaluated with significance-tester.py by the cro-specialist agent.
ad-creative
Generate 3-5 ad copy variations per platform — headlines, descriptions, and CTAs formatted to Google, Meta, LinkedIn, TikTok, X, and Pinterest specs — each scored 1-10 with policy-compliance flags, A/B testing groupings, and a message-match check against the landing page. Triggers on "/digital-marketing-pro:ad-creative", "write ad copy for Meta", "give me RSA headline variations", "we need LinkedIn ad copy", "draft TikTok ad creative". Reads the brand profile, guidelines, and compliance rules; routes video ad scripts to /digital-marketing-pro:video-script and gates AI-generated visuals for EU campaigns through /digital-marketing-pro:c2pa-metadata and /digital-marketing-pro:check.
connect
Guide the connection of a known MCP integration to the plugin — looks up the connector registry via connector-status.py, checks current status, and returns transport-specific setup steps (OAuth for HTTP connectors, env-var credentials plus the exact .mcp.json block for npx connectors), verification steps, and the skills each connector unlocks. Triggers on "/digital-marketing-pro:connect", "connect Google Ads", "hook up Slack to the plugin", "set up the HubSpot integration", "how do I add Mailchimp". Guidance and status checks only — the user adds credentials themselves; unknown or custom servers route to /digital-marketing-pro:add-integration.
content-brief
Create a production-ready content brief a writer can execute without extra context — keyword map (primary, secondary, related questions), H2/H3 outline with key points and word-count targets, brand voice guidance, on-page SEO checklist, visual/media spec with AI-generation and C2PA provenance notes, and success metrics. Triggers on "/digital-marketing-pro:content-brief", "write a brief for this topic", "brief a blog post on X", "what should this article cover", "outline and SEO requirements for a pillar page". Preferred upstream of /digital-marketing-pro:content-engine. Reads the brand profile, guidelines, and compliance rules.
content-decay-scan
Scan the content library for decay — declining traffic, falling keyword positions, stale content, broken links, lost AI citations — scoring each URL 0-100 via creative-fatigue-predictor.py and ranking refreshes by recoverable revenue, with actionable refresh briefs and traffic-recovery estimates for top-priority tiers. Triggers on "/digital-marketing-pro:content-decay-scan", "which content is losing traffic", "find stale content to refresh", "our blog traffic keeps dropping", "prioritize content refreshes". Pulls performance data from Google Analytics/Search Console MCPs or exported CSVs; cross-reference causes with /digital-marketing-pro:seo-drift. Reads the brand profile for content strategy context.
content-engine
Draft marketing content in brand voice — blog posts, ad copy, email sequences, social posts, landing pages, and brand-voice guides — through a gated pipeline (research, outline, draft, fact-check, humanize, voice check, SEO checklist) with numbered working files and a five-gate quality scorecard before copy is publish-ready. Triggers on "/digital-marketing-pro:content-engine", "write a blog post about X", "draft ad copy for this campaign", "create an email sequence", "landing page copy for our product". Takes /digital-marketing-pro:content-brief as preferred upstream; hands off to /digital-marketing-pro:publish-blog, /digital-marketing-pro:content-repurpose, and /digital-marketing-pro:check. Reads the brand profile, guidelines, platform specs, and compliance rules.
context-engine
Load and manage the shared marketing context other skills build on — the active brand profile (voice, audiences, competitors, goals), industry benchmark profiles, geographic and industry compliance rules, platform specs, and scoring rubrics — plus brand switching and campaign-data persistence under ~/.claude-marketing/. Triggers on "/digital-marketing-pro:context-engine", "switch to brand X", "what are the benchmarks for my industry", "which compliance rules apply to us", "load my brand context". Pairs with /digital-marketing-pro:brand-setup to create profiles and /digital-marketing-pro:switch-brand to change them; its reference files are read by nearly every sibling skill.
cowork-setup
One-shot setup that wires Digital Marketing Pro for team use in Anthropic Cowork — verifies the sandbox via plugin-metadata.py, checks a Google Drive MCP is connected, creates the canonical Drive folder skeleton (_brands/, _runs/, _plans/), and writes the routing config via drive-sync-state.py so brand profiles, plans, and run checkpoints persist across sessions. Triggers on "/digital-marketing-pro:cowork-setup", "set up DMP for my team in Cowork", "brand profiles aren't persisting between sessions", "route outputs to our shared Drive", "first-time Cowork install". Run once per team; in local Claude Code it only offers optional Drive mirroring. Pairs with /digital-marketing-pro:brand-setup next and /digital-marketing-pro:doctor to verify routing.
creative-testing-framework
Design a structured ad creative testing playbook — prioritized variable matrix, isolated test grid, script-computed sample sizes and minimum budgets per variant, holdout control design, iteration cadence, and winner selection criteria. Plans the testing program; it does not launch or edit live ads. Triggers on "/digital-marketing-pro:creative-testing-framework", "design an A/B test for our ads", "our ad creatives fatigue too fast", "build a creative testing roadmap", "how many conversions per variant do we need". Reads the brand profile and guidelines, and pairs with /digital-marketing-pro:c2pa-metadata for AI-generated variants headed to EU placements.
crm-sync
Sync marketing data to and from Salesforce, HubSpot, Zoho, or Pipedrive — contacts, deals, and campaign links with field mapping, deduplication, consent checks, batched execution behind a mandatory approval gate, and a rollback manifest. Produces a full sync report with per-record outcomes. Triggers on "/digital-marketing-pro:crm-sync", "push these contacts into HubSpot", "sync deals to Salesforce", "our CRM and marketing lists don't match", "set up a recurring CRM sync". Reads the brand profile and compliance rules; for scored lead imports use /digital-marketing-pro:lead-import instead.
add-integration
Walk through adding a custom MCP server integration to the plugin — searches npm for an existing MCP package (or scaffolds a custom server from the plugin's guide), generates the exact .mcp.json entry, sets up environment-variable credentials, tests connectivity, and documents the tools the new server exposes. Triggers on "/digital-marketing-pro:add-integration", "connect Ahrefs to the plugin", "add a new MCP server", "integrate our internal API", "hook up Stripe data". Reads the brand profile and agency credential profiles at ~/.claude-marketing/credentials/ to map client-specific keys; custom builds follow skills/context-engine/custom-mcp-guide.md.
aeo-audit
Audit how a brand appears across the 6 canonical AI answer surfaces — ChatGPT, Perplexity, Google AI Mode, AI Overviews, Gemini, Copilot — probing 10-25 queries into a numbered output bundle with per-platform visibility scorecards, citation-accuracy checks, a competitor matrix, content gaps, and an optimization playbook behind a four-gate quality scorecard. Triggers on "/digital-marketing-pro:aeo-audit", "does ChatGPT know about our brand", "check our AI search visibility", "how does Perplexity describe us", "are we showing up in AI Overviews". Reads the brand profile; reconciles probes against GSC actuals via /digital-marketing-pro:gsc-ai-performance and defines the AI-visibility scoring standard reused by geo-monitor and share-of-voice.
agency-dashboard
Generate a portfolio-level dashboard across ALL client brands — per-client RAG health scores, campaign activity, budget pacing, aggregate KPIs, team utilization, pending approvals, upcoming deadlines, and an alerts panel — built for agency standups and weekly reviews. Triggers on "/digital-marketing-pro:agency-dashboard", "how are all our clients doing", "portfolio health check", "budget pacing across accounts", "which accounts are at risk". Enumerates every brand under ~/.claude-marketing/brands/ and pulls data via campaign-tracker.py, execution-tracker.py, and team-manager.py; drill into a single client with /digital-marketing-pro:performance-report or /digital-marketing-pro:client-report.
audience-profile
Build a named, narrative buyer persona document — demographic snapshot, psychographic drivers, jobs-to-be-done, day-in-the-life scenario, buyer journey map, objections with counter-messaging, and content/channel preferences — for the 2-4 personas a brand actually needs. Triggers on "/digital-marketing-pro:audience-profile", "create a buyer persona", "profile our target customer", "who is our ideal customer", "map the buyer journey for this segment". Reads the brand profile, guidelines, and any customer data supplied (surveys, CRM exports, analytics demographics); run by the marketing-strategist agent. For the deeper research module — segmentation, anti-personas, buying committees — see /digital-marketing-pro:audience-intelligence.
backlink-gap
Find referring domains that link to your competitors but not to you, ranked by an outreach-priority score (0.40 DR + 0.25 link-overlap + 0.20 traffic + 0.15 topical relevance) — outputs a four-gate quality scorecard, a 30-prospect outreach shortlist, broken-link candidates, and pre-filled outreach templates. Triggers on "/digital-marketing-pro:backlink-gap", "where are competitors getting links we aren't", "plan a link-building campaign", "quarterly backlink audit", "first 50 link targets for a new client". Consumes backlink CSV exports from the brand's connected backlink MCP, runs scripts/backlink_gap.py, reads the brand profile for DR thresholds and voice, and hands off to /digital-marketing-pro:digital-pr and /digital-marketing-pro:pr-pitch.
brand-setup
Create or update the brand profile every other skill reads — a quick 5-question or full 17-question interactive setup capturing identity, business model, industry and compliance markets, 4-dimension voice scales, channels, goals, and competitors, saved to ~/.claude-marketing/brands/{slug}/profile.json via scripts/setup.py. Triggers on "/digital-marketing-pro:brand-setup", "set up a new brand", "onboard a new client", "switch to another brand", "update our brand voice". Also handles brand switching (updates _active-brand.json) and field-level profile edits; run this first — all marketing skills auto-apply the resulting profile, voice samples, and compliance rules.
budget-optimizer
Reallocate marketing spend across channels using performance data and diminishing-returns modeling — produces a current-vs-optimized allocation table, projected ROI ranges with confidence intervals, a phased 4-8 week reallocation timeline, and a 10-15% testing reserve. Recommends shifts only; it never changes spend on any platform. Triggers on "/digital-marketing-pro:budget-optimizer", "optimize my marketing budget", "which channels should get more spend", "reallocate budget based on ROAS", "is our channel split right". Reads the brand profile and guidelines, runs scripts/budget-optimizer.py, and pairs with /digital-marketing-pro:budget-tracker for in-flight pacing.
campaign-plan
Generate a complete multi-channel campaign plan document — SMART objectives, audience segments with targeting criteria, channel mix with rationale, a budget allocation table with reach/cost estimates, a phased timeline from pre-launch to wrap-up, a KPI framework, and a risk register. Plans only; it does not launch or modify campaigns. Triggers on "/digital-marketing-pro:campaign-plan", "plan a campaign for our product launch", "build the Q3 campaign plan", "what channels and budget for lead gen", "draft a campaign timeline with KPIs". Reads the brand profile, guidelines, and agency SOPs, and reuses the /digital-marketing-pro:campaign-orchestrator reference docs for planning frameworks instead of re-deriving them.
case-study-plan
Build a complete case-study creation blueprint — a Challenge-Solution-Results narrative framework, 15-20 client interview questions plus 10 internal-team questions, a data-visualization plan, format specifications (PDF, web page, slide deck, video script outline, social snippets, sales one-pager), a distribution strategy, a permission/approval checklist, and a draft executive summary. Plans the case study; it does not produce the finished designed asset. Triggers on "/digital-marketing-pro:case-study-plan", "turn this client win into a case study", "what should we ask the client in the interview", "plan a success story for sales enablement", "case study formats and distribution plan". Reads the brand profile, guidelines, custom templates, and agency SOPs.
competitor-analysis
Run a multi-dimensional competitive teardown of 2-5 competitors — content strategy, SEO, paid ads, social, AI answer-engine visibility, and pricing/positioning — producing a competitor overview matrix, per-competitor SWOT, gap analysis, and strategic recommendations prioritized by opportunity size. Triggers on "/digital-marketing-pro:competitor-analysis", "analyze our competitors", "how do we stack up against X", "competitive landscape report", "what are competitors doing that we aren't". Point-in-time analysis, not ongoing tracking — pair with /digital-marketing-pro:competitor-monitor for that. Reads the brand profile, guidelines, and compliance rules.
competitor-pages
Build competitor comparison and alternatives pages — X-vs-Y head-to-heads, alternatives-to-X lists, category roundups, and feature-matrix pages — delivering a 1,500+ word page template, comparison table, JSON-LD schema via schema-generator.py, keyword and title-tag targeting, an internal-linking plan, and fairness/accuracy guardrails. Triggers on "/digital-marketing-pro:competitor-pages", "create a vs page", "build an alternatives page", "comparison page for our product", "best tools roundup for our category". Produces page content and markup, not a live publish. Reads the brand profile and guidelines, especially restrictions on competitor mentions.
content-calendar
Generate a structured content calendar for a month, quarter, or custom range — topics mapped to platforms and publish dates, content-pillar and funnel-stage tags, repurposing chains from each core piece, SEO keyword targets, and owner assignments when team capacity is given. Triggers on "/digital-marketing-pro:content-calendar", "plan next month's content", "build a quarterly editorial calendar", "what should we publish in March", "map our content pillars to a schedule". Planning output only — it does not schedule or publish posts. Reads the brand profile, guidelines, and compliance rules for pillars and voice.
credential-switch
Switch the active credential profile to a different client brand, validating each configured platform's API keys, env vars, and token expiry before anything runs — preventing cross-client data leaks and misrouted ad spend. Outputs a per-platform validation report plus a logged switch confirmation with audit trail. Triggers on "/digital-marketing-pro:credential-switch", "switch to the other client's account", "activate Acme's API keys", "are the right credentials active", "change which brand we're working on". Reads brand and credential profiles under ~/.claude-marketing/ and pairs with /digital-marketing-pro:client-onboarding when a profile is missing.
crisis-response
Assess a PR crisis and deliver a structured response plan — severity classification (Level 1-3), a ready-to-publish holding statement, tailored messaging per stakeholder group, an hour-by-hour communication timeline, and a trust-rebuilding roadmap. Drafts and plans only; it publishes nothing. Triggers on "/digital-marketing-pro:crisis-response", "we're getting slammed on social media", "draft a holding statement fast", "a negative story just broke about us", "how do we respond to this backlash". Reads the brand profile, voice settings, guidelines, and market compliance rules before drafting any statement.
analytics-insights
Marketing measurement module — builds KPI trees per business model, reporting templates (weekly, monthly, QBR, campaign), anomaly root-cause diagnosis, MMM and incrementality guidance, dark-social tracking, and privacy-first cookieless measurement architecture, including the GA4 AI Assistant channel group for attributing AI-referred traffic. Triggers on "/digital-marketing-pro:analytics-insights", "why did traffic drop", "define our KPIs", "design an executive dashboard", "can we do marketing mix modeling". Reads the brand profile, industry benchmarks, and campaign history; pairs with /digital-marketing-pro:gsc-ai-performance and /digital-marketing-pro:aeo-audit to triangulate AI-surface impressions against actual traffic.
audience-intelligence
Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle segmentation models, anti-personas with exclusion criteria, B2B buying-committee maps, and lookalike seed specs. Triggers on "/digital-marketing-pro:audience-intelligence", "who are our customers", "build buyer personas", "segment our audience", "run a JTBD analysis". Reads the brand profile, industry benchmarks, and campaign history, and works from CRM/survey/analytics data when supplied — or labels hypothesis personas explicitly when data is thin. For a single quick persona document, /digital-marketing-pro:audience-profile is the lighter sibling.
c2pa-metadata
Embed a C2PA provenance manifest into an AI-generated marketing asset (PNG, JPG, WebP, GIF, TIFF, MP4, MOV, WebM, MP3, WAV, PDF) via scripts/embed-c2pa.py — produces a signed copy of the file carrying IPTC digital-source-type AI claims, an optional c2pa.ai-disclosure assertion for EU AI Act Article 50 (applicable 2 Aug 2026), and a JSON status report. Triggers on "/digital-marketing-pro:c2pa-metadata", "sign this AI image for EU compliance", "add content credentials to this asset", "embed provenance metadata", "mark this video as AI-generated". Uses a self-signed dev certificate unless --signing-cert/--signing-key are supplied; pairs with /digital-marketing-pro:check, which verifies manifests pre-publish.
campaign-orchestrator
Full campaign-lifecycle module — produces campaign briefs, budget allocations via three models (70/20/10, efficiency-ranked, funnel-weighted), channel-mix and media plans, UTM taxonomies with governance rules, launch checklists, ABM plans, and post-mortem reports. Plans and documents; it does not launch or edit live campaigns. Triggers on "/digital-marketing-pro:campaign-orchestrator", "build a media plan", "how should we split budget across channels", "set up UTM naming conventions", "run a post-mortem on the campaign". Reads the brand profile, guidelines, and campaign history via campaign-tracker.py; its reference docs are consumed by /digital-marketing-pro:campaign-plan rather than duplicated.
churn-risk
Score customer segments for churn risk from behavioral signals — email engagement decline, purchase recency, usage drops, support sentiment — producing a 0-100 risk scorecard with four tiers, per-tier intervention playbooks (actions, timing windows, channels, messaging), LTV-at-risk totals, and retention-ROI prioritization. Assesses and recommends; it does not send outreach or launch campaigns. Triggers on "/digital-marketing-pro:churn-risk", "which customers are about to churn", "score our segments for churn risk", "email engagement is dropping, who is at risk", "build a retention intervention plan". Pulls behavioral data from a connected CRM MCP (Salesforce or HubSpot) or user-provided exports, runs scripts/churn-predictor.py, and reads the brand profile for lifecycle context.
competitor-alerts
Configure a tiered competitor alert system — per-competitor trigger thresholds across content, pricing, ads, social, ranking, and SERP changes, with critical/warning/info urgency routing, digest batching, and alert-fatigue guardrails — then send test alerts to verify Slack or email delivery. Triggers on "/digital-marketing-pro:competitor-alerts", "alert me when a competitor changes pricing", "set up competitor alerts", "too many competitor notifications", "tell me when competitors launch new ads". Requires baselines from /digital-marketing-pro:competitor-monitor and persists config via competitor-tracker.py; reads the brand profile for competitive context.
competitor-monitor
Set up ongoing competitor monitoring — captures per-competitor baselines across content, pricing, ads, social, SEO, and SERP features, saves them via competitor-tracker.py, configures per-dimension scan schedules and alert rules, and produces an initial competitive intelligence brief with threat rankings. Triggers on "/digital-marketing-pro:competitor-monitor", "track our competitors over time", "watch competitor pricing pages", "set up competitor tracking", "detect when competitors change their site". Baselines power /digital-marketing-pro:competitor-alerts and share-of-voice trends. Reads the brand profile for competitive landscape context.
counter-narrative
Build a counter-narrative playbook responding to a competitor's positioning move — rebrand, category claim, aggressive campaign, price change, or partnership. Analyzes the move and its impact, selects a counter approach (direct counter, reframe, category counter, social proof, or zeitgeist) via narrative-mapper.py, and delivers a multi-channel response plan with content angles, ad concepts, PR angles, messaging guidelines, an urgency-calibrated timeline, and tracking metrics. Triggers on "/digital-marketing-pro:counter-narrative", "competitor just rebranded, how do we respond", "they are claiming a new category", "respond to their attack campaign", "counter a competitor price cut". Plans the response — it does not launch campaigns. Reads the brand profile and messaging guardrails.
creative-health
Assess ad creative fatigue across active campaigns — scores each creative 0-100 via creative-fatigue-predictor.py (CTR, CPM, and engagement vs baseline, frequency saturation, time running), predicts days until fatigue, and delivers refresh briefs, A/B test plans, and a priority list ranked by estimated spend waste. Triggers on "/digital-marketing-pro:creative-health", "are our ads fatiguing", "CTR is dropping on our ads", "when should we refresh creatives", "which ads are wasting spend". Needs per-creative performance data (exported or from connected ad platform MCPs). Analysis and recommendations only — it does not pause or launch ads. Reads the brand profile and visual-identity restrictions for refresh constraints.
cro
Audit landing pages, forms, pricing pages, and checkout flows for conversion killers, and design statistically sound A/B tests — ICE-prioritized recommendations, hypothesis templates, and script-computed sample sizes and significance checks. Advises and plans; it does not edit your site or run the tests. Triggers on "/digital-marketing-pro:cro", "audit this landing page", "why is our conversion rate so low", "how long should this A/B test run", "reduce cart abandonment". Reads the brand profile, industry benchmarks, and campaign history before making recommendations.
aeo-geo
Strategy module for Answer Engine / Generative Engine Optimization — audits AI visibility, restructures content for citation, runs entity-consistency checks across Knowledge Graph, Wikidata, Wikipedia, Crunchbase, and LinkedIn, and produces JSON-LD schema specs, monitoring frameworks, and a 90-day LLM content strategy. Triggers on "/digital-marketing-pro:aeo-geo", "how do we get cited by AI", "optimize for AI Overviews", "fix our entity consistency", "do we need llms.txt". Reads the brand profile, compliance rules, and industry benchmarks; its measurement counterpart is /digital-marketing-pro:aeo-audit, with GSC actuals via /digital-marketing-pro:gsc-ai-performance.
anomaly-scan
Scan all connected marketing platforms for statistically significant deviations from stored baselines — traffic drops, CPA spikes, deliverability collapse, budget overruns, or unexpected wins — classified critical/warning/info with probable causes, correlation to recent changes, and recommended actions. Triggers on "/digital-marketing-pro:anomaly-scan", "why did our CPA spike", "did anything weird happen this week", "check for anomalies", "our conversions suddenly dropped". Runs performance-monitor.py for baselines and detection, correlates flags against execution-tracker.py history and the diagnostic framework in skills/analytics-insights/anomaly-diagnosis.md, and persists critical findings as insights via campaign-tracker.py. Reads the brand profile.
attribution-model
Design a multi-touch attribution strategy — recommends the best-fit model for the business's sales cycle and data maturity, defines credit-distribution rules and lookback windows, maps platform-specific setup (GA4, HubSpot, Salesforce, warehouse), and documents tracking gaps and known blind spots. Triggers on "/digital-marketing-pro:attribution-model", "set up multi-touch attribution", "which attribution model should we use", "configure GA4 attribution", "how should we credit channels for conversions". Reads the brand profile and consumes the canonical model taxonomy in skills/funnel-architect/attribution-models.md; to run the models against real conversion data, pair with /digital-marketing-pro:attribution-report.
attribution-report
Run multi-touch attribution analysis on real conversion-path data — applies two or more models side-by-side (first-touch, last-touch, linear, time-decay, position-based, data-driven), computes per-channel attributed revenue and ROAS, assisted-conversion ratios, path-length and time-to-conversion distributions, and budget reallocation recommendations. Triggers on "/digital-marketing-pro:attribution-report", "which channels actually drive revenue", "compare first-touch vs last-touch", "run an attribution analysis", "is paid social undervalued". Pulls journeys from Google Analytics, Google Ads, Meta, and CRM MCPs and includes GA4's AI Assistant channel; model definitions come from skills/funnel-architect/attribution-models.md, strategy design from /digital-marketing-pro:attribution-model.
autopilot-status
Campaign autopilot operations dashboard — 0-100 health scores for all active campaigns, a chronological log of auto-corrections taken (bid, budget, audience, creative, pause) with before/after metrics, the current guardrail rule table, campaigns escalated for human attention ranked by urgency, and estimated savings from automated interventions. Triggers on "/digital-marketing-pro:autopilot-status", "how is autopilot doing", "what did the autopilot change", "which campaigns need my attention", "show guardrail settings". Runs campaign-health-monitor.py for health scores, corrections history, and the savings report; reads the brand profile for KPI targets, naming conventions, and budget constraints.
budget-tracker
Track advertising spend pacing in real time across connected ad platforms (Google Ads, Meta, LinkedIn, TikTok) — produces a budget dashboard with daily burn rates, end-of-period projections, overspend/underspend alerts, and dollar-specific reallocation recommendations backed by CPA/ROAS context. Monitors and recommends only; it never edits platform budgets. Triggers on "/digital-marketing-pro:budget-tracker", "are we overspending this month", "how is our ad budget pacing", "track spend across platforms", "will we blow through the budget cap". Reads budget targets from the brand profile, runs scripts/ad-budget-pacer.py, and saves snapshots for trend history; pairs with /digital-marketing-pro:budget-optimizer.
campaign-status
Unified status dashboard for every tracked campaign across connected platforms — produces a summary table with health indicators, live spend and performance metrics, a 7-day execution history, pending approvals with age, KPI variance classification (on track / at risk / behind), flagged issues, and next scheduled actions. Reports only; it changes nothing on any platform. Triggers on "/digital-marketing-pro:campaign-status", "what campaigns are running right now", "any failed executions or stuck approvals", "status of the Q1-Launch campaign", "which campaigns are behind target". Reads the brand's campaign registry, execution log, and approval queue via campaign-tracker.py, execution-tracker.py, and approval-manager.py, plus live metrics from connected platform MCPs.
client-onboarding
Generate a complete onboarding package for a new marketing client — kickoff meeting agenda, 20-30 question discovery questionnaire, stakeholder map with RACI matrix, platform-by-platform access checklist, 30-60-90 day milestone plan, communication cadence, escalation protocol, welcome email template, internal team brief, risk register, and a day-by-day first-week action plan. Triggers on "/digital-marketing-pro:client-onboarding", "we just signed a new client", "build a kickoff agenda and discovery questionnaire", "30-60-90 day plan for the new account", "what access do we need from the client". Reads the brand profile, guidelines, custom templates, and agency SOPs so the package matches house process.
client-proposal
Draft a professional agency proposal or pitch document for a prospective client — executive summary, situation analysis, scope of services with a deliverables matrix, KPI targets with baselines and stretch goals, 2-3 pricing options, team bio structure, case-study placeholders, terms outline, and next steps, written from the agency's perspective. Triggers on "/digital-marketing-pro:client-proposal", "write a proposal for this prospect", "scope of work for a 6-month retainer", "respond to this RFP", "pitch deck outline with pricing tiers". Loads the agency's own brand profile (not the client's), plus custom templates and agency SOPs; industry benchmarks inform the KPI and pricing sections.
client-report
Generate a white-labeled client report in agency voice — weekly pulse, monthly review, or QBR — with a KPI scorecard vs targets and comparison period, channel breakdowns, top wins with attribution, root-cause analysis of misses, 3-5 strategic recommendations, and budget efficiency. Requires explicit approval before any external send; only then can it deliver via connected Slack, email, or Google Sheets MCPs and log the delivery. Triggers on "/digital-marketing-pro:client-report", "prepare the monthly report for the client", "build the QBR for this account", "send the weekly performance pulse", "white-labeled performance report". Reads the brand profile and pulls data via campaign-tracker.py, execution-tracker.py, and connected platform MCPs; formats via report-generator.py.
cohort-analysis
Segment customers into cohorts — by acquisition period, channel, first behavior, or revenue tier — and produce a color-coded retention matrix, overlaid retention curves, LTV-by-cohort comparisons with LTV:CAC where cost data exists, best/worst cohort rankings with hypothesized drivers, stabilization-point analysis, and intervention recommendations for underperformers. Analyzes and recommends; it launches nothing. Triggers on "/digital-marketing-pro:cohort-analysis", "are newer customers retaining better than older ones", "which channel produces the highest-LTV customers", "build a retention matrix", "when does our churn stabilize". Pulls customer data from connected CRM and analytics MCPs, reads the brand profile for business-model context, and saves the summary as a campaign-tracker.py insight for trend tracking.
content-repurpose
Turn one piece of content into a multi-channel repurposing plan — a derivative matrix targeting 10+ formats, full platform-adapted drafts, a publishing calendar, UTM-tagged links, and per-piece brand-voice scores; every derivative must pass the standalone test (own hook, own payoff) and the cut list records what failed it. Triggers on "/digital-marketing-pro:content-repurpose", "repurpose this blog post", "turn this webinar into social posts", "get more mileage out of this article", "atomize this whitepaper". Produces drafts and a schedule, not published posts. Reads the brand profile, channel style overrides, and platform specs.
cf-publish
Execute CMS publishing: push a finished, reviewed piece (Phase 8 complete, quality score >=7.0) to Webflow or WordPress via MCP connectors as draft, scheduled, or live — always showing a full publish preview and waiting for your explicit yes/no/edit confirmation before anything is pushed. Runs the EU AI Act Article 50 disclosure check, verifies the live URL, meta tags, and images post-publish, and falls back to a standalone HTML export when no CMS connector is configured. Triggers on "/contentforge:cf-publish", "publish this article to WordPress", "push this to Webflow", "schedule this post for next week", "export the article as HTML". Refuses unreviewed content; pairs with /contentforge:cf-social-adapt for post-publish promotion.
cf-social-adapt
Repurpose a finished article into ready-to-publish, platform-native social posts for LinkedIn, Twitter/X, Instagram, Facebook, Threads, TikTok, Bluesky, and YouTube Shorts — each with hook, hashtags, CTA, character count, image spec, and posting time, typically 24-40 posts per article. Triggers on "/contentforge:cf-social-adapt", "turn this article into LinkedIn posts", "make social posts from this blog", "repurpose this for social media", "promote the published article". Dispatches the contentforge:social-adapter agent, takes all platform limits from config/social-platform-specs.json, reads the brand profile for voice, and requires pipeline-approved content (score >=7.0). Pairs with /contentforge:cf-publish for the live article URL.
cf-switch-backend
Switch ContentForge's tracking and delivery backend between Google Sheets + Drive, Airtable, and local filesystem — guiding credential setup, verifying access, optionally migrating existing tracking records and output files (migration is additive and never deletes source data), and updating tracking.backend in the brand profile so the next run uses it immediately. Triggers on "/contentforge:cf-switch-backend", "switch tracking to Airtable", "move tracking to Google Sheets", "which backend am I using", "migrate my tracking data". Runs backend-migrator.py, sheets-tracker.py, airtable-tracker.py, or local-tracker.py; --status reports current backend health. Pairs with /contentforge:cf-cowork-setup for the Cowork Drive route and /contentforge:cf-style-guide, whose Step G sets the initial backend.
cf-translate
Translate publication-ready ContentForge content into any of 15 languages at three localization levels (literal, adapted, transcreated) — preserving brand voice, keeping citation URLs and DOIs untouched, and adapting SEO keyword placements for the target market — delivered as a translated .docx plus a quality report via the brand's tracking backend. Triggers on "/contentforge:cf-translate", "translate this article to Spanish", "localize this for the German market", "make a French version of this post", "transcreate this for Japan". Dispatches the contentforge:translator agent, maps voice via config/multilingual-patterns.json, and runs a target-language humanizer pass. Requires pipeline output scoring >=7.0 and a brand profile; pairs with /contentforge:create-content upstream.
cf-add-integration
Connect any external API or service to ContentForge as a custom MCP connector — walks non-technical users from finding a verified MCP package or HTTP endpoint to a ready-to-paste .mcp.json entry, credential setup instructions, and a post-restart verification check. Triggers on "/contentforge:cf-add-integration", "connect our internal CMS", "add a custom integration", "hook up Google Analytics to ContentForge", "there is no connector for this service". Reads .mcp.json.connectors-reference for verified endpoints and checks the registry via scripts/connector-status.py first; for connectors already in the registry, /contentforge:cf-connect is the shorter path. Configuration guidance only — never asks for secrets in chat and does not call the connected service itself.
adapt-copy
Adapt post copy for every target platform — character limits, hashtag counts and placement, tone, compliance, and the right CTA mechanism per platform (comment-keyword or link-in-bio on Instagram/TikTok, direct link elsewhere; the CTA is never dropped). Triggers on "/adapt-copy", "adapt this copy", "platform versions", "rewrite for LinkedIn", "caption for each platform", "cross-post this", or any time one piece of copy needs platform-native variants. Reads the brand profile for voice, hashtags, and cta_keyword.
brand-manager
Set up and manage brand profiles — colors, fonts, logo, voice, pillars, platforms, hashtags, compliance rules, cta_keyword. Triggers on "/brand-manager", "new brand", "set up a brand", "update the brand config", "switch brand", "change brand colors", "add a platform to the brand", or any time brand configuration is created or edited. Every other skill reads this profile — run it before any production.
compose-creative
Core creative engine — turns a calendar post into finished images or video using 4 modes (anchor-compose, enhance-extend, style-referenced, pure-creative) with brand assets, AI generation, and human approval before credits are spent. Triggers on "/compose-creative", "generate the creative", "make the image for P07", "produce this post", "create the visual", "compose this", or any time a calendar post needs its creative produced. Overlay text follows the pairing rule — it never echoes the caption.
full-pipeline
Run the complete production pipeline end to end — parse the calendar, match assets, compose creative, adapt copy, build previews, run reviews, finalize delivery — with checkpoints between phases. Triggers on "/full-pipeline", "run the whole month", "produce the month", "end to end", "do everything", "full production run", or when a parsed calendar exists and the whole month should be produced in one supervised pass. Quote costs first via price-check.
generate-video
Generate short-form video via a 5-stage human-in-the-loop pipeline — concept, first frame, last frame, motion, final render — with approval at every stage before credits are spent. Triggers on "/generate-video", "make a video", "video for P12", "animate this image", "reel from this", "image to video", "video post", or any calendar post whose content_type is video, reel, or story. Models and prices are resolved live, never hardcoded; sound costs extra — quote it first.
index-assets
Index the brand photo and asset library with AI vision — each asset described, tagged, and made searchable so match-assets can pair them with calendar posts. Triggers on "/index-assets", "index the assets", "scan the photo library", "new brand photos", "refresh the asset index", "what assets do we have", or after any batch of brand imagery lands. Run once per brand, re-run on new uploads.
match-assets
Match indexed brand assets to calendar posts and assign each post its creative mode (anchor-compose, enhance-extend, style-referenced, pure-creative). Triggers on "/match-assets", "match assets", "which photos for which posts", "assign creative modes", "pair assets to the calendar", or right after parse-calendar and before compose-creative. Reads the asset index; posts with no suitable asset are flagged rather than force-matched.
parse-calendar
Parse a monthly content calendar from DOCX, XLSX, Notion, or pasted text into structured calendar-data.json — the source of truth every downstream skill reads. Triggers on "/parse-calendar", "parse the calendar", "import this calendar", "here is the month", "load the content plan", "calendar to JSON", or whenever a client calendar arrives in any format. No calendar yet? /socialforge:ideate-month drafts one in this exact shape.
setup
One-time setup for image and video generation APIs — Vertex AI, WaveSpeed, and Higgsfield credentials stored persistently and verified before use. Triggers on "/setup", "set up socialforge", "configure the APIs", "add credentials", "connect vertex", "credential status", or before any creative production on a new machine. Keys live outside the repo; nothing is committed to git.
render-carousels
Render multi-slide carousels from HTML templates via Playwright — slide content injected, brand styling applied, assembled to platform-ready images or PDF. Triggers on "/render-carousels", "render the carousel", "carousel for P04", "build the slides", "multi-slide post", "carousel from this outline", or any calendar post whose content_type is carousel. Local rendering, no API cost.
model-check
Find the model that is currently best for a capability by reading the provider live catalogue, and record it with its source — the code asks for kinds, never hardcoded ids. Triggers on "/model-check", "which model should we use", "best video model right now", "is this model still current", "model staleness", "update the models", or before any production month and whenever a resolve comes back stale. Pairs with price-check — newest is not automatically best or cheapest.
price-check
Look up what a generation actually costs right now from the provider live pricing page, record it with its source, and quote a run before spending anything. Triggers on "/price-check", "what will this cost", "quote the month", "price this video", "compare providers", "is sound extra", "cost estimate", or before generate-all and any paid generation. Prices expire after 24h; quotes refuse rather than guess, and a quote is never an approval.
ideate-month
Plan next month's content calendar from a theme, raw signals, and last month's results — before any calendar exists. Triggers on "/ideate-month", "/plan-month", "what should we post next month", "plan the calendar", "ideas for next month", "month theme", "content ideas for [brand]", "build a calendar from scratch", or any time a brand needs a month planned and no client calendar has arrived. Outputs a calendar-data.json-compatible draft — series arcs, one-off posts, tiers, platforms — that feeds straight into /socialforge:parse-calendar and the production pipeline. Reads the brand profile for pillars and voice; mines pasted news/trends/notes into on-pillar angles; compounds last month's measured wins (fed by /socialforge:ingest-performance, with anecdotal reports labeled as such) instead of starting from zero.
assemble-document
Assemble the final month-end delivery manifest — every approved post with its copy, creative files, platform variants, and metadata in one structured JSON handoff. Triggers on "/assemble-document", "assemble the delivery", "final document", "package the month", "client handoff file", "delivery manifest", or when all posts are approved and the month needs packaging. Runs after finalize-month; the output is what the client receives.
finalize-month
Package all approved content into the final delivery folder — files renamed per convention, per-platform copy files, manifest included — ready for client handoff. Triggers on "/finalize-month", "finalize the month", "package everything", "prepare the delivery", "close out the month", "handoff folder", or when every post has cleared its approval queue and the month ships to the client.
build-review-gallery
Build the interactive HTML review gallery showing every generated post — image, copy, platform, status — for team or client review in a browser. Triggers on "/build-review-gallery", "review gallery", "show me the month", "build the gallery", "preview everything", "review page", or after a generation batch completes and someone needs to see it all in one place. Local file, no server, no API cost.
create-previews
Generate platform-accurate mockup previews — the post as it will actually render on LinkedIn, Instagram, X, TikTok — before anything is published. Triggers on "/create-previews", "preview this post", "how will it look", "platform mockup", "show it on Instagram", "preview batch", or after creative and copy exist and stakeholders need to see the assembled post in context before approval.
manage-reviews
Run the approval workflows — internal review, client review, CEO sign-off, revision requests, reminders — that gate every asset before delivery. Triggers on "/manage-reviews", "send for review", "approval status", "who has not approved", "client feedback", "request revisions", "chase approvals", or any time content is waiting on a human decision. The approver recorded here feeds the c2pa-sign human-oversight record.
cf-help
Show the ContentForge user guide with live plugin state — version, agent/skill/command counts, connector availability, and runtime environment read from scripts/plugin-metadata.py, never hardcoded — plus pipeline overview, per-skill listings, worked examples, brand-setup methods, and a troubleshooting matrix. Triggers on "/contentforge:cf-help", "how do I use ContentForge", "list the ContentForge skills", "explain the content pipeline", "ContentForge isn't working". Flags route to sections (--pipeline, --skills, --examples, --troubleshoot, --brand), and a Cowork sandbox warning is surfaced automatically when detected. Documentation only — it renders guidance from live metadata and runs no production pipeline.
cf-style-guide
Import a brand voice profile from an existing style guide — a .docx/.pdf document, a URL, or manual input — extracting tone, formality, personality, approved/banned terminology, compliance guardrails, and author profiles into a structured brand-profile JSON at ~/.claude-marketing/{brand-slug}/Brand-Guidelines/, then configure the tracking backend (Google Sheets + Drive, Airtable, or local). Triggers on "/contentforge:cf-style-guide", "import our style guide", "set up a brand from this document", "update the brand profile with new guidelines", "extract our banned terms and disclaimers". Deterministic parsing, no agent. The saved profile is read by every pipeline phase — drafting, brand compliance, humanizer; pairs with /contentforge:brand-setup and /contentforge:cf-switch-backend.
cf-video-script
Produce a production-ready video script for YouTube, YouTube Shorts, TikTok, Instagram Reels, or explainers — timestamps, scene dialogue, B-roll shot list, on-screen text, and music notes. Every script passes the Phase 3.5 claim-verification gate (contentforge:fact-checker checks each statistic in narration and on-screen overlays; zero unverified claims survive), a spoken-language humanizer pass so narration reads for the ear, and a 5-dimension review scorecard (hook, claim integrity, payoff density, retention risk, CTA — >=7.0 average to ship). Triggers on "/contentforge:cf-video-script", "write a YouTube script about this", "turn this article into a TikTok", "script a 60-second reel", "make an explainer video script". Dispatches researcher, content-drafter, and structurer agents, reads the brand profile, delivers via the tracking backend. Scripts only — no finished video.
cf-aeo-check
Post-publication AI-visibility check — re-probes target queries via web search, records whether the published piece is cited in Google AI Overviews, audits on-page extractability (definition block, dates, schema, structures) via web fetch, and appends every check to per-brand history so deltas are tracked over time. Triggers on "/contentforge:cf-aeo-check", "is our article cited in AI Overviews", "did we earn AI citations", "check AEO for this URL", "why is a competitor cited instead of us". Measures Google-observable signals only (no ChatGPT/Perplexity probing unless an AEO-tracking connector is present, and then labeled); closes the loop /contentforge:cf-brief opens and routes absent verdicts to /contentforge:content-refresh with evidence. Reports and records — it does not edit or republish the page.
cf-analytics
Render an ASCII analytics dashboard of ContentForge production history — quality score trends, phase-by-phase pipeline timing, brand and content-type comparisons, compliance and citation metrics, outlier detection, and triggered alerts over a 7/30/90-day window. Triggers on "/contentforge:cf-analytics", "are our quality scores improving", "which pipeline phase is slowest", "show content production stats", "compare brands by quality". Reads tracking records written by Phase 8 to the brand's tracking backend (local JSON, Google Sheets, or Airtable) and alert rules from config/analytics-config.json; needs 10+ tracked pieces for meaningful trends. Analysis only — invokes no agents and never reads or stores content text.
cf-audit
Audit an existing content library for freshness decay and coverage gaps — scores every piece 0-100 on age, statistic currency, link health, and citation recency, maps covered topics against target keywords, and produces a prioritized report: top refresh candidates, gap topics, retire candidates, and the exact follow-up commands. Triggers on "/contentforge:cf-audit", "which content needs refreshing", "content health check", "what topics are we missing", "audit our blog library". Reads inventory from a Google Drive folder, WordPress REST API, or CSV; pulls performance data only if Google Analytics/Search Console MCPs are connected. Audit only — refreshing happens via /contentforge:content-refresh and new pieces start at /contentforge:cf-brief.
cf-brief
Generate a research-backed content brief from a keyword or topic — keyword data with volume and difficulty, top-5 competitor and E-E-A-T analysis, search-intent classification, audience pain points, a section-by-section outline with word counts and citation targets, plus SEO and AEO/GEO strategy (AI Overview status, answer-block map, entity list). Triggers on "/contentforge:cf-brief", "write a content brief", "keyword research for this topic", "what should this article cover", "analyze competitors before we write". Uses the researcher agent with Ahrefs/Similarweb MCPs when connected (labeled heuristic estimates otherwise) and aligns terminology to a brand profile when --brand is given. Produces a plan, not the article — feed it to /contentforge:create-content via --brief.
cf-cowork-setup
One-shot setup that wires ContentForge for team usage in Anthropic Cowork — verifies the Cowork sandbox environment, checks a Google Drive MCP is connected, creates the canonical Drive folder layout (_brands/, _runs/), and persists the team's routing config so .docx outputs, brand profiles, and checkpoints land in shared Drive instead of the ephemeral sandbox. Triggers on "/contentforge:cf-cowork-setup", "set up ContentForge in Cowork", "our files aren't landing in Drive", "wire outputs to our shared Drive", "first-time Cowork install". Runs scripts/plugin-metadata.py for environment detection, writes config via scripts/drive-sync-state.py, and can chain into /contentforge:brand-setup with --brand. Setup only — it does not migrate existing local brands and changes nothing in local Claude Code.
cf-template
Create and manage custom content-type templates beyond the 8 built-ins (article, blog, whitepaper, faq, research-paper, video-script, case-study, newsletter) — defining section structure, word-count allocations, readability targets, citation minimums, and quality standards, then validating the template against every pipeline phase. Saves to ~/.claude-marketing/_templates/ so plugin updates never wipe it. Triggers on "/contentforge:cf-template", "create a template for press releases", "add a custom content type", "list available templates", "import a structure from this example doc". Deterministic, no agent; produces the template file consumed by /contentforge:create-content --type=custom:name, and /contentforge:cf-brief can target its section structure.
cf-variants
Generate 3-10 scored A/B test variations of a single content element — headline, hook, CTA, intro, or conclusion — each rated across 6 quality dimensions and ranked by your optimization goal (clicks, engagement, conversions, or readability), with top-3 recommendations and A/B test setup guidance (sample size, duration, success metric). Triggers on "/contentforge:cf-variants", "give me headline alternatives", "A/B test options for this CTA", "which hook is stronger", "write 5 versions of this intro". Applies Humanizer phrasing patterns and Reviewer scoring logic, and reads the brand profile for voice fit. Scores are predictive, not live-traffic data; it varies single elements only — use /contentforge:create-content for full pieces.
content-refresh
Re-optimize an existing content piece with current statistics, new sources, and fixed citations at light (~20%), medium (~50%), or heavy (~80%) rewrite scope — preserving evergreen sections, SEO keyword placements, the URL slug, and internal links, then re-running the pipeline's quality gates (fact-check, validation, humanizer, reviewer) and saving as a new version with a before/after comparison report; the original file is never overwritten. Triggers on "/contentforge:content-refresh", "update this old article", "rankings dropped, refresh this post", "this content has outdated stats", "refresh it with current data". Reuses the 10-phase pipeline agents and loads the original .docx from the brand's tracking backend; pairs with /contentforge:cf-audit to find candidates and /contentforge:publish to push the update.
contentforge
Produce a publication-ready, fact-checked, brand-compliant, SEO-optimized content piece through the full 10-phase pipeline: every phase dispatched to a dedicated subagent (researcher, fact-checker, drafter, visual annotator, scientific validator, structurer, SEO/GEO optimizer, humanizer, reviewer, output manager) behind 10 orchestrator-verified quality gates — three-layer fact verification, the 43-pattern humanizer pass, and 5-dimension reviewer scoring (approve >=7.0) — ending in a .docx with scorecard appendices. Triggers on "/contentforge:contentforge", "write an article about", "create a blog post", "produce a whitepaper", "I need a fact-checked, publication-ready piece", "run the content pipeline". This is ContentForge's front door: reads the brand profile, then routes onward to /contentforge:publish, /contentforge:social-adapt, and /contentforge:translate.
batch-process
Produce multiple content pieces as a sequential, checkpointed queue — each piece runs the full 10-phase ContentForge pipeline with all 10 quality gates, sorted by priority and resumable after interruption. Intake from local JSON, Google Sheets, Airtable, or CSV; outputs per-piece .docx files plus a batch summary report. Triggers on "/contentforge:batch-process", "produce these 15 blog posts", "run the whole content queue", "batch content production", "process my content spreadsheet". Requires an existing brand profile per brand (create via /contentforge:brand-setup) and a pre-set title per piece — batch runs are non-interactive. Dispatches the batch-orchestrator agent; produces files, does not publish them.
cf-calendar
Plan a 30/60/90-day content production calendar — works backward from publish dates to schedule production windows, balances team assignments, detects deadline conflicts, renders a text Gantt-chart timeline, and optionally creates Google Calendar milestone events when that MCP is connected. Triggers on "/contentforge:cf-calendar", "plan next quarter's content schedule", "build an editorial calendar", "when should production start for these pieces", "schedule content deadlines for the team". Imports topics from manual input, Google Sheets, or the latest /contentforge:cf-audit recommendations; pairs with /contentforge:cf-brief and /contentforge:batch-process for execution. Deterministic scheduling only — it plans dates, produces no content, and does not auto-reschedule delays.
cf-connect
Set up a specific MCP connector from the ContentForge registry with step-by-step instructions tailored to its transport — verified endpoint URL for HTTP connectors, env vars plus a ready-to-paste .mcp.json entry for npx connectors, credential acquisition guidance, and post-setup verification. Triggers on "/contentforge:cf-connect", "connect WordPress", "set up the Notion connector", "how do I add Google Sheets", "a skill says a connector is missing". Status always comes from scripts/connector-status.py (never memory) and endpoints from .mcp.json.connectors-reference; fuzzy-matches names like wp or gsheets. Setup guidance only — for services not in the registry it hands off to /contentforge:cf-add-integration, and /contentforge:cf-integrations shows the full status dashboard.
cf-integrations
Render a live integration status dashboard for ContentForge — configured vs available MCP connectors grouped by category, coverage totals, and the top 3 quick-win connectors to add next, all taken from scripts/connector-status.py output. Triggers on "/contentforge:cf-integrations", "what integrations are connected", "show connector status", "why can't a skill reach my CMS", "which connectors should I set up next". Reads .mcp.json and environment variables only — no network calls, no agent; it reports status but does not configure anything. Pairs with /contentforge:cf-connect for guided setup and /contentforge:cf-add-integration for services outside the registry.
cf-environment
Detect where ContentForge is running (Cowork sandbox, local Claude Code on Windows/Mac/Linux, uncertain sandbox, or unknown) and report a capability matrix for that surface — which connector transports work, where files actually land, and whether /contentforge:resume survives sessions. Triggers on "/contentforge:cf-environment", "will this work in Cowork", "where did my files save", "why is my Documents folder empty after a run", "check capabilities before a long pipeline". Runs scripts/plugin-metadata.py --section environment and scans the session for Drive MCPs; pairs with /contentforge:cf-cowork-setup when Cowork+Drive wiring is missing. Diagnostic only — it reports the environment's limits and changes nothing.
ingest-performance
Feed last month's real numbers into next month's plan: ingest a platform analytics export (CSV from Instagram Insights, LinkedIn analytics, TikTok Studio, X analytics — any export with a post-id column) into per-post performance records, then rank the month's wins with sample floors and margin rules so ideation compounds measured winners, not remembered ones. Triggers on "/ingest-performance", "here are last month's numbers", "import analytics", "which posts performed best", "engagement report", "what worked last month", or whenever ideate-month needs its wins rung fed. Writes performance.json next to the month's tracker; /socialforge:ideate-month reads it and labels every win measured vs anecdotal.
c2pa-sign
Embed C2PA provenance manifests in AI-generated assets — the machine-readable AI disclosure EU AI Act Article 50 expects (enforceable since 2 Aug 2026), plus the human-approval record for the Article 50(4) exemption. Triggers on "/c2pa-sign", "sign this asset", "provenance", "content credentials", "AI disclosure", "Article 50", "is this compliant to publish", or before any AI-generated asset ships. Pass --reviewed-by and --model-id so the manifest records who approved it and what made it.
aeo-strategist
Enterprise AEO strategist for SEO/AEO practitioners on retainer client work. Use for any AEO or AI visibility task: audits, strategy, content briefs, schema markup, query libraries, competitive displacement, monthly reports, llms.txt, roadmaps, CMO explainers, client onboarding, tracking setup, and PR targeting. Covers 12 verticals (Pharma, BFSI, Real Estate, SaaS, Retail, Healthcare, EdTech, Legal, Manufacturing, Hospitality, Automotive, Media) and 8 markets (India, US, UK, UAE, SEA, Europe, Australia, Africa). Trigger for: AEO audit, AEO strategy, content brief, schema markup, query library, competitor AEO, AI Share of Voice, monthly AEO report, llms.txt, "why isn't [brand] in AI answers", "how do I get cited by ChatGPT/Gemini/Perplexity", roadmap, new client onboarding, tracking setup, PR targets, parametric knowledge, RAG optimization, AI crawler access, or any generative engine optimization task.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.