internal-comms

Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement, a tool rollout, a policy change, a leadership transition, a layoff, an acquisition close, or an internal product launch — and the audience is employees (not customers). Pairs Prosci ADKAR and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points; industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Triggers on "all-hands announcement", "change comms", "rollout comms", "re-org announcement", "manager talking points", "layoff comms".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

71%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, well-organized operational skill with concrete tooling, an explicit validation gate, and clean progressive disclosure. Its main weakness is redundancy between the Workflow/Scripts and When-NOT-to-use/Distinct-from section pairs, which adds tokens without adding guidance.

Suggestions

Collapse the per-script 'Scripts' section into the Workflow steps (or vice versa) to remove the duplicated tool descriptions and tighten conciseness.

Merge 'When NOT to use' and 'Distinct from' into a single scope/boundary section; they currently restate overlapping redirections to marketing-skill/* and c-level-advisor/*.

Make the validation feedback loop explicit in step 5 (e.g. 'If any anti-pattern is hit, revise the input/builder args and re-run before publishing') to push workflow clarity to the top anchor.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and filled with specialized domain content rather than concepts Claude already knows, but the Scripts section re-covers tools already described in Workflow, and 'When NOT to use' overlaps with 'Distinct from', so it could be tightened.	3 / 5
Actionability	Gives concrete, runnable commands (e.g. 'python3 scripts/comms_template_filler.py --sample') with named scripts and flags, plus an explicit JSON intake enum; the only minor gap is that a full input-JSON example lives in the asset rather than inline.	4 / 5
Workflow Clarity	A clearly numbered five-step sequence with an explicit validation gate (step 5 anti-pattern sweep as a 'do not send' signal) and tool-enforced magnitude/tone checks, though the error-recovery loop ('if anti-pattern, fix and re-run') is implied rather than spelled out as explicitly as the top anchor.	4 / 5
Progressive Disclosure	Well-structured overview with clearly signaled, verified one-level-deep references (references/.md, assets/comms_template.md, scripts/.py) that do not nest further, and content appropriately split across files.	5 / 5
	Total	16 / 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.

An exemplary description: concrete deliverables, explicit trigger phrases, clear what/when framing, and a sharply scoped niche that distinguishes it from adjacent marketing and strategy skills. No verbosity or vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points' — giving comprehensive coverage of the skill's deliverables.	5 / 5
Completeness	Clearly answers 'what' (the four artifacts produced via named tools) and 'when' ('Use when a Head of People Ops... needs to draft and sequence...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Explicit 'Triggers on' clause lists natural phrases a user would say ('all-hands announcement', 'change comms', 're-org announcement', 'manager talking points', 'layoff comms') with good synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Clear niche — internal-only, employee-audience change-management comms — with explicit scope boundary ('audience is employees (not customers)') and distinct triggers, minimizing conflict risk.	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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: business-operations/skills/internal-comms/SKILL.md
Commit: 19392f7

Reviewed: ~13 hours 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.