Cyber Whitepaper Builder is a skill designed for cybersecurity consultants, risk advisors, and business development teams who need to convert technical material into polished, client-facing documents. It accepts raw technical intelligence, incident reports, and sector trend data, then structures that input into one of three output formats: a 2–4 page Executive Brief, a concise One-Pager suitable for stakeholder meetings, or a full deep-dive Whitepaper.

The skill uses a “Before You Begin” gate that locks in audience, industry context, and source material before any drafting starts. This enforces workflow consistency and reduces the risk of producing documents that miss their intended readers. All output is framed around industry-standard consulting frameworks, translating technical jargon into business-risk language targeted at boards and C-suites.

A core design constraint is evidence integrity: the skill separates confirmed facts from public reporting and threat actor claims, annotating the distinction explicitly rather than allowing unsupported forensic or regulatory conclusions to appear in the final text. The tone is advisory-first — intended to position a consulting firm as knowledgeable without functioning as a direct sales pitch.

This skill is appropriate when the primary task is document drafting from supplied inputs. It does not perform live threat intelligence gathering, scan networks, query external databases, or replace human expert review of regulatory conclusions.

Use cases

Draft an executive brief summarizing a recent ransomware incident for a client's board

Produce a sector-specific one-pager on emerging threat trends for a stakeholder meeting

Convert a technical vulnerability report into business-risk language for C-suite consumption

Build a commercial-ready whitepaper to support a cybersecurity consulting firm's thought leadership

Generate advisory documents that separate verified findings from unconfirmed threat actor claims

Standardize document structure across multiple client engagements using consistent consulting frameworks

When to use it

Cybersecurity consultants need to turn raw technical intel or incident reports into structured client documents quickly

Business development teams require professionally formatted advisory content without starting from a blank page

Output must clearly distinguish confirmed evidence from public reporting or threat actor statements

Documents need to be framed for board or C-suite audiences rather than technical security teams

When not to use it

Live threat intelligence collection or real-time network scanning is required

The task involves querying external databases, SIEMs, or threat feeds directly

Legal or regulatory conclusions require certified human expert sign-off beyond document structuring

The audience is technical security engineers who need raw, unformatted data rather than executive prose

No source material is available to supply — the skill structures input, it does not generate intelligence