status Skill
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report. Published by anthropics in claude-for-legal.
Decision snapshot
Is this a fit?
Developers using claude-for-legal, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
26 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is status Skill?
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report. Published by anthropics in claude-for-legal. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using claude-for-legal
Declared skill metadata
- Source file: legal-clinic/skills/status/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use status Skill
- Use it for developers using claude-for-legal.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/claude-for-legal
- Skill file: legal-clinic/skills/status/SKILL.md
What it does
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Skill instructions
/status 1. Load ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → supervision style, plain-language standards, jurisdiction. 2. Use the workflow below. Read case notes. 3. Generate for the specified audience: - client — plain language, what happened/next/you do/reach us - internal — procedural posture, done since last check-in, upcoming, needs professor input, student's assessment - court — formal status report in caption format per local rules 4. Supervision routing per audience (client-facing and court-ready usually flag). /legal-clinic:status client /legal-clinic:status internal /legal-clinic:status court --- Status: Audience-Aware Case Summaries Purpose Clinics generate enormous numbers of status updates — to clients, to professors, to co-counsel, to courts. Same case, same facts, completely different documents. This skill takes the case notes and produces the right summary for the right reader. Load context ~/.claude/plugins/config/claude-for-legal/legal-clinic/CL
Verified compatibility and discovery
Frequently asked questions
What is status?
status is a open-source AI agent skill with Copy skill directory. Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth.
Who is status best for?
status is best for reusing agent instructions, scripts, and references.
How do I install status?
Install or run status using Copy skill directory. Check status for the latest setup command.
Is status actively maintained?
status may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
