Token导航 LogoToken导航TokenDH.com
待分类external-servicegithub未标认证来源可访问许可证需确认审计提醒

campaign-status活动状态

Agent Skill

campaign-status 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

661

周安装

27

GitHub Stars

67

下载量

212
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:campaign-status(活动状态)
来源仓库:https://github.com/indranilbanerjee/digital-marketing-pro
仓库路径:skills/campaign-status
安装命令:
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill campaign-status
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill campaign-status

简介

campaign-status 聚合各平台活动状态与关键指标的一站式视图。

  • 自动识别暂停、失败或待审批等异常情况,提前预警风险。
  • 用户需提供查询范围(全部/指定/某平台),返回结构化摘要。
  • 数据实时性取决于各平台 API 同步频率,可能存在延迟。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

/dm:campaign-status

Purpose

Provide a unified view of all active campaigns across every connected platform — ads, email, social, blog — with their current status, live performance metrics, execution history, and any pending approvals or scheduled actions. Eliminates the need to check each platform individually and surfaces issues (paused campaigns, failed executions, stale content) before they become problems.

Input Required

The user must provide (or will be prompted for):

  • Scope: All active campaigns, a specific campaign by name or ID, or a specific platform (e.g., "Google Ads campaigns only", "email campaigns", "campaign named Q1-Launch")
  • Detail level: Summary (one-line status per campaign) or detailed (full metrics, execution history, and next actions per campaign)
  • Time window (optional): How far back to include execution history. Defaults to last 7 days
  • Status filter (optional): Filter by campaign status — active, paused, scheduled, completed, failed. Defaults to active + paused + scheduled
  • Sort order (optional): Sort campaigns by spend, performance, recency, or status. Defaults to platform grouping

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/dm:brand-setup)?" — or proceed with defaults.
  2. List all tracked campaigns: Execute scripts/campaign-tracker.py --brand {slug} --action list-campaigns to get the campaign registry with names, platforms, statuses, creation dates, and assigned KPI targets.
  3. Pull execution history: Execute scripts/execution-tracker.py --brand {slug} --action get-history --days {time_window} to retrieve recent execution logs — what ran, when it ran, outcome (success/failure/skipped), error messages if any, and the user or automation that triggered it.
  4. Check pending approvals: Execute scripts/approval-manager.py --brand {slug} --action list-pending to surface any campaigns, creatives, or content pieces awaiting review before they can go live. Include submission date and age in hours for each pending item.
  5. Pull live metrics from connected MCPs: For each active campaign, query the relevant platform MCP (google-ads, meta-marketing, linkedin-marketing, tiktok-ads, mailchimp, etc.) for current performance:

- Spend: total spend, daily spend, budget consumed - Performance: impressions, clicks, CTR, conversions, CPA, ROAS - Engagement: open rate, click-through rate, bounce rate, video views - Platform-specific: quality score, relevance score, deliverability rate

  1. Aggregate by platform and status: Group campaigns by platform and status, calculate platform-level totals (total campaigns, total spend, total conversions, average CPA/ROAS), and flag any discrepancies between tracked campaigns and what the live platform reports.
  2. Calculate performance vs KPIs: For each active campaign with defined targets, compute actual vs target for primary KPIs. Classify as:

- On track (green): Meeting or exceeding targets - At risk (yellow): Within 15% of target with negative trend - Behind (red): Missing target by >15%

  1. Flag issues requiring attention: Identify problems that need action:

- Campaigns paused unexpectedly or by the platform (policy violation, billing issue) - Executions that failed with errors - Campaigns running past their planned end date - Stale campaigns with no activity in 7+ days - Campaigns exceeding budget pacing by >20% - Approval bottlenecks older than 48 hours

  1. Compile next scheduled actions: List upcoming scheduled launches, budget changes, creative rotations, A/B test completions, or automated optimizations from the execution log with dates and dependencies.

Output

A structured campaign status dashboard containing:

  • Campaign summary table: Campaign name, platform, status (active/paused/scheduled/completed/failed), days running, total spend, key metric (conversions or leads), CPA or ROAS, and health indicator (green/yellow/red)
  • Active campaigns by platform: Grouped view with platform-level totals — number of campaigns, total spend, total conversions, average CPA, average ROAS, and platform health status
  • Execution history (last 7 days): Chronological log of actions taken — campaign launches, pauses, budget changes, creative swaps, bid adjustments, email sends — with timestamps, outcomes, and actor (manual or automated)
  • Pending approvals: List of items awaiting review with requester name, submission date, type (creative, campaign launch, budget change, content), age in hours, and direct reference to the item
  • Performance vs KPIs: For each active campaign, actual performance vs the KPI targets set at campaign creation — on track, at risk, or behind, with variance percentage and trend direction
  • Flagged issues: Priority-ordered list of problems requiring attention with severity (critical/warning/info), description, affected campaign, and recommended resolution
  • Next scheduled actions: Upcoming automated or planned actions with dates, descriptions, dependencies, and responsible party
  • Quick actions: Suggested immediate next steps based on current status — approve pending items, investigate failures, pause underperformers, scale winners, extend successful campaigns

Agents Used

  • execution-coordinator — Execution history retrieval, approval queue management, scheduled action tracking, cross-platform status aggregation, and issue flagging
  • analytics-analyst — Live performance metrics interpretation, KPI comparison, campaign health assessment, and performance-based recommendations

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.3%
按下载量换算73

Claude

33.14%
按下载量换算70

Cursor

20.02%
按下载量换算42

Gemini CLI

8.5%
按下载量换算18

安全审计

Gen Agent Trust Hub

可疑

Socket

可疑

Snyk

可疑

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills