Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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
  • 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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Executive Board

ASecurity

Prepare board and investor decisions, narratives, pre-reads and governance communications around material metrics, variance, risks and explicit asks without spin or fabricated confidence.

3 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add marcmarti9/agentit --skill executive-board --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Executive Board?

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

Security grade badge for Executive Board
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/marcmarti9-executive-board/badge)](https://www.skillsdirectory.com/skills/marcmarti9-executive-board)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: executive-board
description: Prepare board and investor decisions, narratives, pre-reads and governance communications around material metrics, variance, risks and explicit asks without spin or fabricated confidence.
---

# Executive Board

Use this skill for board/investor pre-reads, board meeting preparation, governance communications, material business updates and decision requests.

A board package is not a company encyclopedia. Its job is to make **material state, decisions, risks and asks** easy to understand and discuss.

## Start with the purpose

Clarify:

- what the board/investor audience needs to decide, approve or understand;
- what changed since the last update;
- which metrics/risks are material;
- what management recommends;
- which decisions/asks require discussion;
- confidentiality and distribution boundaries.

Do not elevate normal operating detail to board level merely because it exists.

## Narrative structure

A useful board narrative usually makes the following clear:

1. what happened;
2. why it happened;
3. how it compares with plan/previous expectations;
4. what management learned;
5. what management is doing next;
6. what decision or help is needed from the board.

Lead with the real situation and the ask. Do not bury bad news after celebratory slides.

## Core material

Select only what is relevant, commonly including:

- headline company/strategic update;
- KPI dashboard with definitions and trend;
- financial actuals and variance versus plan;
- product/customer/commercial evidence;
- top risks and mitigations;
- major people/org items when board-relevant;
- key strategic decisions;
- explicit asks / approvals;
- appendix for detail that should not consume meeting time.

Numbers must reconcile with the underlying source. Do not fabricate missing metrics to make the deck look complete.

## Variance and misses

For material misses:

- state the miss plainly;
- quantify it when evidence allows;
- explain the causal drivers, not excuses;
- distinguish temporary timing from structural change;
- show the corrective action;
- update forecast/assumptions honestly.

Boards generally learn more from precise variance and changed assumptions than from defensive spin.

## Meeting design

When practical, send a pre-read early enough that the live meeting can focus on discussion rather than slide narration. A 48–72 hour window is a common operating heuristic, subject to company cadence and urgency.

Pre-wire genuinely sensitive surprises with the appropriate board stakeholders when governance norms and confidentiality allow. “No surprises” does not mean hiding information; it means creating enough context for a productive formal discussion.

## Investor / governance discipline

Separate:

- factual reporting;
- forecast/management assumptions;
- strategic recommendation;
- formal board decision/approval.

Respect information rights, confidentiality, privilege, securities-law and governance obligations. Pair with `executive-legal` for binding governance, financing, disclosure or securities questions.

## Decision method

1. Identify board-level purpose and audience.
2. Select material facts/metrics and reconcile them.
3. Frame what changed versus plan.
4. Surface top decisions and risks.
5. State management recommendation.
6. Define explicit board asks.
7. Remove operating detail that does not change discussion.
8. Verify the document for consistency, confidentiality and unsupported claims.

## Output contract

Depending on the task, return:

- board narrative/outline;
- decision memo;
- KPI/variance structure;
- risk/ask list;
- speaker prep / likely questions;
- investor update framing.

Use externally appropriate formal prose when producing board/investor-facing artifacts.

## Failure modes

Avoid:

- “everything we did this quarter” decks;
- metrics with changing definitions;
- surprises hidden until the room;
- optimistic forecasts that ignore new evidence;
- stitched specialist prose with no executive narrative;
- vague asks such as “thoughts?” when a decision is actually needed;
- sharing board/legal/comp material with an unnecessarily broad audience.

## Provenance

Original Agentit guidance materially informed by the Board Communications specialist design and board operating heuristics in Sente Labs' OpenExecutive (Apache-2.0). See `THIRD_PARTY_NOTICES.md`.

Attribution

marcmarti9marcmarti9
View sourceMore from marcmarti9 →
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

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 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', ...

686011 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.

3331 votes

catchup

Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.

611 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →