security-comms
From the author
Use to translate a security finding, incident, or program update for a specific audience — board, executives, engineering, customer success, end customers, legal, or procurement. Produces audience-tuned writeups: incident notification, breach disclosure, post-mortem, status update, remediation ask, and customer-facing advisory. Use when the same technical fact needs different framing per stakeholder, when drafting external disclosure, or when an exec/board/customer needs the "so what" without the packet captures. Coordinator skill — route findings and incidents here for the human-readable layer.
Install
npx skills add 26zl/cybersec-toolkit --skill security-comms -a claude-code
Installs to .claude/skills/security-comms/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).OfficialWriting★ 183.6K
- stakeholder-communicationrampstackco/claude-skillsCommunicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on stakeholder update, status report, executive summary, exec review, manage up, communicate bad news, project comms, status meeting, weekly update. Also triggers when a project is going off track and the team needs to communicate it.Writing★ 994
- message-framing-commsitseffi/agentic-osDesign audience-specific framing, drafts, and communication sequence for stakeholder updates.Design★ 117
- roadmap-communicatoralirezarezvani/claude-skillsUse when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.Planning★ 28.7K
- incident-responsecbrock84/headcountRuns a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward. Use this when a compromise is suspected or confirmed, when preparing an incident response plan or running an exercise, when deciding whether something is an incident, or when a breach may trigger notification obligations.Security★ 2.1K
- foundation-stakeholder-updateproduct-on-purpose/pm-skillsProduces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference. Translates meeting outcomes into what-it-means language for readers, with channel variants (slack, teams, email, notion, exec-memo) and audience variants (engineering, design, leadership, customer-facing, mixed). Surfaces a primary CTA up front, flags technical-to-business translations for user verification, and detects thread continuation from prior updates.Design★ 760
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in