portfolio-status

Original：🇺🇸 English

Translated

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.

1installs

Sourceanthropics/claude-for-legal

Added on2026-08-27

NPX Install

npx skill4agent add anthropics/claude-for-legal portfolio-status

SKILL.md Content

View Translation Comparison →

/portfolio-status

Load

~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md

→ risk calibration (defines how to read the

risk:

field).

Follow the workflow and reference below.

Parse

~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml

. Filter closed matters by default (include with

--all

).

Produce rollup: risk distribution, deadlines in next 14/30/60 days, matters with no update in >30 days, materiality totals, stage distribution.
Flag anomalies — everything marked critical, overdue next_deadline, matters without outside counsel assigned where risk is medium or high.

Portfolio Status

Purpose

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.

Load context

~/.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)

Flags & filters

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

The rollup

markdown

[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.]

Anomaly rules

These are the checks that make the skill useful rather than decorative:

Overdue deadline:
```
next_deadline < today
```
and
```
status != closed
```

Stale:

last_updated < today - 30d

and

status != closed

Conflicts unresolved:

conflicts.status in [pending, not-run]

and

status != closed

3b. Conflicts override active:

conflicts.override.by != null

(never auto-clears)

High-risk uncovered:

risk in [high, critical]

and

outside_counsel.firm == null

Stale reserve:

materiality == reserved

and

last_updated < today - 60d

Hold gap:
```
status in [threatened, active, discovery, trial, appeal]
```
and
```
legal_hold.issued == false
```
— preservation duty attaches at reasonable anticipation, so
```
threatened
```
matters are in scope.
Missing fields: any required field null —
```
risk
```
,
```
materiality
```
,
```
status
```
,
```
opened
```
,
```
conflicts.status
```

Close with the next-steps decision tree

End with the next-steps decision tree per CLAUDE.md

## Outputs

. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.

If the portfolio has more than ~10 matters, or any time the user asks: offer the dashboard (see CLAUDE.md

## Outputs → Dashboard offer for data-heavy outputs

). Shape the offer for this output — counts by risk tier, a timeline of upcoming deadlines, and a sortable matter ledger with status, conflicts check, and last-touched date.

What this skill does not do

Make decisions. It surfaces what needs attention; the user decides priority.
Pretend precision it doesn't have. Exposure midpoints are rough and should be labeled so.
Replace a real MMS. This is a working-memory rollup, not a system of record.