Skip to content
Back to skills

Legal Litigation Timeline Builder

ASecurity

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.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
businessgoawsapidatabase

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned October 6, 2026

npx -y skills add aAAaqwq/openclaw-team --skill legal-litigation-timeline-builder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Legal Litigation Timeline Builder?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Legal Litigation Timeline Builder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aaaaqwq-legal-litigation-timeline-builder/badge)](https://www.skillsdirectory.com/skills/aaaaqwq-legal-litigation-timeline-builder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
slug: legal-litigation-timeline-builder
version: "1.0.0"
type: descriptive
language: en
---

# Legal Litigation Timeline Builder

## 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.

Files in this skill

  • .clawhub/origin.json165 B
  • ACCEPTANCE.md796 B
  • README.md1.2 KB
  • SKILL.md3.6 KB
  • _meta.json152 B
  • skill.json800 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…