Token导航 LogoToken导航

Agent Skill · 研究检索

case-analyzer(案例分析器)

case-analyzer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

case-analyzer 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 50,488。

总安装 612周安装 25GitHub Stars 11下载 196核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:case-analyzer(案例分析器)
来源仓库:https://github.com/enuno/claude-command-and-control
仓库路径:skills/case-analyzer
安装命令:
npx skills add https://github.com/enuno/claude-command-and-control --skill case-analyzer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/enuno/claude-command-and-control --skill case-analyzer

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

case-analyzer 用于法律案件分析与诉讼策略制定。识别可行诉由、评估证据强度与发现需求。适用于民权案件与法律援助场景的初步研判。不替代专业律师意见,仅提供结构化分析框架。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/case-analyzer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/enuno/claude-command-and-control --skill case-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

case-analyzer 怎么安装?

在终端执行 npx skills add https://github.com/enuno/claude-command-and-control --skill case-analyzer。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

case-analyzer 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

case-analyzer 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

case-analyzer 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

case-analyzer 用的人多吗?

公开数据是累计安装 612 次,近一周安装 25 次,下载 196 次,GitHub 11 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

case-analyzer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
case-analyzer

案例分析器 · 本页

61211只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Case Analyzer Skill

Purpose

Conduct comprehensive legal case analysis to identify viable claims, evaluate strengths and weaknesses, map evidence requirements, and develop litigation strategy for civil rights and legal advocacy cases.

When to Use This Skill

  • When user says "analyze this case" or "help me with a new case"
  • During initial case intake and assessment
  • When evaluating potential causes of action
  • When mapping legal theories to case facts
  • When assessing case viability for litigation
  • When identifying discovery needs
  • When strategizing affirmative defenses to counter

When NOT to Use This Skill

  • For legal research (use legal-research-assistant skill instead)
  • For drafting legal documents (use legal-document-drafter skill instead)
  • For case archival (use arweave-case-archiver skill instead)
  • For calculating damages (use damages-calculator skill if available)
  • For trial preparation (use trial-prep skill if available)

Prerequisites

  • Basic case facts available (who, what, when, where)
  • Jurisdiction identified (federal, state, which court)
  • General understanding of harm/violation alleged
  • Access to reference files in references/ directory
  • Python 3.9+ for automation scripts (statute of limitations calculator)

Workflow

Step 1: Case Intake and Fact Gathering

Purpose: Collect essential case information systematically

Process:

Ask the user these intake questions in order:

  1. What happened? (Chronological narrative of events)

- Request dates, times, locations - Identify all parties involved - Note sequence of events

  1. Who is involved?

- Plaintiff(s) - individual or organization - Defendant(s) - individual, organization, government entity - Witnesses - who observed what - Other parties - employers, supervisors, third parties

  1. When did events occur?

- Specific dates of incidents - Ongoing conduct vs. discrete events - CRITICAL: Calculate statute of limitations immediately

  1. Where did events take place?

- Geographic location (determines jurisdiction) - Federal property vs. state property - Public vs. private property

  1. What harm resulted?

- Physical injuries - Economic damages (lost wages, medical costs) - Emotional distress - Civil rights violations - Property damage

  1. What evidence exists?

- Documents (emails, contracts, policies) - Video/audio recordings - Photographs - Witness statements - Medical records - Police reports

Output: Structured case facts document

## Case Facts Summary

**Incident Date**: [YYYY-MM-DD]
**Location**: [City, State] - [Specific location]
**Jurisdiction**: [Court]

### Parties
- **Plaintiff**: [Name] - [Description]
- **Defendant**: [Name/Entity] - [Role]
- **Witnesses**: [List]

### Narrative
[Chronological description of events]

### Harm Alleged
- [Injury type 1]
- [Injury type 2]

### Evidence Available
- [Document 1]
- [Recording 1]
- [Witness testimony]

Statute of Limitations Check:

Use scripts/statute_of_limitations.py immediately:

python3 scripts/statute_of_limitations.py \
  --incident-date="2025-06-15" \
  --claim-type="1983" \
  --jurisdiction="california"

CRITICAL: If statute of limitations is approaching (<90 days), flag as URGENT


Step 2: Identify Applicable Legal Theories

Purpose: Match case facts to potential causes of action

Process:

Review case facts against legal frameworks in references/causes-of-action.md:

Federal Civil Rights Claims

42 U.S.C. § 1983 (Civil Rights Act):

  • Elements:

1. Defendant acted under color of state law 2. Defendant's conduct violated constitutional rights

When to Consider:

  • Police misconduct (excessive force, false arrest, malicious prosecution)
  • Jail/prison conditions (deliberate indifference to harm)
  • First Amendment violations (retaliation for protected speech)
  • Due process violations

Check for:

  • State actor involvement (police, sheriff, correctional officers, public officials)
  • Constitutional rights implicated (4th, 8th, 14th Amendments)

Americans with Disabilities Act (ADA):

  • Title I: Employment discrimination
  • Title II: State/local government services discrimination
  • Title III: Public accommodations discrimination

When to Consider:

  • Disability discrimination by government entity
  • Failure to provide reasonable accommodation
  • Denial of access to services
State Law Claims

Review references/state-tort-law.md for:

  • Assault and Battery: Intentional harmful or offensive contact
  • False Imprisonment: Unlawful restraint of liberty
  • Intentional Infliction of Emotional Distress: Extreme and outrageous conduct
  • Negligence: Breach of duty causing harm

Analysis Framework:

For each potential claim, create preliminary assessment:

### Legal Theory: [Claim Name]

**Legal Basis**: [Statute, constitutional provision]

**Elements**:
1. [Element 1]
2. [Element 2]
3. [Element 3]

**Fact Mapping**:
- Element 1: [How facts support this element]
- Element 2: [How facts support this element]
- Element 3: [How facts support this element]

**Preliminary Viability**: [Strong | Moderate | Weak]

**Challenges**:
- [Potential defense 1]
- [Evidentiary gap]

Output: List of 2-5 viable legal theories ranked by strength


Step 3: Elements-Based Analysis

Purpose: Rigorously analyze whether facts satisfy each required legal element

Process:

For each identified claim (from Step 2), perform detailed elements analysis using references/elements-checklists/.

Example: § 1983 Excessive Force Claim

Load reference: references/federal-civil-rights.md → § 1983 Elements

Required Elements:

  1. Defendant acted under color of state law
  2. Force used was objectively unreasonable (Graham v. Connor standard)
  3. Plaintiff suffered injury

Elements Analysis Table:

| Element | Facts Supporting | Evidence Available | Strength | Notes |
|---------|------------------|-------------------|----------|-------|
| Color of law | Officer on duty, badge #1234 | Body camera, uniform | ★★★★★ | Clear state actor |
| Objectively unreasonable | No resistance shown, compliant | Video, 3 witnesses | ★★★★☆ | Strong but need expert |
| Injury | Broken arm, bruising | Medical records, photos | ★★★★★ | Well documented |

**Overall Element Support**: 14/15 stars - STRONG CASE

Graham v. Connor Factors (for excessive force):

  1. Severity of crime at issue
  2. Whether suspect poses immediate threat
  3. Whether suspect actively resisting or fleeing

Analysis:

1. **Severity of Crime**: Misdemeanor jaywalking - LOW
2. **Immediate Threat**: No weapon, hands visible, compliant - NONE
3. **Resistance/Flight**: Video shows no resistance - NONE

**Conclusion**: Force objectively unreasonable under Graham

For Each Claim, Assess:

  • ✅ Strong (4-5 stars): All elements clearly supported by facts and evidence
  • ⚠️ Moderate (2-3 stars): Most elements supported but gaps exist
  • ❌ Weak (0-1 stars): Critical elements missing or unsupported

Output: Elements analysis for top 2-3 claims


Step 4: Discovery Planning

Purpose: Identify what additional evidence is needed to prove elements

Process:

Based on elements analysis, create comprehensive discovery plan:

Documents to Request

Initial Disclosures (FRCP 26):

  • Witness list with contact information
  • Document list (descriptions)
  • Damages computation
  • Insurance agreements

Interrogatories (Questions to opposing party):

1. Identify all officers present at scene on [date]
2. Describe all use-of-force policies in effect on [date]
3. Detail training received by Officer [Name] on [topic]
4. Identify all internal affairs investigations of Officer [Name]
5. [Additional interrogatories - maximum 25 under FRCP]

Document Requests:

### Request 1: Incident Reports
All police reports, incident reports, and supplemental reports related to incident on [date]

### Request 2: Video Evidence
All body camera, dashboard camera, and surveillance footage from [time range]

### Request 3: Personnel Files
Complete personnel file for Officer [Name] including:
- Training records (use of force, de-escalation)
- Disciplinary history
- Prior complaints
- Performance evaluations

### Request 4: Policies and Procedures
All use-of-force policies in effect on [date]

### Request 5: Internal Investigations
All internal affairs investigations related to Officer [Name]

Depositions (Oral testimony under oath):

Priority Order:
1. **Defendant Officer(s)** - 7 hour deposition
   - Training and experience
   - Incident reconstruction
   - Force decision-making process

2. **Supervisor(s)** - 4 hour deposition
   - Oversight and training
   - Policy enforcement

3. **Eyewitnesses** - 2-3 hours each
   - What they observed
   - Credibility assessment

4. **Plaintiff** - 6 hours (prepare thoroughly)
   - Incident narrative
   - Injuries and damages
   - Medical treatment

Expert Witnesses Needed:

1. **Use of Force Expert**
   - Credentials: Former police chief, trainer
   - Purpose: Opine on reasonableness of force
   - Cost: $10,000 - $25,000

2. **Medical Expert**
   - Credentials: Orthopedic surgeon
   - Purpose: Causation of injuries, permanence
   - Cost: $5,000 - $15,000

3. **Economic Expert** (if wage loss)
   - Credentials: Economist, CPA
   - Purpose: Calculate economic damages
   - Cost: $5,000 - $10,000

Output: Comprehensive discovery plan organized by category


Step 5: Assess Affirmative Defenses and Weaknesses

Purpose: Anticipate opposing arguments and develop counter-strategies

Process:

Review references/defenses.md for common defenses:

Qualified Immunity (§ 1983 cases)

Defense Argument: "The constitutional right was not clearly established at the time of the incident"

Two-Prong Test:

  1. Did defendant violate constitutional right?
  2. Was the right clearly established?

Our Response Strategy:

### Defeating Qualified Immunity

**Prong 1: Constitutional Violation**
- Video evidence shows clear excessive force
- No resistance, no threat = constitutional violation

**Prong 2: Clearly Established Law**
- **Case 1**: [Circuit Case Name] (20XX)
  - Holding: Force against compliant suspect unreasonable
  - Similarity: [Explain how facts parallel our case]

- **Case 2**: [Supreme Court Case]
  - Holding: Graham factors analysis
  - Application: All factors support plaintiff

**Conclusion**: Right was clearly established. QI should be denied.

Risk Assessment: [Low | Medium | High] Mitigation: Conduct thorough legal research on circuit precedents

Governmental Immunity (State Tort Claims)

Defense Argument: "Municipality has governmental immunity for discretionary acts"

Analysis:

**Immunity Type**: [Sovereign | Qualified | Discretionary]

**Exceptions Available**:
- Ministerial act exception
- Dangerous condition of public property
- [Jurisdiction-specific exceptions]

**Our Strategy**:
- Focus on federal § 1983 claim (no immunity)
- State claims as alternative/backup
- Identify applicable immunity exceptions
Contributory Negligence

Defense Argument: "Plaintiff's own actions contributed to injury"

Analysis:

**Defendant's Likely Arguments**:
- Plaintiff was jaywalking (crime)
- Plaintiff didn't immediately comply

**Our Counters**:
- Jaywalking is minor infraction, doesn't justify force
- Video shows compliance
- Contributory negligence not applicable to § 1983 excessive force

**Risk**: Low - Strong video evidence of compliance
Case Weaknesses to Address

Identify Honestly:

### Weakness 1: [Description]
**Issue**: Only plaintiff's testimony for initial contact
**Impact**: Credibility battle
**Mitigation**:
- Obtain body camera footage
- Depose witnesses
- Medical records corroborate injuries

### Weakness 2: [Description]
**Issue**: Minor physical injuries (no hospitalization)
**Impact**: Lower damages
**Mitigation**:
- Emphasize constitutional violation (nominal + punitive damages available)
- Emotional distress damages
- Focus on deterrence value of verdict

### Weakness 3: [Description]
**Issue**: [Specific weakness]
**Impact**: [How it affects case]
**Mitigation**: [Strategy to address]

Output: Comprehensive defense analysis with counter-strategies


Step 6: Generate Case Analysis Report

Purpose: Create comprehensive documented analysis for case file

Process:

Synthesize all prior steps into structured CASE_ANALYSIS.md:

# Case Analysis: [Case Name]

**Generated**: [ISO Timestamp]
**Analyst**: case-analyzer skill v1.0.0
**Jurisdiction**: [Court]

---

## Executive Summary

[2-3 paragraph summary of case viability and recommended strategy]

**Recommended Primary Strategy**: [e.g., Federal § 1983 claim in U.S. District Court]

**Estimated Likelihood of Success**: [Percentage or qualitative assessment]

**Estimated Settlement Range**: $[Low] - $[High]

**Statute of Limitations**: [Date] ([X] days remaining)

**Urgency**: [CRITICAL <30 days | URGENT <90 days | MODERATE <180 days | ROUTINE]

---

## Case Facts

### Incident Summary
[Chronological narrative - 3-5 paragraphs]

### Parties
- **Plaintiff**: [Name], [Age], [Occupation]
- **Defendant**: [Name/Entity], [Role]
- **Witnesses**: [List with brief descriptions]

### Evidence Inventory
| Evidence Type | Description | Status | Location |
|---------------|-------------|--------|----------|
| Body camera | Officer #1234 footage | Requested | City PD |
| Medical records | ER visit 12/15/25 | ✓ Obtained | Case file |
| Witness statements | 3 civilian witnesses | Pending | To be deposed |

---

## Legal Analysis

### Identified Claims

#### Primary Claim: 42 U.S.C. § 1983 - Excessive Force

**Legal Basis**: Fourth Amendment via § 1983

**Elements Analysis**:

| Element | Support | Strength | Evidence |
|---------|---------|----------|----------|
| Color of state law | Officer on duty | ★★★★★ | Badge, uniform |
| Constitutional violation | Force unreasonable | ★★★★☆ | Video, witnesses |
| Injury | Physical harm | ★★★★★ | Medical records |

**Overall Viability**: ★★★★☆ (STRONG)

**Estimated Damages**: $75,000 - $200,000
- Compensatory: $25,000 - $75,000
- Punitive: $50,000 - $125,000 (if malice/recklessness shown)
- Attorney's fees: Recoverable under 42 U.S.C. § 1988

#### Alternative Claim: State Assault and Battery

**Legal Basis**: [State] Common Law Tort

**Elements Analysis**:
[Similar format as above]

**Overall Viability**: ★★★☆☆ (MODERATE)

**Challenges**:
- Governmental immunity may apply
- Lower damages than § 1983
- Purpose: Backup if federal claim fails

---

## Discovery Plan

### Phase 1: Initial Disclosures (Due: [Date])
- [ ] Witness list
- [ ] Document list
- [ ] Damages computation
- [ ] Insurance disclosure

### Phase 2: Written Discovery (Serve by: [Date])

**Interrogatories** (25 maximum):
1. [Question 1]
2. [Question 2]
...

**Document Requests** (50 recommended):
1. All police reports re: incident
2. All body/dashboard camera footage
3. Personnel files for Officer [Name]
...

### Phase 3: Depositions (Complete by: [Date])

