Skip to content
Security
Skill

/board-deck

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

From plugin
awesome-claude-security
6111 skills17 agents13 commands1 MCP
Install
$ npx -y skills add jassics/awesome-claude-security --skill board-deck --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/board-deck

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

board-deck.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.

Read more
Ships withawesome-claude-security

A Claude Code plugin marketplace for the full cybersecurity & GenAI-security lifecycle — from recon and threat modeling to detection engineering, GRC, and CISO-level strategy. A pentester knows which OWASP test bends a broken-access-control endpoint.

Get the whole plugin

Other skills on awesome-claude-security.