本文へ移動
cccskills
無料GitHub で公開

status

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md7.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

/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/CLAUDE.md → supervision style, plain-language standards (for client-facing), jurisdiction. Case notes for facts.

Audience modes

Client-facing

Reader: The client. Probably stressed. Possibly unfamiliar with legal process. Reading level per ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md plain-language standards (default 6th grade).

Include:

  • What's happened since they last heard from the clinic
  • What's happening next and when
  • What (if anything) they need to do
  • How to reach the clinic

Don't include:

  • Legal analysis (they don't need to know the IRAC)
  • Weaknesses in their case (unless it's time to have that conversation — and that's a call for the professor, not a status update)
  • Jargon

Review label for the student (not for the client — strip before sending): [AI-ASSISTED DRAFT — requires student review and supervision step per plugin config]

Check your jurisdiction's student practice rule for required law-student sign-off language; some jurisdictions require specific forms.

Dear [Client],

I wanted to update you on your case.

**What's happened:** [Plain English. "We filed your answer with the court on
[date]" not "The responsive pleading was submitted."]

**What's next:** [What and when. "The court scheduled a hearing for [date] at
[time]. You need to be there." Or: "We're waiting for the landlord's lawyer
to respond. That could take a few weeks."]

**What you need to do:** [Specific and clear. Or: "Nothing right now — we'll
let you know when we need something from you."]

**How to reach us:** [Clinic phone, hours, student name]

[Student name]
Law Student, Certified Legal Intern
Under the supervision of [Supervising Attorney]
[Clinic name]

Before sending: sending a client status update is a consequential action. The gate is the supervision workflow in ## Supervision style in ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md, reinforced by the Part 0 role check confirming a licensed supervising attorney owns the setup. Confirm the draft has been reviewed per the supervision protocol (queue / flag / lighter-touch) and all internal review labels ([AI-ASSISTED DRAFT], [VERIFY], etc.) have been removed from the client-facing copy.

Internal (for the professor)

Reader: The supervising professor. Knows the law. Wants to know where the case stands and what the student needs from them.

Include:

  • Procedural status (where in the life of the case)
  • What's been done since last check-in
  • What's coming up (deadlines, hearings)
  • Issues needing professor input
  • Student's assessment (how it's going, concerns)
# Status: [Client] — [Matter] — [date]

**Student:** [name] | **Procedural posture:** [pre-filing / answer filed /
discovery / motion pending / etc.]

## Since last check-in

- [What's been done]

## Upcoming

| Date | What | Action needed by |
|---|---|---|
| [date] | [deadline/hearing] | [date] |

## Needs professor input

- [Question or decision point — specific]

## Student's assessment

[How it's going. Strengths, concerns, strategic questions. This is where the
student's thinking shows.]

---
[AI-ASSISTED DRAFT — student should revise the assessment section especially;
that's your thinking, not a summary of notes]

Court-ready

Reader: A judge or clerk. Formal. Specific to what the court needs (often a status report ordered by the court, or a statement in advance of a status conference).

Include:

  • Procedural history (briefly)
  • Current status of discovery/motions/settlement
  • What's outstanding
  • Proposed next steps or scheduling

Format: Per local rules. Caption, signature block, certificate of service if filed.

═══════════════════════════════════════════════════════════════════════
  AI-ASSISTED DRAFT — requires student analysis and attorney review
  Court filings ALWAYS require professor review before filing
═══════════════════════════════════════════════════════════════════════

[Caption per jurisdiction — VERIFY against current local rules]

STATUS REPORT

[Party] respectfully submits this status report pursuant to [the court's
order of [date] / local rule [X] / in advance of the status conference
scheduled for [date]].

1. Procedural history: [brief]

2. Current status: [discovery status / motion status / settlement status]

3. Outstanding matters: [what's pending]

4. Proposed next steps: [scheduling, if the court wants input]

[Signature block — student attorney under supervision of [Professor]]

[Certificate of service if filing]

---

[VERIFY: caption format, local status report requirements, service
requirements — per current [Court] rules]

Supervision routing

Per ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md:

  • Client-facing → usually a flag trigger (client communication)
  • Internal → no flag (it's going to the professor anyway)
  • Court-ready → always flagged if formal queue enabled (court filings)

What this skill does NOT do

  • Decide what to tell the client. Especially on bad news or case weaknesses — that's a conversation for the student and professor to have, then the student to have with the client. Status updates are status, not strategic advice.
  • File anything with a court. Drafts the document; professor reviews; filing per clinic procedure.
  • Replace the student's assessment in internal status. The "student's assessment" section is the student's thinking — the draft can scaffold it but can't write it.

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6562026年9月30日 更新

Detects when Luminance, Kira, or a similar bulk-review tool is in use, hands off the high-volume clause extraction to it, and QAs its output per the trust level in `~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md`. Use when user says "send to Luminance", "bulk review", "AI extraction", or when diligence-issue-extraction hits a high-volume category.

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6562026年9月30日 更新

Run an AI impact assessment — structured intake, risk analysis, regulatory classification per regime in scope, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed impact assessment in `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md`. Use when user says "impact assessment for", "assess this AI use case", "run an AIA", "generate an AIA", "we need to document this AI system", "AI risk assessment for X", or follows a conditional triage result.

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6562026年9月30日 更新

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6562026年9月30日 更新

Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6562026年9月30日 更新

Bar prep questions — MBE or essay, targeted at your weak subjects and bar jurisdiction. Tracks misses and comes back to patterns. Use when the user says "bar prep", "MBE questions", "practice essay", or "test me for the bar".

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6562026年9月30日 更新

anthropics のスキルをすべて見る

このスキルの問題を報告する