| Deponent | Role | Priority | Duration | Topics |
|----------|------|----------|----------|--------|
| Officer Smith | Defendant | HIGH | 7 hours | Force decision, training |
| Witness Jones | Eyewitness | MEDIUM | 2 hours | Observations |
| Plaintiff | Party | HIGH | 6 hours | Incident, injuries, damages |

### Phase 4: Expert Witnesses

| Expert Type | Name | Purpose | Cost Est | Deadline |
|-------------|------|---------|----------|----------|
| Use of force | [TBD] | Opine on reasonableness | $15K | Discovery close |
| Medical | [TBD] | Injury causation | $10K | Discovery close |

---

## Affirmative Defenses & Counter-Strategies

### Defense 1: Qualified Immunity

**Defendant's Argument**:
"Right not clearly established; officer entitled to immunity"

**Our Counter-Strategy**:
1. Identify circuit precedents with similar facts
2. Emphasize obviousness of constitutional violation
3. Cite: [Case 1], [Case 2], [Case 3]

**Risk Level**: MEDIUM
**Likelihood of Success in Defeating**: 70%

### Defense 2: [Additional Defense]
[Similar format]

---

## Case Strengths and Weaknesses

### Strengths ✓
1. **Video Evidence**: Body camera shows clear lack of resistance
2. **Injury Documentation**: Medical records well-documented
3. **Precedent**: Strong circuit law on excessive force
4. **Credible Plaintiff**: No criminal history, steady employment

### Weaknesses ⚠️
1. **Minor Crime**: Jaywalking is low-level infraction
   - **Mitigation**: Emphasize this strengthens our case (force disproportionate)

2. **Limited Physical Injury**: No hospitalization
   - **Mitigation**: Focus on constitutional violation + emotional distress

3. **Witness Credibility**: Only 1 witness to initial contact
   - **Mitigation**: Obtain body camera, depose all witnesses early

---

## Recommended Strategy

### Forum Selection
**Primary**: U.S. District Court, [District]
- **Rationale**: Federal jurisdiction via § 1983, federal judges experienced in civil rights

**Alternative**: State Superior Court
- **Use if**: Federal court dismisses on qualified immunity (unlikely)

### Claim Prioritization
1. **Primary**: § 1983 excessive force (strongest claim)
2. **Alternative**: State assault/battery (backup)
3. **Omit**: [Weaker claims with high risk]

### Settlement Posture
**Pre-Suit Demand**: $150,000
**Post-Suit Settlement Range**: $100,000 - $175,000
**Trial Verdict Estimate**: $150,000 - $250,000

**Timing**:
- Demand letter: Immediate (preserve SOL)
- Mediation: Post-discovery (6-9 months)
- Trial: 12-18 months if no settlement

---

## Next Steps

### Immediate (Week 1)
- [ ] Calculate exact SOL deadline (scripts/statute_of_limitations.py)
- [ ] Draft and send demand letter to defendant
- [ ] Preserve evidence (send preservation letter)

### Short-term (Weeks 2-4)
- [ ] Conduct legal research on qualified immunity
- [ ] Draft federal complaint (use legal-document-drafter skill)
- [ ] Identify and retain expert witnesses

### Medium-term (Months 1-3)
- [ ] File complaint
- [ ] Serve defendants
- [ ] Initiate discovery process

### Long-term (Months 4-12)
- [ ] Complete discovery
- [ ] Prepare for trial or mediation
- [ ] Archive case documents to Arweave (arweave-case-archiver skill)

---

## Statute of Limitations Tracker

**Incident Date**: 2025-06-15
**Claim Type**: § 1983 (uses state personal injury SOL)
**Jurisdiction**: California (2-year SOL)
**Filing Deadline**: 2027-06-15
**Days Remaining**: 547 days
**Urgency**: ROUTINE (adequate time)

**Calculated by**: scripts/statute_of_limitations.py
**Last Checked**: [ISO Timestamp]

---

## Archive Information

**Case ID**: [UUID]
**Arweave TX IDs**: [To be populated after archival]
**Last Updated**: [ISO Timestamp]
**Next Review**: [Date + 30 days]

---

**END OF CASE ANALYSIS**

