Token导航 LogoToken导航

Agent Skill · 研究检索

executive-dashboard(执行仪表板)

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

executive-dashboard 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 48,496。

总安装 685周安装 28GitHub Stars 66下载 222核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

executive-dashboard 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于关键词搜索、任务场景匹配或来源线索梳理等研究检索场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。

安装前需确认权限范围、维护状态及是否涉及联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/executive-dashboard

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

executive-dashboard 怎么安装?

在终端执行 npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill executive…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

executive-dashboard 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

executive-dashboard 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

executive-dashboard 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

executive-dashboard 用的人多吗?

公开数据是累计安装 685 次,近一周安装 28 次,下载 222 次,GitHub 66 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

executive-dashboard 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
executive-dashboard

执行仪表板 · 本页

68566只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

/dm:executive-dashboard

Purpose

Design a C-suite marketing dashboard that translates marketing metrics into business outcomes for executive decision-making. Bridges the gap between marketing activity data and business impact, giving senior leaders the clarity to make faster, better-informed strategic decisions without drowning in operational detail.

Input Required

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

  • Executive role: Primary audience — CEO, CMO, CFO, VP Marketing, or board — each requires different metric emphasis and abstraction level
  • Business model and revenue drivers: How the company makes money — SaaS, e-commerce, lead gen, marketplace, subscription — and the key revenue levers marketing influences
  • Strategic priorities this quarter: The 2-4 business priorities the executive team is focused on that marketing should ladder up to
  • Reporting frequency: How often the dashboard will be reviewed — weekly executive standup, monthly leadership meeting, quarterly board review
  • Current data sources and tools: Analytics platforms, CRM, ad platforms, attribution tools, and BI systems currently in use with data freshness and reliability notes
  • Existing reports being replaced: Current reporting artifacts the dashboard will consolidate or replace — helps identify gaps and redundancies
  • Key decisions the dashboard should inform: Specific decisions executives make that this dashboard should support — budget allocation, channel mix, hiring, campaign scaling, market expansion
  • Stakeholder data literacy level: How comfortable the audience is with marketing metrics — determines labeling, context, and narrative density needed

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 and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. 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. Identify north-star metrics: Select 5-7 metrics that directly tie marketing activity to business outcomes — revenue influenced, pipeline generated, customer acquisition cost, lifetime value, market share, brand equity indicators
  3. Design metric hierarchy: Organize metrics into three tiers — leading indicators (predict future performance), lagging indicators (confirm past results), and health metrics (signal system stability and sustainability)
  4. Select visualization type per metric: Choose the optimal chart type for each metric based on data shape and decision context — trend lines for trajectory, gauges for targets, bar charts for comparisons, sparklines for density
  5. Define alert thresholds and anomaly triggers: Set green/yellow/red thresholds for each metric with specific trigger values, and configure anomaly detection rules for unexpected spikes or drops
  6. Map data sources to each metric: Document which system provides each metric, how it is calculated, data freshness (real-time, daily, weekly), and known limitations or lag
  7. Design layout for scanning speed: Structure the dashboard for F-pattern or Z-pattern scanning — most critical metrics top-left, summary before detail, consistent visual hierarchy, minimal cognitive load
  8. Add narrative guidance: Write "how to read this" instructions for each section — what good looks like, what bad looks like, and what action to take in each scenario
  9. Build drill-down structure: Design three levels of depth — summary view (the dashboard itself), detail view (campaign or channel breakdowns), and root cause view (diagnostic data for investigating anomalies)
  10. Create mobile-friendly variant: Adapt the dashboard layout for mobile or tablet viewing — prioritize top 3-5 metrics, stack vertically, enlarge touch targets, and simplify visualizations
  11. Add comparison baselines: Define what each metric is compared against — plan/target, prior period (MoM, QoQ, YoY), industry benchmark, and competitive estimate — with comparison display format

Output

A structured executive dashboard design containing:

  • North-star metrics (5-7): Selected metrics with business rationale explaining why each matters to the executive audience and how it connects to strategic priorities
  • Metric hierarchy diagram: Visual framework showing leading, lagging, and health metrics with causal relationships and directional influence between them
  • Visualization recommendations: Chart type, scale, color coding, and annotation style for each metric with rationale for the design choice
  • Alert threshold definitions: Green/yellow/red boundaries for each metric with specific trigger values, anomaly detection rules, and notification routing
  • Data source mapping: Metric-by-metric documentation of source system, calculation method, refresh frequency, data latency, and known quality issues
  • Dashboard wireframe layout: Spatial layout showing metric placement, section grouping, visual hierarchy, and scanning flow optimized for the target audience
  • Narrative guide: Section-by-section presentation guide explaining how to read each area, what questions it answers, and what actions to consider based on the data shown
  • Drill-down structure: Three-level depth design — summary (dashboard), detail (channel/campaign breakdown), and root cause (diagnostic investigation) with navigation flow
  • Mobile layout variant: Adapted design for mobile viewing with prioritized metrics, vertical stacking, simplified charts, and touch-optimized interactions
  • Comparison baseline definitions: For each metric, the comparison standard (target, prior period, benchmark, competitive) with display format and context notes
  • Refresh cadence and data latency notes: Documentation of how often each metric updates, expected data lag, and implications for decision timing
  • Executive summary template: A 3-sentence written narrative template that synthesizes dashboard findings into a verbal briefing — what happened, why it matters, what to do next
  • Glossary of terms: Plain-language definitions of all metrics and marketing terminology for non-marketing stakeholders with examples and context

Agents Used

  • analytics-analyst — Metric selection, hierarchy design, visualization recommendations, data source mapping, alert thresholds, drill-down architecture, refresh cadence, and dashboard layout optimization

平台分布

Codex

39.58%
按下载量换算88

Claude

28.43%
按下载量换算63

Cursor

18.4%
按下载量换算41

Gemini CLI

9.38%
按下载量换算21

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills