Legal Litigation Timeline Builder

Organizes litigation facts, events, deadlines, and evidence references into structured timelines, checklists, and templates for legal case workflow support.

Security Scan

This is a descriptive, instruction-only legal workflow skill that is internally consistent with its stated purpose and requests no credentials, binaries, or installs.

Purpose & Capability

Name, description, README, SKILL.md, and skill.json align: the package is document-only and focused on structuring litigation facts, deadlines, and checklists. No unrelated capabilities (cloud, git, databases) are requested or implied.

Instruction Scope

SKILL.md stays within scope: it asks the agent to solicit case facts, dates, jurisdiction, and produce timelines/checklists/templates. It explicitly forbids code execution, external API calls, or retrieving court records. It does not instruct reading system files, environment variables, or external endpoints.

Install Mechanism

No install spec and no code files are present; this is the lowest-risk packaging model and matches the stated descriptive-only intent.

Credentials

The package requires no environment variables, credentials, or config paths. There are no requests for unrelated secrets or broad access.

Persistence & Privilege

always is false and there are no special persistence or system-modifying behaviors. disable-model-invocation is false (normal default), meaning the agent could call the skill autonomously — this is expected for usable skills and not a red flag by itself.

Assessment

This skill appears to be a safe, document-only helper for organizing litigation timelines and deadlines. Before installing or using it: (1) remember it is informational only and not a substitute for an attorney — verify all legal conclusions and deadlines with counsel; (2) avoid pasting privileged or confidential evidence into any third-party tools or prompts unless you control data handling; (3) treat outputs as templates that require human review (LLMs can hallucinate dates, rules, or procedural requirements); (4) if you need jurisdiction-specific deadlines or filings, consult official court rules rather than relying solely on this skill. No technical credentials or installs are required, so the primary risks are legal/operational (misuse, overreliance), not technical exfiltration.

Overview

Organizes litigation facts, procedural events, deadlines, and evidence references into a coherent case timeline. This is a descriptive OpenClaw skill for legal-industry workflow support. It provides structured frameworks, checklists, templates, and issue-spotting prompts. It does not execute code, call external APIs, access legal databases, retrieve court records, automate filings, or perform legal services.

When to Use

• Preparing pleadings or motions
• Understanding fact chronology
• Coordinating litigation deadlines

Target Users

• Litigators
• Paralegals
• Case managers
• Trial teams

Inputs to Collect

• Matter or project context, including jurisdiction if known
• Relevant facts, documents, parties, dates, and constraints
• Desired output format, audience, and level of detail
• Known deadlines, risk concerns, or review priorities

Core Modules

1. Fact chronology table — provides structured prompts, checklists, and review fields for this area.
2. Procedural deadline tracker — provides structured prompts, checklists, and review fields for this area.
3. Source/evidence reference field — provides structured prompts, checklists, and review fields for this area.
4. Disputed vs undisputed facts — provides structured prompts, checklists, and review fields for this area.
5. Gap and follow-up list — provides structured prompts, checklists, and review fields for this area.

Workflow

1. Confirm the user's legal workflow goal and the relevant practice context.
2. Ask for missing facts, documents, dates, parties, jurisdiction, and audience where needed.
3. Apply the modules below as a structured thinking framework.
4. Produce checklists, templates, matrices, memos, or planning aids tailored to the user's context.
5. Flag uncertainty, verification needs, deadlines, ethics concerns, confidentiality issues, and attorney-review points.

Expected Outputs

• Chronology table
• Deadline tracker
• Evidence reference map
• Fact-gap list

Example Prompts

• "Build a litigation timeline template for a breach of contract case."
• "Help organize these facts into disputed and undisputed chronology."

Safety and Legal Limitations

• This skill provides informational workflow support only and is not legal advice.
• It does not create an attorney-client relationship and does not replace review by a qualified attorney.
• Laws, court rules, deadlines, ethics duties, privilege, confidentiality, and professional responsibility rules vary by jurisdiction and matter.
• Users must verify all legal authorities, filing requirements, deadlines, facts, citations, and strategic decisions with qualified counsel.
• The skill must not be used to fabricate evidence, coach false testimony, evade regulation, access data unlawfully, or bypass confidentiality obligations.
• Specific limitation for this skill: Users must verify court deadlines, rules, and evidence admissibility independently.

Acceptance Criteria

• Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.
• SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.
• Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.
• Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.
• skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.