Quality Check:

  • All sections complete
  • Legal citations accurate
  • Evidence mapped to elements
  • Discovery plan comprehensive
  • Defense analysis thorough
  • Next steps actionable
  • SOL calculated and verified

Error Handling

Scenario: Insufficient Facts Provided

Symptom: User provides vague description like "police mistreated me"

Response:

I notice we need more detailed facts to conduct thorough analysis. Let me ask some targeted questions:

1. What specifically did the officer(s) do? (describe physical actions)
2. When did this occur? (exact date and time if possible)
3. Where did this take place? (city, state, specific location)
4. What injuries did you sustain? (physical, emotional, economic)
5. Do you have any documentation? (reports, medical records, video)

Once we have these details, I can identify viable legal claims and assess case strength.

Escalation: If user cannot provide basic facts, suggest:

  • Obtain police report
  • Gather medical records
  • Interview witnesses
  • Return when facts are better documented

Scenario: Novel Legal Issue

Symptom: Facts don't clearly fit known causes of action

Response:

## Novel Legal Issue Identified

**Issue**: [Description of novel issue]

**Why Novel**: [Explanation - e.g., "No binding precedent in this circuit"]

**Recommended Approach**:
1. Flag for legal research (use legal-research-assistant skill)
2. Research analogous cases in other circuits
3. Consult with senior attorney specializing in [area]
4. Consider test case strategy if issue important

**Risk**: [HIGH - outcome uncertain]
**Recommendation**: Proceed with caution; may require expert consultation

Scenario: Statute of Limitations Expired

Symptom: SOL calculator returns negative days remaining

Response:

⚠️ **CRITICAL ISSUE: STATUTE OF LIMITATIONS EXPIRED**

**Incident Date**: [Date]
**SOL Deadline**: [Date - in past]
**Days Overdue**: [X] days

**Implications**:
- Case likely barred from filing
- Exceptions are rare and narrow

**Possible Exceptions to Explore**:
1. **Tolling**: Was plaintiff minor, incapacitated, or fraudulently concealed?
2. **Discovery Rule**: Did plaintiff reasonably discover injury later?
3. **Continuing Violation**: Is conduct ongoing?
4. **Equitable Tolling**: Extraordinary circumstances?

**URGENT ACTION REQUIRED**:
Consult experienced attorney immediately to assess exception applicability.
Do NOT proceed with case analysis until SOL issue resolved.

Scenario: Jurisdictional Complexity

Symptom: Multiple potential forums (federal, multiple states, tribal, etc.)

Response:

## Jurisdictional Analysis Required

**Complexity Detected**: [e.g., "Incident spans multiple states"]

**Potential Forums**:
1. **U.S. District Court - [District]**
   - Pros: [Federal question jurisdiction, experienced judges]
   - Cons: [Qualified immunity more common]

2. **[State] Superior Court**
   - Pros: [Jury pool favorable, state law claims easier]
   - Cons: [Slower docket, less civil rights experience]

3. **[Other Forum]**
   - Pros: [...]
   - Cons: [...]

**Recommendation**: Analyze forum selection as separate task
**Tools**: Use jurisdiction_analyzer.py script (if available)
**Consult**: Attorney licensed in all relevant jurisdictions

Quality Standards

Output Quality Checklist

Before marking case analysis complete, verify:

  • Completeness: All 6 workflow steps executed
  • Accuracy: Legal citations correct (case names, statutes)
  • Element Mapping: Every element analyzed with evidence
  • Risk Assessment: Strengths and weaknesses candidly assessed
  • Actionability: Next steps are specific and time-bound
  • SOL Verified: Deadline calculated and flagged if urgent
  • Professional Tone: Objective, analytical, non-judgmental
  • Organized: Clear structure with headers and tables
  • Archived: Ready for Arweave permanent storage

Red Flags (Do Not Proceed)

  • ❌ Statute of limitations < 30 days without immediate action plan
  • ❌ Critical facts missing (who, what, when, where)
  • ❌ Jurisdictional issues unresolved
  • ❌ Legal issues beyond analyzer's expertise (complex constitutional law, novel theories)
  • ❌ Conflicts of interest detected

