How do I install the Litigation Workflows skill?

Run npx skillmds@latest add infometa/litigation-workflows in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Litigation Workflows safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Litigation Workflows?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Litigation Workflows free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Litigation Workflows?

infometa (@infometa) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Litigation Workflows by infometa — Agent Skill

Name: Litigation Workflows
Rating: 4.5 (4 reviews)
Author: infometa

File contents

Litigation Legal Workflows

This skill is a merged entry point. The porting method is copy → merge → modify → optimize:

Source README / practice profile / SKILL.md / agent markdown files were copied into references/source-workflows/.
Hook and slash-command behavior was removed because this marketplace uses experts, agents, and skills.
The exposed skill below consolidates the copied source workflows into a smaller routing surface.
Local adaptation should be done cautiously through jurisdiction notes, not by replacing the source workflow wholesale.

Copied source materials

See references/source-workflows/ in this plugin for the debranded source workflow text used during consolidation.

Consolidated behavior

Capabilities

matter intake and updates
portfolio status and outside counsel status drafts
chronology building
claim chart drafting and review
evidence and exhibit outline preparation
confidentiality and sensitive-materials review
litigation correspondence triage
deadline and obligation tracking
demand letter intake, drafting, and response triage
brief section drafting

Operating rule

Use this as a structured checklist. Do not treat it as legal advice or a substitute for qualified legal review.

Working across jurisdictions

Use the source workflow as the operating skeleton, but read the matter through the jurisdiction the user is actually working in. If the facts point to China or another non-US setting, first anchor the analysis in the applicable law, regulator, industry, contract language, and document purpose. Keep the familiar review flow, while translating only the parts that are jurisdiction-shaped: legal labels, deadlines, regulator references, employment classifications, data-protection vocabulary, and court or filing procedures.

When the local rule is not in the provided materials or a current source you can inspect, say so naturally in the analysis and treat it as something for counsel to verify. The goal is a localized draft that still feels like the original workflow, not a new legal product rebuilt from scratch.

Legal-output boundary

Outputs are lawyer-review drafts, not legal advice. Mark assumptions, sources, and attorney-review points.

---name: litigation-workflowsdescription: Consolidated workflow layer copied and merged from litigation-legal. Use this skill as the exposed entry point while preserving detailed source workflows under references/source-workflows.--- # Litigation Legal Workflows This skill is a merged entry point. The porting method is copy → merge → modify → optimize: 1. Source README / practice profile / SKILL.md / agent markdown files were copied into `references/source-workflows/`. 2. Hook and slash-command behavior was removed because this marketplace uses experts, agents, and skills. 3. The exposed skill below consolidates the copied source workflows into a smaller routing surface. 4. Local adaptation should be done cautiously through jurisdiction notes, not by replacing the source workflow wholesale. ## Copied source materials See `references/source-workflows/` in this plugin for the debranded source workflow text used during consolidation. ## Consolidated behavior ## Capabilities - matter intake and updates - portfolio status and outside counsel status drafts - chronology building - claim chart drafting and review - evidence and exhibit outline preparation - confidentiality and sensitive-materials review - litigation correspondence triage - deadline and obligation tracking - demand letter intake, drafting, and response triage - brief section drafting ## Operating rule Use this as a structured checklist. Do not treat it as legal advice or a substitute for qualified legal review. ## Working across jurisdictions Use the source workflow as the operating skeleton, but read the matter through the jurisdiction the user is actually working in. If the facts point to China or another non-US setting, first anchor the analysis in the applicable law, regulator, industry, contract language, and document purpose. Keep the familiar review flow, while translating only the parts that are jurisdiction-shaped: legal labels, deadlines, regulator references, employment classifications, data-protection vocabulary, and court or filing procedures. When the local rule is not in the provided materials or a current source you can inspect, say so naturally in the analysis and treat it as something for counsel to verify. The goal is a localized draft that still feels like the original workflow, not a new legal product rebuilt from scratch. ## Legal-output boundary Outputs are lawyer-review drafts, not legal advice. Mark assumptions, sources, and attorney-review points.

Frequently asked questions

Litigation Workflows