resource-planner

Team structure, gearing analysis, continuity planning, and competing demand management for legal matters. Use when setting up a matter team, reviewing whether work is being done at the right grade, planning cover for an unavailable team member, or managing a resource conflict across matters. Trigger on: 'who should be on this matter', 'team structure', 'gearing', 'right people at the right level', 'partner is doing associate work', 'cover for maternity leave', 'who has capacity', 'team member leaving', 'over-allocated', 'staffing conflict', 'pinch point', 'capacity problem', 'how do we resource this', 'team too senior', 'team too junior'.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is highly actionable and well-sequenced with concrete output templates and explicit gating checkpoints, but it is a long monolithic document with meaningful redundancy across sections and reference-style material that is not split into separate files.

Suggestions

Consolidate the repeated partner-authority boundary and named-firm attribution rule into a single canonical statement and reference it, rather than restating them across Operating Modes, Output Format, and LPM vs Attorney Boundary.

Move dense reference material (gearing failure-mode taxonomy, capacity-signal reliability ranking, M365 connected-mode capabilities, and the future PMS-connector paragraph) into separate reference files under references/, linked from SKILL.md with clear one-level-deep navigation.

Tighten the Time-Sensitive Assumptions section to remove duplication of the capacity-signal-lagging point already made in the Domain Knowledge section.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and rich in domain knowledge Claude does not already know (gearing failure modes, capacity-signal reliability ranking), but several points are restated across sections — partner-authority boundary, named-firm attribution rule (stated three times), and fee-basis-required-before-analysis — which is padding that could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready guidance: an exact gearing-model table with specified columns, verbatim required diagnostic strings (capacity-email check, Mode 4 flag line), the named client-introduction action, enumerated Mode 3 outputs in priority order, and placeholder conventions.	3 / 3
Workflow Clarity	Clear sequencing with a pre-flight confirmation gate, fee-basis gating ("ask before, not after"), four distinct modes each with stated inputs, and an explicit required-output order for Mode 3; the pre-flight checklist and delegation test act as validation checkpoints.	3 / 3
Progressive Disclosure	The body is a large monolithic SKILL.md with no bundle files and all content inline; well-organized into sections, but reference-style material (gearing failure-mode taxonomy, capacity-signal ranking, M365 connected-mode capabilities, the future PMS-connector paragraph) stays inline rather than being split into referenced files.	2 / 3
	Total	10 / 12 Passed

Description

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.

The description is a strong, third-person statement that clearly states what the skill does and when to use it, with a rich set of natural trigger phrases and a distinctive legal-matter-resourcing niche.

Dimension	Reasoning	Score
Specificity	Names the domain plus four concrete capability areas ("Team structure, gearing analysis, continuity planning, and competing demand management") and enumerates specific operating scenarios; lists multiple concrete actions rather than vague language.	3 / 3
Completeness	Explicitly answers both "what" (first sentence) and "when" ("Use when setting up a matter team..."), followed by an explicit "Trigger on:" clause with concrete triggers.	3 / 3
Trigger Term Quality	Extensive natural trigger phrases users would actually say ("who has capacity", "gearing", "pinch point", "partner is doing associate work", "team too senior", "over-allocated"); good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Clear law-firm legal-resourcing niche with distinctive triggers ("gearing", "pinch point", "partner is doing associate work") unlikely to fire for unrelated skills; low conflict risk.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: legalopsconsulting/lpm-skills
Commit: 178ed52

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