If Red Flag Detected: Escalate to supervising attorney


Resources

Reference Files

Load these as needed during analysis:

  • references/causes-of-action.md - Comprehensive list of federal/state claims
  • references/federal-civil-rights.md - § 1983, ADA, Fair Housing detailed
  • references/state-tort-law.md - State-specific tort claims by jurisdiction
  • references/elements-checklists/ - Element-by-element analysis templates
  • references/defenses.md - Common affirmative defenses and counters
  • references/qualified-immunity.md - QI doctrine and defeat strategies

Automation Scripts

  • scripts/statute_of_limitations.py - Calculate filing deadlines python3 scripts/statute_of_limitations.py \ --incident-date="2025-06-15" \ --claim-type="1983" \ --jurisdiction="california"
  • scripts/jurisdiction_analyzer.py - Determine proper venue (optional)
  • scripts/damages_estimator.py - Estimate settlement range (optional)

Templates

  • assets/intake-questionnaire.md - Client intake form
  • assets/case-analysis-template.md - Blank analysis template

Integration with MISJustice Platform

Related Skills

  • legal-research-assistant: Use after Step 2 to research identified claims
  • legal-document-drafter: Use after Step 6 to draft complaint
  • arweave-case-archiver: Use after Step 6 to permanently archive analysis

Related Commands

  • /case-plan: Orchestrates this skill + research + drafting
  • /legal-session-start: Loads legal context before case analysis

MCP Dependencies

None currently. Future: Legal database MCPs (Westlaw, LexisNexis)

Orchestration

Can be chained with other skills:

case-analyzer → legal-research-assistant → legal-document-drafter → arweave-case-archiver

Examples

Example 1: § 1983 Excessive Force Case

Input (User):

I was arrested for jaywalking on December 15, 2025. The officer tackled me to the ground even though I wasn't resisting. I suffered a broken arm and needed surgery. I have body camera footage showing I had my hands up. This happened in Oakland, California.

Output (case-analyzer):

# Case Analysis: [Plaintiff] v. Oakland Police Department

## Executive Summary

Strong § 1983 excessive force claim against arresting officer. Video evidence shows plaintiff compliant with hands up when tackled, resulting in significant physical injury (broken arm requiring surgery). Incident occurred 17 days ago, SOL deadline is December 15, 2027 (729 days remaining).

**Recommended Strategy**: File federal § 1983 claim in U.S. District Court, Northern District of California. Estimated settlement value: $100,000 - $250,000.

**Urgency**: MODERATE (adequate time but act promptly to preserve evidence)

## Identified Claims

### Primary: 42 U.S.C. § 1983 - Fourth Amendment Excessive Force

**Elements Analysis**:
| Element | Support | Strength | Evidence |
|---------|---------|----------|----------|
| Color of law | Oakland PD officer on duty | ★★★★★ | Body camera, badge |
| Objectively unreasonable force | Tackling compliant suspect for jaywalking | ★★★★★ | Body camera, medical records |
| Injury | Broken arm requiring surgery | ★★★★★ | Medical records, X-rays, surgical notes |

**Graham v. Connor Analysis**:
1. Severity of crime: Jaywalking (infraction) - MINIMAL
2. Immediate threat: Hands up, compliant - NONE
3. Active resistance/flight: No resistance shown on video - NONE

**Conclusion**: All Graham factors favor plaintiff. Force objectively unreasonable.

**Viability**: ★★★★★ (VERY STRONG)

[... continues with full analysis ...]

Example 2: ADA Disability Discrimination

Input (User):

I use a wheelchair. Last month, the county courthouse had no elevator working and staff refused to help me access the courtroom on the second floor. I missed my hearing because of this. This was in Tampa, Florida on January 5, 2026.

Output (case-analyzer):

# Case Analysis: [Plaintiff] v. [County] Courthouse

## Executive Summary

Strong ADA Title II claim against county for failure to provide access to government services. Plaintiff, wheelchair user, denied access to second-floor courtroom due to broken elevator and staff refusal to assist, causing missed court hearing.

**Recommended Strategy**: Federal ADA Title II claim + potential § 1983 claim (deprivation of court access). Settlement range: $25,000 - $75,000 + injunctive relief.

## Identified Claims

### Primary: ADA Title II - Denial of Access to Government Services

**Elements Analysis**:
| Element | Support | Strength | Evidence |
|---------|---------|----------|----------|
| Plaintiff has disability | Wheelchair user (physical impairment) | ★★★★★ | Medical documentation needed |
| Otherwise qualified | Had court hearing scheduled | ★★★★★ | Court docket |
| Excluded from services | Denied courtroom access | ★★★★★ | Witness testimony, court records |
| Because of disability | Inaccessible second floor | ★★★★★ | Physical inspection, photos |

**Viability**: ★★★★★ (VERY STRONG)

**Estimated Damages**:
- Compensatory: $25,000 - $50,000 (emotional distress, legal consequences of missed hearing)
- Injunctive relief: Elevator repair, accessibility plan
- Attorney's fees: Recoverable under ADA

### Alternative: 42 U.S.C. § 1983 - Access to Courts

[... continues with full analysis ...]

Example 3: Weak Case (Honest Assessment)

Input (User):

I got a speeding ticket last week and the cop was really rude to me. Can I sue for civil rights violations?

Output (case-analyzer):

# Case Analysis: Speeding Stop

## Executive Summary

**Case Viability**: ★☆☆☆☆ (VERY WEAK - NOT RECOMMENDED)

After analyzing the facts, this case does not present a viable civil rights claim. While the officer's rudeness was unprofessional, it does not rise to the level of a constitutional violation.

## Analysis

### Potential Claim: § 1983 Violation

**Why This Fails**:
1. **No Constitutional Right Violated**: Rudeness alone does not violate the Constitution
2. **No Physical Force**: Traffic stop without excessive force is lawful
3. **No Unlawful Detention**: Speeding provides probable cause for stop
4. **No Actionable Harm**: Emotional distress from rudeness insufficient

**Supreme Court Precedent**:
"The Fourth Amendment does not forbid officers from being rude" - controlling case law

### Alternative Options

1. **Traffic Court**: Challenge the ticket on its merits
2. **Police Complaint**: File internal affairs complaint about officer conduct
3. **Not Recommended**: Federal civil rights lawsuit (likely dismissed, waste of resources)

## Recommendation

**Do NOT pursue civil rights litigation**. This case does not meet the threshold for federal constitutional claims.

**Alternative Actions**:
- Contest ticket in traffic court if factual disputes
- File police complaint if officer conduct warrants discipline
- Accept outcome and move forward

**Consultation**: If you believe there are additional facts not disclosed (physical force, discriminatory statements, unlawful search), please provide those details for re-analysis.

Version History

  • 1.0.0 (2026-01-01): Initial release

- Comprehensive 6-step workflow - Federal civil rights focus (§ 1983, ADA) - State tort law integration - Discovery planning module - Defense analysis framework - SOL automation integration


Troubleshooting

Issue: Skill produces overly optimistic case assessment

Solution:

  • Re-review Step 5 (affirmative defenses)
  • Ensure weaknesses are honestly identified
  • Apply "red team" thinking - argue against your own case
  • Consult qualified-immunity.md for realistic QI assessment

Issue: Legal citations are outdated or incorrect

Solution:

  • Verify citations in references/ files are current
  • Update reference files annually
  • Flag for legal research if citation uncertain
  • Use legal-research-assistant skill for verification

Issue: Jurisdiction-specific rules not addressed

Solution:

  • Ensure references/state-tort-law.md includes your jurisdiction
  • Add jurisdiction-specific reference files as needed
  • Consult local counsel for unique state rules
  • Note jurisdiction limitations in analysis

END OF SKILL DOCUMENTATION

平台分布

Codex

37.12%
按下载量换算73

Claude

31.63%
按下载量换算62

Cursor

17.79%
按下载量换算35

Gemini CLI

9.06%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills