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'.
71
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 resourcing), lists specific capabilities, and provides comprehensive trigger guidance. The extensive list of natural trigger phrases covers a wide range of scenarios users might encounter, and the legal-specific terminology ensures strong distinctiveness. The description is well-structured with 'Use when' and 'Trigger on' sections that make skill selection straightforward.
| 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 an explicit 'Use when...' clause and a detailed 'Trigger on:' list covering numerous scenarios. | 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 'who has capacity'. These are highly realistic phrases from legal practice. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in legal matter resourcing and team composition. The domain-specific terminology (gearing, matter team, partner/associate levels) makes 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 workflows, with well-defined modes and clear authority boundaries. However, it is severely over-length, spending hundreds of tokens explaining domain concepts (what gearing is, how law firms staff matters, why continuity matters) that should either be assumed knowledge or split into reference files. The lack of concrete worked examples or templates means a reader must infer what good output looks like rather than seeing it demonstrated.
Suggestions
Extract the three 'Domain Knowledge' sections into separate reference files (e.g., GEARING.md, RESOURCING-CONTEXT.md, CONTINUITY.md) and replace with brief summaries and links in the main skill.
Add a concrete worked example for at least one mode — e.g., a sample Mode 2 gearing review showing actual input data transformed into the output table with variance analysis.
Cut explanatory paragraphs that teach concepts rather than instruct behavior — e.g., 'What gearing is and why it matters' can be reduced to 2-3 bullet points of the specific patterns to flag, since Claude understands the concept.
Add explicit mid-workflow validation steps within each mode, such as 'Verify gearing percentages sum to 100%' or 'Confirm all affected matters have fee basis identified before producing the conflict map.'
| 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, why continuity planning matters). The 'Domain Knowledge' sections are largely educational material that could be condensed to brief bullet points of firm-specific conventions. Significant padding with context-setting paragraphs that don't add actionable value. | 1 / 3 |
Actionability | The skill provides structured modes with clear input requirements and output specifications (e.g., the gearing table format, the four required continuity outputs). However, there is no executable code, no concrete example of a completed analysis, and no template showing what a finished output actually looks like. The guidance is specific in what to produce but lacks concrete worked examples showing the transformation from input to output. | 2 / 3 |
Workflow Clarity | The four modes are clearly defined with input requirements and output expectations. The pre-flight checklist and identifier confirmation are good validation steps. However, there are no explicit validation checkpoints within each mode's workflow (e.g., no 'verify the gearing table sums correctly' or 'confirm cover options are feasible before producing the document'). The fee basis check is a good early gate, but mid-workflow validation is largely absent. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to external files. Domain knowledge sections on gearing, law firm resourcing reality, and continuity planning could easily be split into separate reference files. The M365 Connected Mode section and cross-skill handoffs add significant length that would be better as linked references. Everything is inline, making the skill 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
1eb58a1
- 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.