SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsclient-comms-log

client-comms-log

General & other

View repository

Updated 10-15 20:29

About this skill

/client-comms-log
  1. Use the following workflow.
  2. Require a case number (prompt if not provided).
  3. Route by flag:
    • --add(default): record direction, medium, student, summary, action items, follow-up deadline. Confirm with the user. Append (newest first) to ~/.claude/plugins/config/claude-for-legal-zh/legal-clinic/client-comms/[案件编号]/log.md。
    • --read: show the most recent N entries.
    • --summary: one-paragraph brief read.
    • --patterns: scan for unanswered communications, missed follow-ups, language gaps, tone shifts, contact gaps. Supervisory-oriented.
  4. Integration: if the entry creates a deadline, propose /legal-clinic:deadlines --add; route to --summary via /legal-clinic:semester-handoff。
Client Communication Log

Purpose

Four reasons to keep this log:

  1. Practice risk protection. If a client claims "no one ever told me [X]," a dated entry showing otherwise is the answer. Clinic supervisors bear practice responsibility for students' practice work; contemporaneous records protect them.
  2. Handoff continuity. Next semester's students take over the case and read the log; they don't re-ask the client questions that have already been answered.
  3. Supervision visibility. Five unanswered voicemails in six weeks is a pattern. The log makes the pattern visible; an individual student may not flag it on their own.
  4. File retention. Law school clinics are obligated to maintain complete client files. Communication history is part of that.

Lightweight. Append-only. The student's job is to write a two-sentence summary after each contact; the skill formats and appends it.

Load context

  • ~/.claude/plugins/config/claude-for-legal-zh/legal-clinic/client-comms/[案件编号]/log.md(if present)—append target
  • ~/.claude/plugins/config/claude-for-legal-zh/legal-clinic/CLAUDE.md → not heavily read; this skill is case-scoped

Mode

Flag:--add | --read | --summary | --patterns(default: add)

--add(default)—record a new entry

Input:

  • Case number (required—which case)
  • Date + time (default: now)
  • Direction:in(client → clinic) | out(clinic → client)
  • Medium:电话 | 邮件 | 短信 | 信函 | 面谈 | 视频 | 留言-已留 | 留言-已收
  • Who (student): name
  • Who (client side): client name, or "third party: [description]" if from opposing counsel, family member, etc.
  • Duration/length (e.g., "10-minute call" "3 email messages" "45-minute meeting")
  • Summary: 2–4 sentences. What happened, what was substantive.
  • Action items:
    • What the student owes the client (with deadline)
    • What the client owes the student (with expected timing)
  • Follow-up deadline: if applicable
  • Notes: anything important that doesn't fit the categories above—language used, emotional tone, observed family dynamics

Before writing: Show the user the formatted entry and seek confirmation. Clinic records should be reviewed before writing, not after.

Appendto ~/.claude/plugins/config/claude-for-legal-zh/legal-clinic/client-comms/[案件编号]/log.md. If the log does not exist, create it with a header:

# 沟通日志 — [案件名称]

**案件编号：** [案件编号]
**当事人：** [姓名]
**建立日期：** [YYYY-MM-DD]

仅追加。最新在最前。

---

Then place the new entry at the top (newest first).

--read— show recent entries

Print the most recent N entries (default 5). Useful before taking over a case mid-semester or before a client call.

--summary— brief read

Generate a one-paragraph log summary — most recent contact, total entry count, common mediums, any pending action items on the student side, any unanswered communications. Input to /semester-handoff and /status。

--patterns— flag concerns across the whole log

Scan for:

  • Unanswered communications on the client side. The client called or emailed N times but no reply entry was logged.
  • Missed follow-ups. Action items with a follow-up deadline but no later entry resolving them.
  • Language/reasonable accommodation issues. The client's language is marked as non-Chinese; check whether outgoing communications used that language.
  • Escalation patterns. Changes in the client's tone (frustration/anxiety) across entries.
  • Gaps. Long periods with no contact on an active case.

This is a coaching tool. Clinic supervisors run --patterns across cases to see which students may need support.

Integration

  • /client-letter： After generating and sending a letter, offer to log it as an outgoing communication.
  • /status client： When generating a client-facing status summary, offer to log it (these summaries are usually sent to the client).
  • /client-intake： The first entry in each new case log is the intake contact.
  • /semester-handoff： The handoff memo reads each case's --summary to populate the communication history section.
  • /deadlines： If a communication established a deadline ("the client said they need to reply by Friday"), offer /deadlines --add。

What this skill does not do

  • Store substantive legal analysis. That lives in the intake, memo, and status files. The log is a communication record — contact facts, not legal strategy.
  • Automatically log from external systems. If the clinic uses a case management system, an integration could automatically pull call records and emails. That is a future development item; not v1.
  • Edit past entries. Append-only. If an entry is wrong, write a new entry citing and correcting it. The integrity of the log depends on not rewriting history.
  • Enforce logging discipline. If students do not log calls, the skill cannot know. Logging habits are a clinic culture issue; the skill just makes logging easy.
  • Handle confidential or attorney-only notes. If students need to record strategic thinking, it should go in the case's internal analysis file, not the communication log.