agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/executive-dashboard/SKILL.md

executive-dashboard

Skill1 starsChanged 23 days agoMITView on GitHub

Designs an executive dashboard when leaders need a concise view of outcomes, trends, exceptions and actions.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for recurring oversight where leaders need signals for intervention rather than operational detail.

    line 9
  2. Distinctive:

    Start from executive decisions and map each to a useful indicator.

    line 18
  3. Distinctive:

    Remove measures that do not change a decision or action.

    line 23

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Executive Dashboard

When to use it

Use for recurring oversight where leaders need signals for intervention rather than operational detail.

What Claude needs

  • client-context.md and executive priorities
  • Outcomes, indicators, baselines and thresholds
  • Current and historical performance data
  • Owners, cadence and available data sources

Method

  1. Start from executive decisions and map each to a useful indicator.
  2. Balance outcome, leading, delivery, risk and capacity measures.
  3. Define calculation, source, owner, cadence and threshold for each measure.
  4. Show trend and variance against baseline or target direction.
  5. Pair every material exception with cause, impact and response.
  6. Remove measures that do not change a decision or action.

Output format

Provide an executive snapshot followed by a table with Indicator, Current Position, Trend, Threshold, Interpretation, Action, Owner and Data Date.

Quality checks

  • Measures reconcile to named and current sources.
  • Status colours follow explicit thresholds.
  • The dashboard distinguishes signal from normal variation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.