executive-dashboard

executive-dashboard is a skill for Claude Code, Codex from indranilbanerjee/neels-plugins. It costs 26 tokens per session (1,385 once invoked), scanned A, a copy of executive-dashboard, MIT.

A specification for an executive marketing dashboard that connects activity metrics to business outcomes. It defines the main metric, charts, alert limits, audience, data sources, and reporting schedule.

In plain words
What is it for?
Use it to plan a dashboard for a CEO, CMO, CFO, vice president of marketing, or board, with the right measures and review frequency.
Why use it?
Leadership dashboards can become crowded with numbers that do not support decisions. This helps select measures and views that match the business model and current priorities.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Good fit Use it to plan a dashboard for a CEO, CMO, CFO, vice president of marketing, or board, with the right measures and review frequency.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/neels-plugins/executive-dashboard
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add indranilbanerjee/neels-plugins --skill executive-dashboard
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/neels-plugins

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for executive-dashboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/executive-dashboard/github.svg)](https://agentmods.dev/skills/indranilbanerjee/neels-plugins/executive-dashboard)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/executive-dashboard"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/executive-dashboard/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for executive-dashboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/executive-dashboard"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/executive-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,385 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.01385
Opus 5.5 $0.00010 $0.00554
Sonnet 5.5 $0.00005 $0.00277
Haiku 4.5 $0.00003 $0.00138

Measured 2d ago against content hash f99f9fa45052, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

executive-dashboard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

88% identical to executive-dashboard — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

hermes/digital-marketing-pro/strategy/skills/executive-dashboard/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/digital-marketing-pro: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 (/digital-marketing-pro: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

Read the full file on GitHub · 60 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 60 lines · 26 tokens per session scan A f99f9fa45052

Subscribe to this mod's changes

executive-dashboard is a skill published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,385 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to executive-dashboard, differing in 0 lines, and is treated as a copy.