Name: internal-comms
Rating: 67.2 (1 reviews)
Author: alirezarezvani

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

81%

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

The canonical home for this skill is internal-comms in alirezarezvani/claude-skills

Quality

Content

63%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.

The body is well-structured and action-oriented with a sound validation-gated workflow, but it is held back by repeated anti-pattern content, a lengthy inlined forcing-question library, and references to bundle files that are not actually present.

Suggestions

Deduplicate the anti-patterns: keep them in references/announcement_anti_patterns.md and have the workflow and Anti-patterns sections point to it rather than restating the list in three places.

Move the forcing-question library into its own reference file (e.g. references/forcing_questions.md) and summarize it in the body to reduce inlined length.

Ship the referenced bundle files (references/*.md, assets/comms_brief_template.md, scripts/*.py) so the signaled one-level-deep navigation actually resolves.

Dimension	Reasoning	Score
Conciseness	Mostly efficient domain-specific content (ADKAR/Kotter/Prosci citations earn their place), but anti-patterns are restated across the workflow step, the Anti-patterns section, and script descriptions, and the forcing-question library is lengthy — could be tightened by deduplicating.	3 / 5
Actionability	Names concrete scripts with specific flags (--profile, --sample, --input, --output) and a copy-paste quick-example command; falls short of 5 only because full invocation examples beyond the single --sample line are not shown.	4 / 5
Workflow Clarity	A clear five-step ordered flow with an explicit validation gate in step 5 ('do not send' signal) and scripts that enforce magnitude/tone rejections; not 5 because error recovery is framed as a gate rather than a spelled-out fix-and-retry loop.	4 / 5
Progressive Disclosure	Section structure is clear and references are one-level-deep and signaled, but the referenced files (references/*.md, assets/comms_brief_template.md) do not exist on disk, and the long forcing-question library plus anti-patterns are inlined while also being referenced — content that should be separate is inline.	3 / 5
	Total	14 / 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 specific, complete, and well-differentiated, naming four concrete deliverables and a full set of natural trigger phrases. It explicitly answers both what and when with minimal conflict risk.

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' — with comprehensive coverage of the deliverables.	5 / 5
Completeness	Explicit 'Use when…' clause plus 'Triggers on…' with concrete phrases clearly answers both what the skill does and when to invoke it.	5 / 5
Trigger Term Quality	'Triggers on "all-hands announcement", "change comms", "rollout comms", "re-org announcement", "manager talking points", "layoff comms"' gives comprehensive natural-term coverage with synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	'the audience is employees (not customers)' carves a clear internal-comms niche with distinct triggers, minimizing overlap with external marketing skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 10 missing	Warning

	Total	14 / 16 Passed

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

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