Generate weekly status-request email drafts to outside counsel across the active portfolio — markdown per matter, plus Gmail drafts when the MCP is available. Use when the user asks for OC status requests, weekly outside counsel check-ins, or wants per-matter status emails drafted from the portfolio log.
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "oc-status" 技能: 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/litigation-legal/skills/oc-status/SKILL.md 2. 保存为 ~/.claude/skills/oc-status/SKILL.md 3. 装好后重载技能,告诉我可以用了
To run weekly, set a recurring reminder to invoke /litigation-legal:oc-status. Automated scheduling requires a scheduled-tasks integration, which is not bundled.
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml, filter per default rules (or per flags).~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → outside counsel directive style, signer defaults, budget posture.matter.md + history.md, draft per-matter email.~/.claude/plugins/config/claude-for-legal/litigation-legal/oc-status/[YYYY-MM-DD]/[slug].md.~/.claude/plugins/config/claude-for-legal/litigation-legal/oc-status/[YYYY-MM-DD]/_summary.md — what ran, what was skipped and why.Writing the same status-request email to outside counsel every week across 5–15 matters is mechanical cognitive tax. The content is consistent per matter (status, decisions pending, budget check). The audience is consistent (OC lead partner). The tone is consistent (per house outside-counsel-directive style). A scheduled task drafts all of them; counsel reviews and sends.
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — the filtering and field source~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md — matter context (current posture, open questions)~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md — recent events to inform what to ask about~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → outside counsel directive style, signer name/email, budget postureDefault filter:
status != closedoutside_counsel.firm != null AND outside_counsel.lead != nullnext_deadline within 21 daysSkip matters that just had a status update in the last 10 days (no need to re-ping) and matters where outside_counsel.email is null (email addresses needed for Gmail draft; still produce markdown).
Flags:
--all → draft for every active matter regardless of recency--slug=[slug] → draft for one matter only (ad-hoc request)--no-gmail → skip Gmail draft creation even if MCP is availableEach email has the same skeleton; content is matter-specific.
Subject: per house convention (from ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md outside counsel directive style; fallback: [Matter: [matter name]] — Weekly status update)
Body skeleton:
[lead partner first name],
[One sentence opener — natural, matches house tone.]
Checking in on [matter name]. A few items:
1. **Status since [date of last update captured in history.md]** — what's moved, what's pending? Any filings, hearings, correspondence, or calls since we last touched base?
2. **Upcoming deadlines** — I show [next_deadline from log + any deadlines in matter.md]. Confirm coverage plan and any dates we should add.
3. **Decisions pending** — [pull open questions from matter.md that require OC input; if none, omit this numbered item and renumber]
4. **Budget** — [monthly / quarterly / on-request per `~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md` budget posture]. Where are we against [budget authorization from matter.md]? Any variance to flag?
[If material and relevant: 5. Specific ask — e.g., "Please send me the latest draft of the motion to dismiss before [date]" — drawn from matter.md open questions.]
[Signoff — name, role, contact. From `~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md` signer default for OC directives.]
…
Manage matter workspaces — create, list, switch, close, or detach the active matter. Use in multi-client private practice to keep one client's context separate from another, or when a substantive skill needs to know which matter it's working in.
Draft a DMCA takedown notice, triage one you received, or draft a §512(g) counter-notice. Use when asserting copyright through a §512(c)(3) takedown with the fair-use and perjury gates, when an incoming takedown needs triage into comply / counter / engage / ignore options, or when drafting a §512(g)(3) counter-notice with the consent-to-federal-jurisdiction gate.
Search watched registries for community legal skills, showing matches with descriptions and offering to show the full SKILL.md before install. Use when the user says "browse", "search skills", "find a skill for", "what's out there for", or wants to add a new registry to the watchlist.
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Draft a brief section in house style, consistent with the case theory — every fact cited, every case checked, every argument tied to the theory. Use when the user says "draft the [section]", "write the statement of facts", "argument section on [issue]", or needs a first draft of a brief section.
Brief a case in your preferred format. In drill-me mode, makes the student state the holding first. Use when the user says "brief [case]", "what's the holding in", "case brief", or pastes a case.