Name: personwise/personwise-internal-change-adoption
Rating: 66.4 (1 reviews)
Author: personwise

personwise/personwise-internal-change-adoption

Employees hear the town hall and still ask — what changes for me? Turn your approved change communications into an interactive digital-human internal change adoption course that answers the questions people will not ask publicly. No speculation about jobs or futures: only what has been communicated, honestly including what is still undecided.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

73%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 content is a thorough, highly actionable operational runbook with explicit validation checkpoints and error-recovery feedback loops. Its weaknesses are verbosity from repeated state handling and a monolithic single-file structure that underuses progressive disclosure despite having real bundle assets.

Suggestions

Move the detailed freshness/update and source-status state-machine prose into a dedicated reference file, keeping SKILL.md to the core command sequence and a one-line pointer.

Consolidate the repeated 'awaiting_sources is a 200 no-op, keep waiting' descriptions into a single canonical note to reduce token cost.

Tighten or relocate the time-sensitive version/contract specifics (e.g. 1.1.6, contract 1.0) so they do not burden the main workflow narrative.

Dimension	Reasoning	Score
Conciseness	The body is dense and information-rich but long; sections like the freshness/update flow and source-status handling repeat state descriptions across multiple subsections and could be tightened without losing clarity.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for each stage (version check, auth begin/wait, readiness, course create, source add/status/retry/detach, run wait/get, course publish/set-access) with exact flags and expected JSON fields.	5 / 5
Workflow Clarity	A clear multi-step sequence runs from readiness through blueprint, source upload, review checkpoints, and publish, with explicit validation gates (ready before advance, fresh reads before mutations, expected-revision, idempotency reuse) and feedback loops for conflicts and failed sources.	5 / 5
Progressive Disclosure	Structure is sectioned and the bundle assets are real referenced files (assets/bootstrap.sh, assets/bootstrap.ps1), but the bulk of operational detail is inlined in SKILL.md rather than split into one-level-deep reference files, so navigation is section-based rather than file-based.	3 / 5
	Total	16 / 20 Passed

Description

86%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 strong: it clearly states what the skill produces and when to use it with explicit trigger language, while adding useful safety and authorization framing. Its main weakness is a somewhat narrow, brand-specific scope that leans toward jargon rather than universally natural user phrasing.

Dimension	Reasoning	Score
Specificity	Names the concrete action ('Produce a grounded interactive digital-human course learners can interrupt with voice questions') and several specifics, but the action set is narrowly described rather than comprehensively listing course-creation operations.	4 / 5
Completeness	Explicitly answers both 'what' (produce a grounded interactive digital-human course) and 'when' ('Use when the user asks for Internal Change Adoption Course... Trigger language: ...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases ('internal change adoption; organizational change; internal software rollout'), but the terms are somewhat niche and lack common synonyms a lay user might say.	4 / 5
Distinctiveness Conflict Risk	The domain is fairly niche (internal change adoption courses) with distinct triggers, but 'organizational change' is broad enough to risk minor overlap with generic change-management skills.	4 / 5
	Total	17 / 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

Reviewed

21 days ago

Table of Contents

Discovery Implementation Validation