$ loading_
Roll up the portfolio from _log.yaml — risk distribution, upcoming deadlines, stale matters, materiality totals, stage distribution, and flagged anomalies. Use when the user asks "where do we stand", "how many open matters", or wants a portfolio rollup or status across all active matters.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "portfolio-status" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/litigation-legal/skills/portfolio-status/SKILL.md 2. Save it as ~/.claude/skills/portfolio-status/SKILL.md 3. Reload skills and tell me it's ready
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → risk calibration (defines how to read the risk: field).~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml. Filter closed matters by default (include with --all).One read that answers: what do I own right now, what needs attention, and what's slipping? Output is scannable — designed for a counsel who has three minutes before their next call.
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — source of truth~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md — risk calibration (to interpret risk/materiality fields correctly)Default: active matters only (exclude status: closed).
Flags:
--all — include closed--risk=high (or critical / medium / low) — filter by risk band--stale — only matters with last_updated > 30 days--type=employment — filter by matter type--owner=[name] — filter by business/HR/comms owner[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
# Portfolio Status — [today]
**Active matters:** [N]
**Closed (ytd):** [N] *(shown only with --all)*
---
## By risk
| Risk | Count | Matters |
|---|---|---|
| Critical | [N] | [slugs] |
| High | [N] | [slugs] |
| Medium | [N] | [count only — expand with `--risk=medium`] |
| Low | [N] | [count only] |
## Upcoming deadlines
| Within | Matters |
|---|---|
| 14 days | [slug — deadline — brief] |
| 15–30 days | [...] |
| 31–60 days | [...] |
*Overdue `next_deadline` flagged separately below.*
## Materiality
| Category | Count | Total exposure (midpoint) |
|---|---|---|
| Reserved | [N] | [$X] |
| Disclosed | [N] | [$X] |
| Monitored | [N] | — |
| None | [N] | — |
## By stage
[table: pleadings / discovery / dispositive motions / trial prep / settlement / appeal]
---
## ⚠️ Anomalies & flags
- **Overdue deadlines:** [list slugs where next_deadline has passed]
- **Stale (>30d no update):** [list]
- **Conflicts unresolved:** [list slugs with `conflicts.status in [pending, not-run]`]
- **Conflicts bypassed (override active):** [list slugs where `conflicts.override.by` is populated — permanent flag until manually cleared]
- **High/critical risk without outside counsel:** [list]
- **Reserved without last_updated in >60d:** [list] — reserve recalibration likely overdue
- **Hold not issued on active litigation:** [list]
- **Missing fields:** [slug → field]
---
## Closing advice
[One or two sentences on what to look at first, if anything stands out. Not boilerplate — only if something truly stands out.]
These are the checks that make the skill useful rather than decorative:
next_deadline < today and status != closedlast_updated < today - 30d and status != closedconflicts.status in [pending, not-run] and status != closed
3b. Conflicts override active: conflicts.override.by != null (never auto-clears)risk in [high, critical] and outside_counsel.firm == nullmateriality == reserved and last_updated < today - 60dstatus in [threatened, active, discovery, trial, appeal] and legal_hold.issued == false — preservation duty attaches at reasonable anticipation, so threatened matters are in scope.…
Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
Drafts board or committee meeting minutes in your house format. Auto-detects upcoming board and committee meetings from your calendar, asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes. Also handles written consents in lieu of meetings. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", "written consent", or calendar detection of an upcoming board or committee event.
Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".
Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.