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

Board Deck

ASecurity

Produce a board / executive security presentation — risk posture and direction, top risks in business terms, program progress against strategy, the metrics that matter, and investment asks tied to risk. Use to prepare for a board or leadership meeting. Audience is non-technical decision-makers.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgosecurity

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add jassics/awesome-claude-security --skill board-deck --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Board Deck?

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

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

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: board-deck
description: >-
  Produce a board / executive security presentation — risk posture and direction,
  top risks in business terms, program progress against strategy, the metrics that
  matter, and investment asks tied to risk. Use to prepare for a board or leadership
  meeting. Audience is non-technical decision-makers.
---

# Goal

A concise, decision-oriented deck that gives the board what they need: how exposed
are we, are we improving, and what should they fund or decide — in business language.

# Structure (lead with the answer)

1. **Bottom line** — overall risk posture and direction vs. last review (1 slide).
2. **Top risks** — 3–5 in business terms (loss scenarios, not CVEs), with severity
   and trend (`cyber-risk-quantification`).
3. **Program progress** — where the strategy stands vs. plan; key wins and what's
   behind (`security-strategy`).
4. **Metrics that matter** — a small, stable set (e.g. risk reduction, critical
   remediation %, MTTR, coverage, incident trend) — consistent across meetings so
   trend is readable.
5. **The ask** — investment/decisions needed, each tied to the risk it reduces and
   the consequence of inaction.
6. **Appendix** — supporting detail, incidents, benchmarks, regulatory items.

# Steps

1. Confirm the audience and the **decision/ask** this meeting must produce — build
   backward from it.
2. Pull the risk picture (`cyber-risk-quantification`) and program status
   (`security-strategy`); translate to business language, drop jargon.
3. Keep it tight: one message per slide, few stable metrics, clear asks.
4. Generate the visuals (posture scorecard, risk heat map, trend) with
   `security-diagramming:infographic`; assemble narrative via
   `security-reporting:executive-summary`.

# Output

A board deck (slide outline + content + visual specs) plus a one-page executive
summary. Render visuals with `security-diagramming`.

# Notes

Boards optimize for decisions under uncertainty — lead with posture and the ask, not
a tour of activity. Keep the metric set small and **stable** so trends are
comparable meeting to meeting. Every ask ties to a risk and the cost of not acting.

Attribution

jassicsjassics
View sourceSee grades on GitHubMore from jassics →
SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

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 Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

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

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

3351 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 →