Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Prod Dashboard

ASecurity

Daily consolidation dashboard — reads outputs from all routines (morning, linear, github, community, strategy, meetings, metrics) and generates a unified HTML dashboard. Trigger when user says 'dashboard', 'generate dashboard', 'overview', 'consolidation', or 'general panel'.

529 stars
0 votes
0 copies
0 views
Added 5/29/2026
ai-agentsgogit

Works with

cli

Security Analysis

A100/100

Scanned 5/29/2026

$npx -y skills add evolution-foundation/evo-nexus --skill prod-dashboard --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prod Dashboard?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Prod Dashboard
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/evolution-foundation-prod-dashboard/badge)](https://www.skillsdirectory.com/skills/evolution-foundation-prod-dashboard)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: prod-dashboard
description: "Daily consolidation dashboard — reads outputs from all routines (morning, linear, github, community, strategy, meetings, metrics) and generates a unified HTML dashboard. Trigger when user says 'dashboard', 'generate dashboard', 'overview', 'consolidation', or 'general panel'."
---

# Consolidated Dashboard — 360 View

Consolidation routine that reads outputs from other routines and generates a unified HTML dashboard with an overview of all business areas.

**Always respond in English.**

**IMPORTANT:** This routine does NOT fetch new data. It reads outputs already generated by other routines for the day/week and consolidates everything into a single view.

## Step 1 — Collect data from sources (silently)

Read all available sources without narrating each step. If a source does not exist (routine has not run yet), use "—" or "no data" as fallback.

### 1a. Tasks
Run `todoist list --filter "today | overdue"` to count pending tasks.

### 1b. Linear / Sprint
Read the latest Linear report in `workspace/projects/linear-reviews/` (most recent file `[C] *-linear-review.html`). Extract:
- Sprint progress (% and count)
- Blockers
- Issues in review
- Completed issues

### 1c. GitHub
Read the latest GitHub report in `workspace/projects/github-reviews/` (most recent file `[C] *-github-review.html`). Extract:
- Open PRs
- Community issues
- Stars this week
- Latest release

### 1d. Community
Read the latest community pulse in `workspace/community/reports/daily/` or weekly in `workspace/community/reports/weekly/`. Extract:
- WAM (Weekly Active Members)
- Overall sentiment
- Support tickets
- Docs gaps

### 1e. Financial
Read the latest strategy digest in `workspace/strategy/digests/` (most recent file). Extract:
- MRR
- Subscriptions
- Runway
- Sales pipeline

### 1f. Calendar
Use /gog-calendar to list today's events.

### 1g. Meetings
Read `workspace/meetings/summaries/` or `workspace/meetings/summaries/` — last 5 meetings. Extract:
- Date, title, participants, action items

### 1h. Routine metrics
Read `ADWs/logs/metrics.json` for status of each automated routine:
- Name, agent, last run, average duration, success rate

### 1i. Morning Briefing
Read today's morning briefing at `workspace/daily-logs/[C] YYYY-MM-DD-morning.html` if it exists, to supplement calendar and priority task data.

## Step 2 — Calculate health badges

For each area, define the status (CSS class):
- **saudavel** (green): all good, metrics within expectations
- **misto** (yellow): some areas of concern
- **risco** (red): serious problems requiring action

Criteria:
- **Product:** blockers > 0 = misto; blockers > 3 = risco; sprint progress < 50% with >60% of time elapsed = risco
- **Community:** negative sentiment = risco; docs gaps > 5 = misto
- **Financial:** MRR declining = misto; runway < 6 months = risco
- **Routines:** any routine with rate < 80% = misto; rate < 50% = risco

## Step 3 — Generate dashboard HTML

Read the template at `.claude/templates/html/custom/dashboard-consolidation.html` and replace ALL `{{PLACEHOLDER}}` with the collected data.

For dynamic rows (marked with `<!-- TEMPLATE -->`), generate the correct HTML:

### Calendar rows
```html
<div class="metric-row">
  <div class="mr-label">HH:MM</div>
  <div class="mr-value">Event name</div>
</div>
```

### Priority tasks rows
```html
<div class="list-item">Task description</div>
```

### Meetings rows
```html
<tr>
  <td>DD/MM</td>
  <td>Meeting name</td>
  <td>Person 1, Person 2</td>
  <td>N action items</td>
</tr>
```

### Routines rows
```html
<tr>
  <td>Routine Name</td>
  <td>@agent</td>
  <td>DD/MM HH:MM</td>
  <td>XXs</td>
  <td><span class="rotina-rate high/medium/low">XX%</span></td>
  <td><div class="rotina-status"><div class="rotina-dot ok/falha"></div></div></td>
</tr>
```

### Attention points
Consolidate into bullets the items requiring immediate attention. Examples:
- Sprint blockers
- PRs without review for more than 2 days
- Negative community sentiment
- Failing routines
- Declining MRR

If there are no attention points, write "No attention points at the moment."

## Step 4 — Save

Save the filled HTML to:
```
workspace/daily-logs/[C] YYYY-MM-DD-dashboard.html
```

## Step 5 — Confirm

Present a short summary:

```
## Dashboard generated

**File:** workspace/daily-logs/[C] YYYY-MM-DD-dashboard.html
**Health:** Product {status} | Community {status} | Financial {status} | Routines {status}
**Alerts:** {N} attention points
```

Attribution

evolution-foundationevolution-foundation
View sourceSee grades on GitHubMore from evolution-foundation →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →