security-comms

Translate technical security work into the language of non-security audiences — board, executives, engineering, customer success, customers, legal, procurement, sales. Covers incident communication, post-mortem narrative, audit-findings-for-stakeholders, risk justification, security spend justification, and customer-facing breach disclosure. Use when the user mentions 'security comms,' 'communicate this finding,' 'explain to my boss,' 'board update,' 'executive summary,' 'incident communication,' 'breach notification,' 'customer disclosure,' 'security memo,' 'post-mortem narrative,' 'risk justification,' 'why this matters to the business,' 'translate this finding,' 'stakeholder update,' or has technical security work that needs to land with a non-security audience.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, practitioner-oriented instruction skill: it distinguishes seven audiences with concrete format guidance, gives a sequenced two-mode workflow with real validation checkpoints, and ships six usable templates. The main weaknesses are light rhetorical padding in the intro and a single-file layout where some templates could live in separate reference files.

Suggestions

Trim the editorializing in the opening two paragraphs ('The skill that closes the gap every other skill produces', 'two to three times a week') — they add tokens without actionable value.

Consider moving the six templates into a references/ file (or per-audience reference files) and keeping SKILL.md as an overview that links to them, improving progressive disclosure and token budget.

Add at least one fully worked example (real content, not just placeholders) for the most common deliverable so Claude has a concrete register model to emulate.

Dimension	Reasoning	Score
Conciseness	The body is largely substantive (audience-specific formats, templates, boundaries), but the opening framing — 'The skill that closes the gap every other skill produces' and 'the skill security practitioners reach for two to three times a week' — is rhetorical padding that could be trimmed without loss.	4 / 5
Actionability	Provides six concrete, copy-paste-ready templates with placeholders (board update, exec memo, customer disclosure, post-mortem, audit-findings, SE FAQ) plus a sequenced workflow; minor gaps in that no template is shown fully filled with a worked example.	4 / 5
Workflow Clarity	Two clearly sequenced modes (draft / review) with explicit validation checkpoints — step 6 second-reviewer pass, the Mode 2 review checklist (audience/decision/jargon/hedging/specificity), and the legal/CEO/CISO review requirements for outward-facing comms — plus feedback loops for error recovery.	5 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent), so all content is inline in one well-organized file with clear section headers (audiences, workflow, templates, boundaries, references); the six full templates are substantial enough that splitting some into reference files could improve navigability, but the current single-file structure is good.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it names a clear niche, enumerates concrete deliverable types, and provides a rich set of natural trigger phrases in third-person voice. Both the 'what' and 'when' are answered explicitly and comprehensively.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete communication deliverables — 'incident communication, post-mortem narrative, audit-findings-for-stakeholders, risk justification, security spend justification, and customer-facing breach disclosure' — giving comprehensive coverage of the skill's actions.	5 / 5
Completeness	Explicitly answers both 'what' (translate technical security work for non-security audiences, covering the listed deliverable types) and 'when' via a concrete 'Use when the user mentions...' clause with many trigger phrases; written in third person.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases including synonyms users actually say — 'security comms,' 'explain to my boss,' 'board update,' 'translate this finding,' 'stakeholder update' — covering the full range of ways a user might request this skill.	5 / 5
Distinctiveness Conflict Risk	Clear niche — translating security work for non-security audiences — with distinct trigger phrases that are unlikely to fire for the upstream audit/incident/governance skills it references.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: briiirussell/cybersecurity-skills
Path: skills/security-comms/SKILL.md
Commit: c9ade03

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.