local-counsel-manager-scott-margetts
End-to-end external local counsel lifecycle management for multi-jurisdiction legal matters. LC selection criteria and capability assessment, engagement setup and instruction design, performance monitoring and check-in cadence, scope enforcement, and relationship escalation. Use when selecting local counsel for a jurisdiction, designing LC instructions, managing the LC check-in rhythm, enforcing scope boundaries when LC signals overreach, or escalating a performance or relationship issue beyond the matter team. Trigger on: 'which LC should we use', 'LC instruction', 'brief the local counsel',
npx skills add lawve-ai/awesome-legal-skills --skill local-counsel-manager-scott-margetts --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Orchestrates the external local counsel lifecycle for multi-jurisdiction matters, covering firm selection, engagement setup, instruction design, performance monitoring, scope enforcement, and relationship escalation. It defines roles between the LPM and supervising attorney, aims to prevent instruction failures, and provides structured modes for selection (Mode 1), instruction/design (Mode 2), and performance monitoring (Mode 3). Trigger phrases guide when to deploy.
How it works
The skill outlines three operating modes:
- Mode 1: LC selection and engagement setup. It requires input on jurisdiction, matter type, scope, and timelines, and outputs a selection recommendation memo with placeholders for missing inputs. It enforces eight required sections in the engagement letter when produced.
- Mode 2: LC instruction design and management. It designs an instruction letter with eight sections: Matter Context, Scope Inclusions, Scope Exclusions, Deliverables, Timeline, Fees, Contact, and Reporting. It uses placeholders for any missing non-identifier inputs and compiles a “Gaps requiring confirmation before issue” section at the end. It can produce the letter immediately.
- Mode 3: LC check-in and performance monitoring. It manages check-in cadence and tracks performance signals such as response times, update quality, issue flagging, and milestone delivery against the instruction timeline. Cadence is set in the instruction letter (weekly, fortnightly, monthly). The skill emphasizes that managing instruction and scope boundaries is the primary LPM task and that escalations depend on established processes.
When to use it
- Selecting local counsel for a jurisdiction with no preferred firm
- Setting up a new LC engagement (instruction design, scope, engagement terms)
- Managing the LC check-in cadence and response health across the network
- Enforcing scope when LC signals additional work or questions their brief
- Escalating LC performance or relationship issues beyond the matter team
What it can touch
- Tools: claude-code
- Output targets: LC instruction letters and engagement-related documents produced per Mode 1 or Mode 2 rules. The skill prescribes structure, placeholders, and escalation triggers, but does not execute legal analysis.
Caveats
- Focuses on coordination and instruction architecture; legal content remains with supervising attorney
- Scope creep and ambiguity are addressed by explicit inclusions, exclusions, and milestone definitions in Mode 2
- It does not handle LC invoicing or cashflow modeling; those fall to billing-cycle-manager modes 2 and 3 when necessary
# Local Counsel Manager You are a Legal Project Management skill that manages the external local counsel lifecycle on multi-jurisdiction legal matters — from firm selection and engagement setup through instruction management, performance monitoring, scope enforcement, and relationship escalation. Managing local counsel is a coordination discipline, not a legal one. The LPM owns the instruction architecture, the check-in cadence, the scope boundary, and the escalation path. The supervising attorney owns the legal content of the advice and the firm relationship at partnership level. This distinction matters most when things go wrong: a scope dispute is an LPM conversation until it isn't, and knowing when to escalate is the core judgment this skill encodes. The most common failure modes on LC networks are not capability failures — they are instruction failures. LC firms interpret ambiguity as authorisation. Gaps in scope letters become scope creep. Timeline assumptions embedded in emails become undocumented commitments. This skill is designed around preventing those failures, not just responding to them. ## When to use this skill - Selecting local counsel for a jurisdiction where no p
- When to use this skill
- Input Classification — Run This First, Before Selecting a Mode
- Boundary with billing-cycle-manager
- Operating Modes
- Mode 1 — LC selection and engagement setup
- Mode 2 — LC instruction design and management
- Mode 3 — LC check-in and performance monitoring
- Mode 4 — LC scope enforcement and relationship escalation
- Domain Knowledge — LC Network Management
- The instruction failure pattern
- LC response quality signals
- Multi-jurisdiction LC network coordination
- Output Format
- LPM vs Attorney Boundary
What does the local-counsel-manager-scott-margetts skill do?
End-to-end external local counsel lifecycle management for multi-jurisdiction legal matters. LC selection criteria and capability assessment, engagement setup and instruction design, performance monitoring and check-in cadence, scope enforcement, and relationship escalation. Use when selecting local counsel for a jurisdiction, designing LC instructions, managing the LC check-in rhythm, enforcing scope boundaries when LC signals overreach, or escalating a performance or relationship issue beyond the matter team. Trigger on: 'which LC should we use', 'LC instruction', 'brief the local counsel',
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill local-counsel-manager-scott-margetts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.