$ loading_
Track case deadlines — add, cross-case rollup report, update, complete, close. Warns at configurable thresholds (default 14/7/3/1 days); overdue items stay flagged until resolved. The operational record for a clinic workload. Use when a student or supervisor needs to add a deadline, ask what's due this week, get a deadline report, or update a case deadline.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "deadlines" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/legal-clinic/skills/deadlines/SKILL.md 2. Save it as ~/.claude/skills/deadlines/SKILL.md 3. Reload skills and tell me it's ready
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → jurisdiction, practice areas, warning-day cadence.--add: capture case, type, description, due date, source, owner. Write to ~/.claude/plugins/config/claude-for-legal/legal-clinic/deadlines.yaml. Check for duplicates first.--report (default): cross-case rollup — overdue, next 3d, next 7d, next 14d; by owner; by practice area; unassigned flags.--update [id]: modify fields; log note with date.--complete [id]: mark done; confirm with student that work is actually filed/submitted.--close [id]: close-without-completing; require rationale in notes.A clinic's biggest operational risk is a missed deadline. Students carry multiple cases, work part-time, turn over every semester. Deadlines that live only in individual students' heads get dropped at handoff, get forgotten during finals week, get missed when a student unexpectedly withdraws from the clinic. This skill is the central operational record.
The supervising attorney is on the hook if a deadline is missed. The skill is calibrated to that stakes level — warnings fire early, overdue items stay visible until explicitly resolved, handoffs (via /semester-handoff) pull the deadline list forward to the next student.
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → jurisdiction, practice areas, deadline warning days (default 14/7/3/1), supervising attorneys~/.claude/plugins/config/claude-for-legal/legal-clinic/deadlines.yaml — the ledgerJurisdiction assumption. Deadline calculations and warning thresholds assume the jurisdiction set in CLAUDE.md. Deadlines, tolling rules, computation-of-time rules, and local court practices vary materially by jurisdiction and by specific court. If a matter involves a different state, a specific court's local rules, or a federal vs. state forum question, confirm the deadline against the governing rule with your supervisor before relying on it.
Flag: --add | --report | --update | --complete | --close (default: report)
--add — log a new deadlineInputs:
The skill generates an id slug automatically: [case]-[short-desc]-[YYYY-MM].
Extraction from other skills: when /client-intake, /draft, or /status surface a deadline in their output, they should hand off to this skill with pre-populated fields. Student confirms and adds.
Pre-add check: if a deadline with the same case_id + type + due_date already exists, flag as likely duplicate and ask before adding.
Plausibility sanity band. After the student enters a due date, do NOT compute or verify — but apply a rough plausibility check against typical ranges for the filing type, and flag the student if the date falls far outside. This is scaffolding to catch gross errors in the student's own math, not an alternative to computing against the rule.
Bands are jurisdiction-keyed. Load the band file for this clinic's jurisdiction from references/plausibility-bands/{state}.md where {state} is the two-letter code from ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → clinic jurisdiction (and federal always loads alongside). The legal-clinic plugin ships references/plausibility-bands/CA.md (fully populated) and references/plausibility-bands/IL.md (placeholder structure) as starting points.
…
Draft a DMCA takedown notice, triage one you received, or draft a §512(g) counter-notice. Use when asserting copyright through a §512(c)(3) takedown with the fair-use and perjury gates, when an incoming takedown needs triage into comply / counter / engage / ignore options, or when drafting a §512(g)(3) counter-notice with the consent-to-federal-jurisdiction gate.
Search watched registries for community legal skills, showing matches with descriptions and offering to show the full SKILL.md before install. Use when the user says "browse", "search skills", "find a skill for", "what's out there for", or wants to add a new registry to the watchlist.
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.
Draft a brief section in house style, consistent with the case theory — every fact cited, every case checked, every argument tied to the theory. Use when the user says "draft the [section]", "write the statement of facts", "argument section on [issue]", or needs a first draft of a brief section.
Build a deposition outline for a witness — pull their documents from the eDiscovery platform, organize topics around the case theory, and surface impeachment material. Use when the user says "depo prep for [witness]", "build a depo outline", or "prepare for [name]'s deposition".
Manage matter workspaces — create, list, switch, close, or detach the active matter. Use in multi-client private practice to keep one client's context separate from another, or when a substantive skill needs to know which matter it's working in.