matter-intake-scoping
Matter scoping across the full pre-execution arc — organise client data into a structured brief, capture the agreed baseline, or reconstruct scope mid-flight. Use when making sense of client information before a proposal, scoping a new matter, running a kickoff, defining scope, mapping stakeholders, or inheriting a matter mid-flight. Trigger on: 'make sense of this', 'structure this for the proposal', 'scope this matter', 'new matter', 'kickoff', 'what are we doing', 'who are the stakeholders', 'what does success look like', 'matter setup', 'intake', 'I've inherited this matter', 'organise this client data'.
85
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 a strong, well-crafted skill description that clearly defines its domain (matter scoping in the pre-execution phase), lists concrete actions, and provides extensive trigger guidance with both a 'Use when' clause and an explicit 'Trigger on' list of natural user phrases. The description is specific to its niche and unlikely to conflict with other skills. Minor improvement could come from slightly tightening the prose, but overall it is exemplary.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'organise client data into a structured brief', 'capture the agreed baseline', 'reconstruct scope mid-flight'. Also references specific sub-tasks like scoping, kickoff, stakeholder mapping. | 3 / 3 |
Completeness | Clearly answers both 'what' (organise client data, capture baseline, reconstruct scope) and 'when' with an explicit 'Use when...' clause covering multiple scenarios, plus a dedicated 'Trigger on:' list with specific phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say, including conversational phrases like 'make sense of this', 'what are we doing', 'I've inherited this matter', and more formal terms like 'scope this matter', 'intake', 'matter setup'. Good variety of natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche — matter scoping in the pre-execution arc of legal/professional services work. The domain-specific terminology ('matter', 'kickoff', 'intake', 'stakeholders', 'proposal') and the explicit phase boundary ('pre-execution arc') make it highly distinguishable from generic project management or document organization skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with excellent workflow clarity across all four modes, concrete document templates, and clear handoff points to other skills. Its primary weakness is extreme verbosity — it reads more like a comprehensive training manual than lean instructions for Claude, with extensive rationale, philosophy, and explanatory content that inflates the token cost substantially. The content would benefit significantly from splitting into a concise overview SKILL.md with detailed mode instructions in separate reference files.
Suggestions
Reduce the main file by 50-60% by moving each mode's detailed instructions and templates into separate reference files (e.g., references/mode-1-pre-engagement.md, references/mode-4-recovery.md) and keeping only a concise overview with routing logic in SKILL.md.
Remove explanatory sections like 'The problem this solves', 'Operational knowledge — why intake fails', and the extended rationale paragraphs — Claude doesn't need to understand why intake fails to execute the workflow correctly.
Trim the confidence label explanations to a compact reference table rather than multi-paragraph descriptions with epistemic justifications.
Move the M365 Connected Mode section to a separate reference file since it's optional and adds significant length to the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines. It extensively explains why intake fails, the philosophy behind confidence labels, the rationale for LPM vs attorney boundaries, and operational context that Claude doesn't need spelled out at this length. Sections like 'The problem this solves' and 'Operational knowledge — why intake fails' are largely explanatory rather than instructional. Much of the content reads like a training manual for a human LPM rather than lean instructions for Claude. | 1 / 3 |
Actionability | The skill provides highly concrete, copy-paste-ready document templates with specific field structures, table formats, and exact labeling conventions. Each mode has explicit step-by-step instructions with specific outputs, naming conventions, and format blocks. The confidence labeling system, conflict rating scale, delta table format, and handoff blocks are all immediately executable. | 3 / 3 |
Workflow Clarity | Each mode has a clearly sequenced multi-step workflow. Mode 1 has seven explicit steps with validation built in (confidence layering, conflict detection, calibration against standing assumptions). Mode 4 has a clear 5-step backwards methodology with explicit outputs and handoff blocks. Cross-skill handoff points are clearly defined with trigger phrases. The 'brief comes first' rule and mandatory DRAFT labeling serve as validation checkpoints. | 3 / 3 |
Progressive Disclosure | The skill references external files well (standing-assumptions.md, matter-type-profiles, shared-knowledge files) and defines cross-skill handoff points. However, the SKILL.md itself is monolithic — all four modes with full templates and operational philosophy are inline rather than split into separate reference files. The operational knowledge section and M365 connected mode section could easily be separate files, reducing the main file's token footprint significantly. | 2 / 3 |
Total | 9 / 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.