portfolio-status

Summarize litigation case portfolios from a local matters log into structured markdown.

183|37|Updated May 15, 2026
One-click install
npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill portfolio-status-zhou210712
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portfolio-status
Source: https://github.com/zhou210712/claude-for-legal-ZH/tree/main/litigation-legal/skills/portfolio-status
Command: npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill portfolio-status-zhou210712

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns a bulky litigation case log into a fast, decision-ready overview of risks, deadlines, stale matters, and missing signals—so you can quickly see what needs attention next.

Core Features & Use Cases

  • Risk-calibrated portfolio summary: Aggregates case counts and risk distribution using the repository’s configured risk interpretation rules.
  • Deadline timeline for the next 14/30/60 days: Surfaces upcoming next_deadline nodes and clearly flags overdue deadlines.
  • Exception detection and escalation signals: Flags stale cases, unresolved conflicts, high/critical cases without outside counsel, evidence hold gaps, and missing required fields.
  • Use Case: Before a client call, quickly answer “How many cases do we have and what’s most urgent right now?” with a structured snapshot.

Quick Start

Ask the assistant: “Run portfolio-status for my active litigation matters and show the risk and deadline highlights for the next 30 days, including exceptions.”

Frequently Asked Questions about portfolio-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize my litigation case portfolio to identify urgent deadlines and risks?

To summarize your litigation case portfolio, parse your local matters log to compute risk distribution, upcoming deadline nodes, and stale items. This produces a structured markdown overview of overall status and operational rollups across configured time windows.

What is the best way to track upcoming deadlines and overdue items in a litigation case log?

Tracking upcoming litigation deadlines requires parsing your matters log to surface next_deadline nodes for the next 14, 30, or 60 days. This approach clearly flags overdue deadlines and stale cases needing immediate escalation.

How does risk assessment work when aggregating case portfolio data from a matters log?

Risk assessment in a case portfolio works by loading risk calibration rules from your plugin configuration, then applying those interpretations to aggregate case counts. This generates a risk distribution breakdown across your entire active litigation log.

Can I use a local matters log to detect exception signals like unresolved conflict checks in my case portfolio?

Yes, you can parse a local matters log to detect exception signals across your case portfolio. This flags unresolved conflict checks, high-risk cases lacking outside counsel, evidence hold gaps, and missing required fields for escalation.

Does portfolio-level legal operations management require specific dependencies or external tools?

Portfolio-level legal operations management requires no external dependencies. It parses a configured local _log.yaml file and loads risk calibration from the plugin CLAUDE.md to produce structured markdown summaries.

Why are some cases flagged as stale items during periodic legal operations rollups?

Cases are flagged as stale items during legal operations rollups when they meet configured exception rules for inactivity. Parsing the matters log identifies these stale cases alongside overdue deadlines and missing fields for escalation.