stakeholder-comms-planner

Stakeholder mapping, communication plan design, reporting hierarchy, and mid-matter comms updates. Use when setting up a new matter and needing to identify who needs what information, designing the communication rhythm, building reporting structures for multi-jurisdiction programmes, or updating the comms plan when the stakeholder landscape changes. Trigger on: 'stakeholder map', 'who needs to be kept informed', 'communication plan', 'reporting structure', 'who do we report to', 'how often do we meet', 'client wants more updates', 'new contact on the client side', 'build the comms plan', 'reporting hierarchy', 'HQ vs regions', 'who is the decision maker', 'comms rhythm', 'meeting cadence', 'status call schedule'.

Quality

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/stakeholder-comms-planner/SKILL.md

Quality

Discovery

100%

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

This is an excellent skill description that clearly defines its capabilities, provides explicit trigger guidance with both a 'Use when' clause and a comprehensive 'Trigger on' list, and occupies a distinct niche. The description uses proper third-person voice, lists concrete actions, and includes a wide range of natural language trigger terms that users would realistically use. It serves as a strong example of a well-crafted skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: stakeholder mapping, communication plan design, reporting hierarchy construction, and mid-matter comms updates. Also specifies contexts like 'multi-jurisdiction programmes' and 'when the stakeholder landscape changes'.	3 / 3
Completeness	Clearly answers both 'what' (stakeholder mapping, communication plan design, reporting hierarchy, mid-matter comms updates) and 'when' with an explicit 'Use when...' clause covering multiple scenarios, plus a detailed 'Trigger on' list.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms that users would actually say, including conversational phrases like 'who needs to be kept informed', 'client wants more updates', 'new contact on the client side', 'how often do we meet', and more technical terms like 'reporting hierarchy', 'comms rhythm', 'meeting cadence'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche around stakeholder communication planning and reporting structures within a legal/matter management context. The specific domain language ('mid-matter', 'multi-jurisdiction programmes', 'HQ vs regions') makes it highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

35%

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

This skill demonstrates deep domain expertise in legal project management communication planning and contains genuinely useful operational intelligence (the HQ vs regions fix, the union communications sequence rule, the primary contact problem). However, it is significantly over-length, spending many tokens on explanatory rationale and domain education that Claude doesn't need. The skill would benefit greatly from being condensed to its actionable core — table templates, decision rules, boundary rules, and output specifications — with domain knowledge moved to reference files.

Suggestions

Cut explanatory rationale paragraphs (e.g., 'The problem this skill solves', 'The most common communication failure', 'Ad hoc communication is expensive') — these explain concepts Claude already understands. Reduce domain knowledge sections to decision rules and reference tables only.

Add a concrete worked example for at least one mode — e.g., a completed Mode 1 stakeholder register with 4-5 sample rows showing how quadrant classification and sensitivities are actually populated, so Claude can pattern-match rather than interpret abstract descriptions.

Move the three domain knowledge sections (Stakeholder Mapping, Communication Planning, Reporting Hierarchy) into separate reference files and link to them from the main skill, keeping only the decision rules and table templates inline.

Add explicit validation checkpoints within each mode — e.g., 'Before finalising Mode 1: verify every Manage closely stakeholder has a named preferred channel and frequency; verify sensitivities column is populated for all High power stakeholders.'

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~3000+ words. It explains concepts Claude already understands (what ad hoc communication is, why reporting hierarchies fail, what RASIC means), provides extensive rationale paragraphs that don't add actionable value, and includes lengthy domain knowledge sections that read more like a training manual than operational instructions. The 'problem this skill solves' paragraph and many explanatory passages could be cut entirely.	1 / 3
Actionability	The skill provides concrete table structures, specific column headers, and clear output requirements (CSV export, BLUF format, .docx default). However, there is no executable code, no template examples showing what a completed stakeholder register or communication plan actually looks like with sample data, and the guidance remains largely descriptive rather than demonstrating concrete outputs. The RASIC and power/interest frameworks are explained but not shown applied to an example.	2 / 3
Workflow Clarity	The four operating modes provide a clear sequence (Mode 1 → Mode 2 → Mode 3 → Mode 4), and Mode 4 has explicit required outputs. However, there are no validation checkpoints within modes — no 'verify the register is complete before proceeding to Mode 2' steps, no feedback loops for error recovery, and the 'Before Starting Any Mode' section is a good gate but the individual modes lack internal verification steps. The cross-skill handoffs are well-documented but the within-mode workflows are underspecified.	2 / 3
Progressive Disclosure	The content is structured with clear headers and sections, and cross-skill handoffs reference other skills appropriately. However, the domain knowledge sections are massive inline blocks that could be split into separate reference files. The skill is monolithic — all domain knowledge for stakeholder mapping, communication planning, and reporting hierarchy is inline rather than referenced. For a skill this long, separate reference documents would significantly improve navigability.	2 / 3
	Total	7 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: legalopsconsulting/lpm-skills
Commit: 1eb58a1

Reviewed: 11 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.