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'.
56
63%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/resource-planner/SKILL.mdQuality
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 domain (legal matter team resourcing), lists specific capabilities, and provides comprehensive trigger guidance. The extensive list of natural trigger phrases covers a wide range of user expressions, and the legal-specific terminology ensures distinctiveness. The description is well-structured and concise despite its thoroughness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: team structure setup, gearing analysis, continuity planning, and competing demand management, all scoped to legal matters. | 3 / 3 |
Completeness | Clearly answers both 'what' (team structure, gearing analysis, continuity planning, competing demand management) and 'when' with explicit 'Use when...' clauses and a comprehensive 'Trigger on:' list. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say, including colloquial phrases like 'partner is doing associate work', 'cover for maternity leave', 'pinch point', 'team too senior', and 'how do we resource this'. These are highly natural and varied. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in legal matter team resourcing. The specific legal domain terminology (gearing, matter team, partner/associate levels) and detailed trigger terms make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates strong domain expertise and thoughtful design around law firm resourcing, but it is far too verbose for its purpose. The extensive domain knowledge sections explain concepts at a training-manual level rather than providing concise operational instructions. The skill would benefit significantly from extracting domain knowledge into separate reference files, adding concrete input/output examples for each mode, and tightening the core instructions to focus on what Claude should do rather than explaining why.
Suggestions
Extract the three 'Domain Knowledge' sections (Gearing, Law Firm Resourcing Reality, Continuity Planning) into separate reference files (e.g., GEARING.md, RESOURCING-CONTEXT.md, CONTINUITY.md) and reference them from the main skill with one-line summaries.
Add a concrete worked example for at least one mode — show sample input data and the expected output structure with realistic placeholder content, so Claude can see what a completed analysis looks like.
Reduce explanatory prose that describes concepts Claude already understands (e.g., what gearing is, how law firms staff matters, what a handover note is) to brief bullet points or remove entirely.
Convert each mode's narrative description into a numbered step-by-step workflow with explicit validation checkpoints (e.g., 'Step 1: Confirm fee basis → Step 2: Build gearing table → Step 3: Validate totals against budget → Step 4: Produce .docx').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines. It extensively explains concepts Claude already knows (what gearing is, how law firm staffing works, what a handover note is, how capacity emails work). The 'Domain Knowledge' sections on gearing, law firm resourcing reality, and continuity planning are largely explanatory background that could be reduced to brief bullet points. Much of this reads like a training manual rather than actionable instructions. | 1 / 3 |
Actionability | The skill provides structured modes with clear input requirements and output specifications (e.g., the gearing model table format, the four required continuity planning outputs). However, there is no executable code, no concrete example of a completed analysis, and no sample input/output pairs. The guidance is specific in what to produce but lacks concrete examples showing what good output actually looks like. | 2 / 3 |
Workflow Clarity | The four operating modes are clearly defined with input requirements, and the pre-flight checklist provides a good starting validation step. However, within each mode the workflow is described narratively rather than as clear sequential steps with checkpoints. Mode 3 has the best structure (four required outputs in order), but Modes 1 and 2 lack explicit step-by-step sequences with validation gates. The fee basis check is a good validation checkpoint but is buried in prose. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload content to. The domain knowledge sections (gearing, law firm resourcing reality, continuity planning) are extensive inline content that should be in separate reference files. The cross-skill handoffs and M365 connected mode sections add significant length. With no supporting files, all content is crammed into one document, making it difficult to navigate. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%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
dc6509d
- Reviewed
Table of Contents
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.