Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计提醒

client-report客户报告

Agent Skill

client-report 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

692

周安装

28

GitHub Stars

66

下载量

217
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

client-report 用于为特定品牌生成白标客户报告,包含 KPI 表现、渠道分析和战略建议。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中制作对外交付物,适用于客户沟通与进度汇报。
  • 支持通过 Slack、邮件、Google Sheets 或 Markdown 发送,具备审批拦截机制防止误发。
  • 需配置品牌信息后方可使用,确保数据来源合法且内容经过专业审核。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

/dm:client-report

Purpose

Generate a professional, white-labeled client report for a specific brand. Uses agency voice (not brand voice), includes KPI performance, channel breakdowns, strategic recommendations, and next steps. Designed for external client delivery via Slack, email, Google Sheets, or markdown — with approval gating before any external send to prevent accidental disclosure or premature delivery of draft findings.

Input Required

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

  • Brand slug: The brand this report covers — must match a configured brand in ~/.claude-marketing/brands/
  • Report type: One of:

- Weekly pulse: Quick KPI snapshot with 3-5 key metrics and brief commentary - Monthly review: Full performance analysis with channel breakdowns and recommendations - QBR: Quarterly deep-dive with strategic roadmap and forward plan

  • Date range: Specific start and end dates for the reporting period — defines what data is pulled and analyzed
  • Delivery channel: Where the report should be sent — slack, email, google-sheets, or markdown-only (no external delivery, just generate the artifact)
  • Custom sections (optional): Any additional sections the client has requested — competitive update, creative performance breakdown, audience insights, attribution deep-dive, or ad-hoc investigation topic
  • Comparison period: What to compare against — prior period, same period last year, plan/target, or all three simultaneously
  • Recipient list (optional): Specific client contacts who should receive the report if delivering via email or Slack — names and handles/addresses
  • Narrative emphasis (optional): What the client cares most about this period — growth, efficiency, brand awareness, pipeline generation, or revenue — influences which metrics are highlighted first and how insights are framed
  • Include appendix: Whether to attach raw data tables and campaign-level detail as an appendix — defaults to yes for monthly and QBR, no for weekly pulse
  • White-label settings (optional): Agency logo placement, color scheme, and disclaimer text — pulled from agency profile if configured, otherwise uses clean defaults

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. Pull all metrics for the brand: Query connected MCP servers and run campaign-tracker.py --brand {slug} --action metrics to gather performance data across all active channels for the specified date range
  3. Gather campaign history and execution log: Run execution-tracker.py --brand {slug} --action list --period {date_range} to compile all deliverables completed, campaigns launched, optimizations made, and tests concluded during the period
  4. Calculate KPIs vs targets and vs comparison period: Compute actuals against the brand's stated KPI targets from profile.json and against the selected comparison period — calculate deltas, percentage changes, trend direction, and statistical significance where sample sizes allow
  5. Break down performance by channel: Segment metrics by channel (paid search, paid social, organic search, email, display, video, affiliate, etc.) with per-channel KPIs, spend, efficiency metrics (CPC, CPA, ROAS, CTR), and contribution percentage to overall goals
  6. Identify top wins and attribution: Select the 3-5 best-performing campaigns or initiatives from the period — document what was done, what drove the result, audience and creative insights, and how it connects to business outcomes
  7. Analyze underperformance with root causes: For any KPI that missed target, identify root causes:

- External factors: market shifts, seasonality, competitive moves, platform algorithm changes - Internal factors: budget constraints, creative fatigue, audience saturation, timing misalignment - Corrective actions: what was already done and what is recommended for next period

  1. Generate strategic recommendations: Based on performance data, formulate 3-5 actionable recommendations — what to scale, what to pause, what to test next, where budget should shift, and what new opportunities to explore
  2. Write report in agency voice: Draft the full report using professional, third-person agency voice — NOT the brand's personality. Focus on clarity, data-backed insights, actionable next steps, and a confident but honest tone that builds client trust
  3. Format for delivery channel: Run report-generator.py --brand {slug} --format {channel} --type {report_type} to produce the channel-specific format (Slack blocks, email HTML, Google Sheets layout, or clean markdown)
  4. Create approval checkpoint: Present the full report preview for review. Risk level: low. Require explicit approval before any external delivery — highlight any sensitive data, unexpected results, or negative findings that may need pre-briefing with the client
  5. Deliver via MCP if approved: On approval, send via the appropriate MCP integration (Slack MCP, email MCP, Google Sheets MCP) if a delivery channel was specified. Handle delivery errors gracefully with retry guidance
  6. Log delivery and archive: Record the report delivery in the execution log with timestamp, recipients, delivery confirmation status, report version, and a reference to the archived report for future comparison

Output

A structured client report containing:

  • Executive summary: 3-5 sentence overview of the period — headline result, key wins, areas of focus, outlook for next period, and one recommended action for the client
  • KPI scorecard: Actuals vs targets vs comparison period in a scannable table with color-coded status indicators (exceeded, on track, at risk, missed) and trend arrows showing directional momentum
  • Channel performance breakdown: Per-channel metrics with spend, results, efficiency metrics (CPC, CPA, ROAS, CTR), contribution percentage to overall goals, and channel health assessment
  • Campaign highlights with attribution: Top-performing campaigns with what drove success, creative and audience insights, measured impact, and replication recommendations for future campaigns
  • Underperformance analysis: Honest assessment of any misses with root cause categorization (external vs internal), impact quantification, corrective actions taken, and preventive measures for next period
  • Strategic recommendations (3-5): Data-backed next steps with expected impact, investment required, implementation timeline, priority ranking, and connection to the client's stated business objectives
  • Budget efficiency analysis: Spend vs return summary by channel, cost trend lines over the period, budget utilization rate, and efficiency comparison to prior periods with improvement/decline indicators
  • Upcoming deliverables and timeline: What the agency will deliver next period with dates, milestones, dependencies, and any client actions required to keep the plan on track
  • Appendix (if requested): Raw data tables, campaign-level breakdowns, full metric exports, creative performance data, and supporting calculations for detailed review
  • Delivery confirmation: Channel, timestamp, recipients, delivery status, and report version — or markdown artifact if no external delivery was requested

Agents Used

  • agency-operations — Report voice and tone (agency professional, not brand personality), client context awareness, approval workflow management, white-label formatting, and delivery coordination
  • analytics-analyst — Metrics analysis, KPI calculations, channel breakdowns, trend analysis, comparison computations, attribution modeling, statistical significance checks, and recommendation data support
  • execution-coordinator — Report formatting for delivery channels, MCP integration delivery, execution logging, delivery error handling, and archival

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

38.02%
按下载量换算83

Claude

27.02%
按下载量换算59

Cursor

20%
按下载量换算43

Gemini CLI

9.8%
按下载量换算21

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

通过

权限和风险

external-service

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

安装前确认

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

来源信息

继续浏览同类 Skills