Automated summary

Generates a complete, read-only status report for a legal matter by aggregating matter data, deadlines, documents, flags, and recent history.

Strengths

Consolidates deadlines, stage progress, documents, and flags into a single view
Explicitly surfaces overdue or imminent deadlines and checks costs disclosure compliance
Explicitly read-only, reducing the risk of accidental changes
Includes git history and prioritized next-step recommendations

Limitations

Assumes a specific file layout (matter.json, .extract.json, rules/stage-expectations.json, activity-log.jsonl)
Relies on an external matter-resolution step and firm-specific legal context
Output is a fixed text template without deep legal analysis beyond configured rules

When to use it

Use when you need a fast overview of an existing client matter, its deadlines, and its flags.

When not to use it

Do not use it to create, modify, or close a matter, or when the matter data files are unavailable.

Security analysis

Safe

Quality score82/100

The skill is a strictly read-only status reporter. It reads local JSON/JSONL files, checks rules files, and runs a bounded read-only `git log` command. There is no network access, no secret exfiltration, no destructive filesystem or shell operations, and it explicitly instructs 'Do not commit.' The only mild sensitivity is handling client PII, but that is inherent to the legitimate legal-domain purpose and stays local. No meaningful execution risk.

Findings

•Reads local matter files containing client PII (DOB, contact details) but is explicitly READ-ONLY and performs no network or write operations.
•Runs a scoped git log command (`git -C matters/ log --oneline -10 -- {id}/`) which is non-destructive.

How this analysis is made

Examples

Matter overview

What's the status of the Martinez matter?

Client-specific summary

Where are we with the Smith case — deadlines and any open flags?

Compliance check

Give me a summary of this matter including whether the costs disclosure was sent.

name: matter-status description: "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."

Matter Status

Name: Matter Status
Author: Skills Guide Bot

Important

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

Instructions

Step 0: Resolve Matter

Follow _shared/resolve-matter.md.

Step 1: Gather Data

Read matter.json fully
Read all .extract.json files (Tier 1) — collect all flags
Check for unanalysed documents
Read last 20 lines of activity-log.jsonl
Check stage expectations from rules/stage-expectations.json
Git history: git -C matters/ log --oneline -10 -- {id}/
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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/matter-status-ms47vq0z/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/matter-status-ms47vq0z' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/matter-status-ms47vq0z/download' --output '.skill-downloads/matter-status-ms47vq0z/SKILL.md.part' && mv '.skill-downloads/matter-status-ms47vq0z/SKILL.md.part' '.skill-downloads/matter-status-ms47vq0z/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/matter-status-ms47vq0z/SKILL.md' && test -s '.skill-downloads/matter-status-ms47vq0z/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/matter-status' && cp -R '.skill-downloads/matter-status-ms47vq0z' '.claude/skills/matter-status'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/matter-status-ms47vq0z'

openskills read 'matter-status-ms47vq0z'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/matter-status-ms47vq0z/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot