Run any Skill in Manus with one click

board-deck

Stars6

Forks0

UpdatedMay 31, 2026 at 17:04

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jassics

jassics/awesome-claude-security

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer and Information Systems ManagersManagement Occupations·SOC 11-3021

SKILL.md

readonly

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)

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

Steps

Confirm the audience and the decision/ask this meeting must produce — build backward from it.
Pull the risk picture (cyber-risk-quantification) and program status (security-strategy); translate to business language, drop jargon.
Keep it tight: one message per slide, few stable metrics, clear asks.
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.

More from this repository

same repository

config-security-scan

jassics/awesome-claude-security

Statically review a Claude Code / AI-agent setup for security misconfigurations — risky hooks, over-broad permissions, untrusted or cleartext MCP servers, hardcoded secrets, endpoint redirection, over-privileged agents/skills, and prompt-injection in steering files. Use when asked to audit a `.claude/` directory, `settings.json`, `.mcp.json`, a plugin/marketplace, or `CLAUDE.md`, or to add a config-security gate to CI. Drives the `agentscanner` CLI.

2026-06-276

ml-pipeline-security-review

jassics/awesome-claude-security

Review the training / MLOps pipeline for security weaknesses — data-poisoning surface, feature-store and data-source trust, experiment-tracking and model-registry access control, secrets, and reproducibility/provenance. Use when assessing how models are built and promoted, not how they're served or consumed.

2026-06-016

ml-supply-chain-review

jassics/awesome-claude-security

Review the provenance and integrity of models, datasets, and ML artifacts pulled from hubs/registries — unsafe deserialization (pickle, PyTorch/Keras/joblib), untrusted model sources, model/dataset tampering, and signing. Use when an app loads third-party model weights or datasets, or before promoting a model.

2026-06-016

model-serving-security

jassics/awesome-claude-security

Harden a deployed model inference endpoint — authn/authz, rate limiting and abuse control, input validation, and exposure to model-extraction / inversion / membership-inference attacks. Use when reviewing how a model is served (REST/gRPC, Triton/TorchServe/KServe, or a hosted inference API), not how it was trained.

2026-06-016

export-to-drive

jassics/awesome-claude-security

Export a finished security artifact (report, executive summary, diagram, spreadsheet of findings) to Google Drive — right folder, clear naming, and shareable with the intended audience. Use when a deliverable needs to be handed to stakeholders who live in Drive/Docs/Sheets rather than a wiki or tracker.

2026-06-016

publish-finding-to-jira

jassics/awesome-claude-security

Turn a security finding (vuln, pentest issue, review item) into a well-formed Jira issue — mapped severity→priority, remediation/repro in the body, labels and components set, and dedup-checked against existing issues. Use when findings need to become tracked, assignable work in Jira.

2026-06-016

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)

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

Steps

Confirm the audience and the decision/ask this meeting must produce — build backward from it.
Pull the risk picture (cyber-risk-quantification) and program status (security-strategy); translate to business language, drop jargon.
Keep it tight: one message per slide, few stable metrics, clear asks.
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.