Legal Evidence Organization Matrix

Provides structured frameworks and checklists to organize legal evidence, linking documents, witnesses, issues, authenticity, relevance, and proof gaps for l...

Security Scan

This is a descriptive, instruction-only skill that generates legal evidence organization frameworks and does not request credentials, install code, or perform external actions — its declared behavior matches its files and instructions.

Purpose & Capability

The skill's name and description align with its contents: SKILL.md, README.md, and skill.json all describe a document-only workflow helper for organizing evidence. There are no declared binaries, env vars, or external APIs required that would be unrelated to the stated purpose.

Instruction Scope

SKILL.md instructs the agent to ask users for matter context and facts and to produce checklists, matrices, and templates — this stays within the stated descriptive purpose. Note: collecting user-supplied facts or documents may involve sensitive or privileged information; the skill itself has no code to access files or networks, but users should avoid pasting privileged/confidential materials into the chat unless appropriate.

Install Mechanism

No install spec or code files are present; the package is instruction-only per ACCEPTANCE.md and the repo contents. This minimizes disk-write or remote-code risks.

Credentials

No environment variables, credentials, or config paths are requested. The lack of required secrets is proportionate to a descriptive/template skill.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and has no installation steps that would persist privileged configuration. Autonomous model invocation is allowed by default but not combined with other risky attributes here.

Assessment

This skill appears internally consistent and lower-risk because it’s document-only and contains no code or external endpoints. Before using it, do not paste privileged, confidential, or personally identifying evidence into the chat unless you have the right to share it; always verify any legal conclusions or jurisdiction-specific requirements with qualified counsel; and do not use the skill to plan or facilitate illegal activity or to fabricate evidence. If you need automation that accesses documents or databases, prefer a skill that explicitly documents safe access methods and necessary credentials rather than pasting sensitive data into an instruction-only skill.

Overview

Creates evidence organization frameworks linking documents, witnesses, issues, authenticity, relevance, and proof gaps. 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 discovery materials
• Mapping evidence to claims or defenses
• Auditing proof gaps before motions or trial

Target Users

• Litigation teams
• Investigators working with counsel
• Paralegals
• Compliance legal 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. Evidence inventory fields — provides structured prompts, checklists, and review fields for this area.
2. Issue-to-evidence map — provides structured prompts, checklists, and review fields for this area.
3. Witness/document cross-reference — provides structured prompts, checklists, and review fields for this area.
4. Authenticity and chain-of-custody notes — provides structured prompts, checklists, and review fields for this area.
5. Proof-gap tracker — 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

• Evidence matrix
• Issue proof map
• Witness-document cross-reference
• Gap list

Example Prompts

• "Create an evidence matrix for a trade secret dispute."
• "Map documents and witnesses to legal issues in a civil case."

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: Does not collect evidence or advise on illegal access; evidence handling must follow law, court rules, and counsel instructions.

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.