MA

Generates a comprehensive summary for a specific legal matter, including deadlines and recent history.

Install

mkdir -p .claude/skills/matter-status && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14563" && unzip -o skill.zip -d .claude/skills/matter-status && rm skill.zip

Installs to .claude/skills/matter-status

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Shows a complete status summary for a matter. Use when Mandy says 'status', 'what's happening with', 'where are we with', 'summary', or asks about a specific client's matter. Shows client details, deadlines, stage expectations, documents, flags, letters, financials, and recent history.
286 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Read `matter.json` and all `.extract.json` files
  • Check for unanalysed documents
  • Read the last 20 lines of `activity-log.jsonl`
  • Check stage expectations from `rules/stage-expectations.json`
  • Retrieve git history for the matter ID
  • Check compliance for costs disclosure

How it works

The skill gathers data from various files like `matter.json`, `.extract.json`, `activity-log.jsonl`, and `rules/stage-expectations.json`. It also checks git history and compliance, then presents a structured summary.

Inputs & outputs

You give it
A specific client's matter
You get back
A complete status summary including client details, deadlines, stage expectations, documents, flags, letters, financials, and recent history

When to use matter-status

  • Checking matter progress
  • Summarizing case deadlines
  • Reviewing financial status

About this skill

Matter Status

Important

  • READ-ONLY. Do not commit.
  • Resolve matter first.

Instructions

Step 0: Resolve Matter

Follow _shared/resolve-matter.md.

Step 1: Gather Data

  1. Read matter.json fully
  2. Read all .extract.json files (Tier 1) — collect all flags
  3. Check for unanalysed documents
  4. Read last 20 lines of activity-log.jsonl
  5. Check stage expectations from rules/stage-expectations.json
  6. Git history: git -C matters/ log --oneline -10 -- {id}/
  7. Check compliance: costs disclosure sent?

Step 2: Present

CLIENT: name, DOB, contact, preferred method
MATTER: ID, type, stage, sub_stage, claim number, DOI
INJURY: mechanism, body parts, work capacity, CoC status
INSURER: name, agent, contact
LIMITATION: expiry date, time remaining
DEADLINES: all with status (✓ met / ⚠ overdue / ⏰ imminent / ○ pending)
STAGE EXPECTATIONS: checklist (✓ / ⚠ / ○)
COSTS DISCLOSURE: s174 status
DOCUMENTS: list with analysed status
FLAGS: open flags with severity
LETTERS: all with status
FINANCIALS: estimated value, fees, disbursements
RECENT HISTORY: last 10 git entries
NEXT STEPS: prioritised recommendations

When not to use it

  • When the skill is expected to commit changes
  • When the matter has not been resolved first

Limitations

  • The skill is READ-ONLY; it does not commit changes.
  • The skill requires the matter to be resolved first.
  • The skill only reads the last 20 lines of `activity-log.jsonl` and last 10 git entries.

How it compares

This workflow aggregates disparate data sources into a single, complete status summary for a matter, providing a holistic view more efficiently than manually checking each source.

Compared to similar skills

matter-status side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
matter-status (this skill)04moNo flagsIntermediate
meeting-briefing26moNo flagsIntermediate
capa-officer22moReviewAdvanced
subcontractor-sow-builder02moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

meeting-briefing

anthropics

Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.

213

capa-officer

alirezarezvani

CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use for CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization.

210

subcontractor-sow-builder

BdM-15

Drafts a federally-defensible SOW or PWS the prime issues to a subcontractor / teaming partner — same FAR 37.102(d) / 37.602 / 16.601(c)(2) / 16.306(d) discipline a contracting officer applies, opposite seat. USE WHEN the user asks to \"write a SOW for our sub\", \"draft a PWS for [Partner]\", \"bui

00

archon

coleam00

Interactive Archon integration for knowledge base and project management via REST API. On first use, asks for Archon host URL. Use when searching documentation, managing projects/tasks, or querying indexed knowledge. Provides RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning. Always try Archon first for external documentation and knowledge retrieval before using other sources.

9140

linear

lobehub

Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.

10117

zapier-workflows

davila7

Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.

11101

Search skills

Search the agent skills registry