change-management

Framework for rolling out organizational changes without chaos. Covers the ADKAR model adapted for startups, communication templates, resistance patterns, and change fatigue management. Handles process changes, org restructures, strategy pivots, and culture changes. Use when announcing a reorg, switching tools, pivoting strategy, killing a product, changing leadership, or when user mentions change management, change rollout, managing resistance, org change, reorg, or pivot communication.

Quality

91%

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

82%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 delivers concrete, actionable change-management guidance through sequenced playbooks and diagnostic tables, with a genuine one-level reference file. It is slightly long for an overview and could push more detail into the existing reference, but the structure and actionability are strong.

Suggestions

Trim the repeated Timeline/Hardest phase/Critical reinforcement/Communication sequence scaffolding by collapsing the four change types into a comparison table, and move the per-type week-by-week sequences into references/change-playbook.md.

Surface the change-playbook.md reference earlier (e.g., a 'See also' line near the top) rather than only at the very bottom under 'Detailed References', so the overview reads as a lean pointer to the deep dive.

Add an explicit verify-gate to the org-change and culture-change sequences (e.g., a 'confirm alignment before proceeding' checkpoint) to match the validation rigor already present in the process-change sequence.

Dimension	Reasoning	Score
Conciseness	Mostly efficient actionable prose with tables and sequenced steps, but the ~240-line body repeats a similar Timeline/Hardest-phase/Sequence pattern across four change types and includes some advisory restatement that could be trimmed.	4 / 5
Actionability	Highly concrete for an advisory skill: week-by-week communication sequences ('Week -2: Announce the why + go-live date'), a resistance-pattern table mapping signal to response, fatigue signals/prevention, and checklists (Key Questions, Red Flags).	5 / 5
Workflow Clarity	Each change type has a clearly numbered, time-phased sequence with check-ins (Week 2 adoption check-in, Month 2 retrospective) and a diagnostic resistance table, but not every sequence has an explicit verify-before-proceeding gate.	4 / 5
Progressive Disclosure	Well-structured with clear section headers and a one-level-deep reference ('references/change-playbook.md' — a real bundle file) signaled at the end; however the body is itself a fairly complete reference rather than a lean overview, and the single pointer sits somewhat buried under 'Detailed References'.	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 states a concrete capability set, enumerates four change types it handles, and pairs it with an explicit, synonym-rich 'Use when...' trigger clause. It is concise, third-person, and clearly distinguishable.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions with comprehensive coverage: 'Covers the ADKAR model adapted for startups, communication templates, resistance patterns, and change fatigue management. Handles process changes, org restructures, strategy pivots, and culture changes.'	5 / 5
Completeness	Explicitly answers both: what ('Framework for rolling out organizational changes...') and when ('Use when announcing a reorg, switching tools, pivoting strategy...'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural terms with synonyms: 'announcing a reorg, switching tools, pivoting strategy, killing a product, changing leadership' plus 'change management, change rollout, managing resistance, org change, reorg, or pivot communication' — phrases a user would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear change-management niche with distinct triggers (reorg, pivot, tool switch) and minimal overlap risk with unrelated skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: c-level-advisor/skills/change-management/SKILL.md
Commit: 19392f7

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