haidong

# Short Video Script Builder

Builds structured short-video scripts using proven frameworks (hook-body-CTA, AIDA, PAS, story arc) with timing and visual notes.

## Target Users

- Content creators
- Video marketers
- Educators
- Storytellers
- Scriptwriters

## When to Use

- Writing a script from scratch for a new video
- Structuring raw ideas into a coherent narrative
- Adapting a long-form piece into a short video

## Core Workflow

1. Video objective and target emotion selection
2. Structure framework selection (AIDA, PAS, Hook-Story-CTA, Problem-Solution, Listicle)
3. Hook development (first 3 seconds)
4. Body / story / value delivery
5. CTA (call to action) design
6. Timing allocation per segment

## Inputs

- Topic
- Target length (15s/30s/60s/90s+)
- Platform
- Target audience
- Video objective

## Expected Outputs

- Structured script with timestamps
- Hook drafts (multiple options)
- B-roll and visual cue notes
- CTA variations

## Example Prompts

- "Write a 60-second script for a Douyin product demo using the Problem-Solution framework."
- "Build a 30-second storytelling script about my morning routine for a lifestyle channel."
- "Adapt this blog post into 3 short video scripts for different platforms."

## Trigger Keywords

video script, script template, script structure, write video, short video script, AIDA script, hook script

## Safety & Limitations

Script structures are templates and guidance. All final content is the creator's responsibility. No automated video generation or text-to-speech.

---

*Generated for project short-video-skills-2026-04-27*

FILE:skill.json
{
  "slug": "sv-script-builder",
  "name": "Short Video Script Builder",
  "description": "Builds structured short-video scripts using proven frameworks (hook-body-CTA, AIDA, PAS, story arc) with timing and visual notes.",
  "type": "descriptive",
  "requires_api": false,
  "readiness": "stable",
  "tags": [
    "video",
    "script",
    "writing",
    "storytelling",
    "structure",
    "descriptive"
  ],
  "trigger_keywords": [
    "video script",
    "script template",
    "script structure",
    "write video",
    "short video script",
    "AIDA script",
    "hook script"
  ],
  "max_files": 4,
  "language": "en",
  "safety": "document-only informational guidance"
}

FILE:README.md
# Short Video Script Builder

Builds structured short-video scripts using proven frameworks (hook-body-CTA, AIDA, PAS, story arc) with timing and visual notes.

## Target Users

- Content creators
- Video marketers
- Educators
- Storytellers
- Scriptwriters

## When to Use

- Writing a script from scratch for a new video
- Structuring raw ideas into a coherent narrative
- Adapting a long-form piece into a short video

## Trigger Keywords

video script, script template, script structure, write video, short video script, AIDA script, hook script

## Full Documentation

See [SKILL.md](./SKILL.md) for complete workflow, inputs, outputs, and examples.

---

*Generated for project short-video-skills-2026-04-27*

FILE:ACCEPTANCE.md
# Acceptance Checklist — Short Video Script Builder

## Criteria

- [x] Document-only: no handler.py, scripts, APIs, or executable code
- [x] No network calls or credential handling
- [x] English-first documentation
- [x] File count ≤ 10 (target: exactly 4)
- [x] Includes safety disclaimer
- [x] skill.json is valid with `requires_api: false`
- [x] No drift from design-spec.md

## Files in This Skill

1. `SKILL.md` — Full workflow, inputs, outputs, examples, safety
2. `README.md` — Quick-start reference
3. `skill.json` — Machine-readable metadata
4. `ACCEPTANCE.md` — This checklist

## Verification Commands

```bash
# Count files in this directory
find /Users/jianghaidong/.openclaw/skills/sv-script-builder -type f | wc -l
# Expected: 4

# Verify skill.json
cat /Users/jianghaidong/.openclaw/skills/sv-script-builder/skill.json | grep requires_api
# Expected: "requires_api": false

# Verify no code files
find /Users/jianghaidong/.openclaw/skills/sv-script-builder -name "*.py" -o -name "*.sh" | wc -l
# Expected: 0
```

---

*Generated for project short-video-skills-2026-04-27*

# Short Video Content Niche Finder

Guides creators through identifying, validating, and refining a unique content niche and positioning for short video platforms.

## Target Users

- New creators
- Pivoters/rebranders
- Marketing strategists
- Agency planners

## When to Use

- Starting a new channel
- Pivoting content direction
- Validating niche viability before investment
- Differentiating in a crowded category

## Core Workflow

1. Personal interest & skill inventory
2. Market gap analysis framework
3. Audience need/pain point mapping
4. Competitive landscape mapping
5. Unique value proposition (UVP) articulation
6. Niche validation checklist

## Inputs

- Creator interests and skills
- Resources
- Platform preferences
- Monetization goals

## Expected Outputs

- Niche shortlist with pros/cons
- UVP statement draft
- Audience persona sketch
- Validation scorecard

## Example Prompts

- "Help me find a short video niche for someone who loves baking, speaks Mandarin, and wants to target the Douyin audience."
- "I currently make travel vlogs but want to pivot — help me explore adjacent niches."
- "Validate whether 'sustainable fashion for college students' is a viable short-video niche."

## Trigger Keywords

find niche, content niche, video positioning, channel niche, niche validation, content strategy

## Safety & Limitations

Niche analysis is strategic guidance only. Market dynamics evolve; users should test with real content. No competitor scraping or market data automation.

---

*Generated for project short-video-skills-2026-04-27*

FILE:skill.json
{
  "slug": "sv-niche-finder",
  "name": "Short Video Content Niche Finder",
  "description": "Guides creators through identifying, validating, and refining a unique content niche and positioning for short video platforms.",
  "type": "descriptive",
  "requires_api": false,
  "readiness": "stable",
  "tags": [
    "video",
    "niche",
    "positioning",
    "strategy",
    "branding",
    "descriptive"
  ],
  "trigger_keywords": [
    "find niche",
    "content niche",
    "video positioning",
    "channel niche",
    "niche validation",
    "content strategy"
  ],
  "max_files": 4,
  "language": "en",
  "safety": "document-only informational guidance"
}

FILE:README.md
# Short Video Content Niche Finder

Guides creators through identifying, validating, and refining a unique content niche and positioning for short video platforms.

## Target Users

- New creators
- Pivoters/rebranders
- Marketing strategists
- Agency planners

## When to Use

- Starting a new channel
- Pivoting content direction
- Validating niche viability before investment
- Differentiating in a crowded category

## Trigger Keywords

find niche, content niche, video positioning, channel niche, niche validation, content strategy

## Full Documentation

See [SKILL.md](./SKILL.md) for complete workflow, inputs, outputs, and examples.

---

*Generated for project short-video-skills-2026-04-27*

FILE:ACCEPTANCE.md
# Acceptance Checklist — Short Video Content Niche Finder

## Criteria

- [x] Document-only: no handler.py, scripts, APIs, or executable code
- [x] No network calls or credential handling
- [x] English-first documentation
- [x] File count ≤ 10 (target: exactly 4)
- [x] Includes safety disclaimer
- [x] skill.json is valid with `requires_api: false`
- [x] No drift from design-spec.md

## Files in This Skill

1. `SKILL.md` — Full workflow, inputs, outputs, examples, safety
2. `README.md` — Quick-start reference
3. `skill.json` — Machine-readable metadata
4. `ACCEPTANCE.md` — This checklist

## Verification Commands

```bash
# Count files in this directory
find /Users/jianghaidong/.openclaw/skills/sv-niche-finder -type f | wc -l
# Expected: 4

# Verify skill.json
cat /Users/jianghaidong/.openclaw/skills/sv-niche-finder/skill.json | grep requires_api
# Expected: "requires_api": false

# Verify no code files
find /Users/jianghaidong/.openclaw/skills/sv-niche-finder -name "*.py" -o -name "*.sh" | wc -l
# Expected: 0
```

---

*Generated for project short-video-skills-2026-04-27*

# Short Video Content Calendar Planner

Helps creators plan and structure posting schedules, content themes, and production timelines for short video series.

## Target Users

- Content creators
- Social media managers
- Marketing teams
- Multi-platform publishers

## When to Use

- Planning a monthly/weekly content pipeline
- Aligning content with seasonal events or product launches
- Balancing content mix across formats

## Core Workflow

1. Time horizon & cadence definition
2. Content pillar / theme mapping
3. Production timeline back-planning
4. Platform-specific posting time optimization
5. Content mix balance check

## Inputs

- Publishing goals
- Content pillars
- Available production days
- Key dates/events
- Platform preferences

## Expected Outputs

- Content calendar template
- Weekly/monthly posting grid
- Production milestone schedule
- Content mix ratio recommendations

## Example Prompts

- "Help me plan a 30-day content calendar for a tech review channel posting daily on Douyin."
- "Build a weekly content mix for a fitness brand covering tutorial, motivation, and product content."
- "Align my content calendar with upcoming e-commerce shopping festivals in Q2."

## Trigger Keywords

content calendar, posting schedule, video planning, content timeline, content mix, video cadence

## Safety & Limitations

Scheduling recommendations are guidelines, not guarantees of optimal performance. Platform algorithms change; users should validate timing with their own analytics.

---

*Generated for project short-video-skills-2026-04-27*

FILE:skill.json
{
  "slug": "sv-content-calendar",
  "name": "Short Video Content Calendar Planner",
  "description": "Helps creators plan and structure posting schedules, content themes, and production timelines for short video series.",
  "type": "descriptive",
  "requires_api": false,
  "readiness": "stable",
  "tags": [
    "video",
    "planning",
    "calendar",
    "scheduling",
    "strategy",
    "descriptive"
  ],
  "trigger_keywords": [
    "content calendar",
    "posting schedule",
    "video planning",
    "content timeline",
    "content mix",
    "video cadence"
  ],
  "max_files": 4,
  "language": "en",
  "safety": "document-only informational guidance"
}

FILE:README.md
# Short Video Content Calendar Planner

Helps creators plan and structure posting schedules, content themes, and production timelines for short video series.

## Target Users

- Content creators
- Social media managers
- Marketing teams
- Multi-platform publishers

## When to Use

- Planning a monthly/weekly content pipeline
- Aligning content with seasonal events or product launches
- Balancing content mix across formats

## Trigger Keywords

content calendar, posting schedule, video planning, content timeline, content mix, video cadence

## Full Documentation

See [SKILL.md](./SKILL.md) for complete workflow, inputs, outputs, and examples.

---

*Generated for project short-video-skills-2026-04-27*

FILE:ACCEPTANCE.md
# Acceptance Checklist — Short Video Content Calendar Planner

## Criteria

- [x] Document-only: no handler.py, scripts, APIs, or executable code
- [x] No network calls or credential handling
- [x] English-first documentation
- [x] File count ≤ 10 (target: exactly 4)
- [x] Includes safety disclaimer
- [x] skill.json is valid with `requires_api: false`
- [x] No drift from design-spec.md

## Files in This Skill

1. `SKILL.md` — Full workflow, inputs, outputs, examples, safety
2. `README.md` — Quick-start reference
3. `skill.json` — Machine-readable metadata
4. `ACCEPTANCE.md` — This checklist

## Verification Commands

```bash
# Count files in this directory
find /Users/jianghaidong/.openclaw/skills/sv-content-calendar -type f | wc -l
# Expected: 4

# Verify skill.json
cat /Users/jianghaidong/.openclaw/skills/sv-content-calendar/skill.json | grep requires_api
# Expected: "requires_api": false

# Verify no code files
find /Users/jianghaidong/.openclaw/skills/sv-content-calendar -name "*.py" -o -name "*.sh" | wc -l
# Expected: 0
```

---

*Generated for project short-video-skills-2026-04-27*

# Short Video Idea Generator

Generates short-video topic ideas, creative angles, and format suggestions based on niche, trend, and audience.

## Target Users

- Content creators
- Social media managers
- Influencers
- Marketing teams
- Beginners

## When to Use

- Running out of content ideas
- Brainstorming a new content series
- Adapting trending topics to your niche
- Planning a themed content sprint

## Core Workflow

1. Niche & audience context capture
2. Idea brainstorming matrix (tutorial, storytelling, reaction, challenge, listicle)
3. Trend-adaptation prompts
4. Angle diversification (same topic, 5 angles)
5. Idea prioritization rubric (effort vs. potential reach)

## Inputs

- Niche description
- Target audience profile
- Platform(s)
- Content goals
- Constraints (e.g., solo filming, no budget)

## Expected Outputs

- 10–30 video topic ideas
- Title draft per idea
- Format suggestion per idea
- Target audience hook
- Estimated difficulty

## Example Prompts

- "Generate 15 short video ideas for a home-cooking channel targeting busy parents on Douyin."
- "Give me 5 angles on the topic 'morning routine' for a fitness creator."
- "Adapt the current 'day in the life' trend to a remote software developer niche."

## Trigger Keywords

video ideas, content ideas, brainstorm video, video topics, creative angles, short video brainstorm

## Safety & Limitations

Ideas are creative suggestions only; no guarantee of virality or platform compliance. Users are responsible for content originality and copyright clearance.

---

*Generated for project short-video-skills-2026-04-27*

FILE:skill.json
{
  "slug": "sv-idea-generator",
  "name": "Short Video Idea Generator",
  "description": "Generates short-video topic ideas, creative angles, and format suggestions based on niche, trend, and audience.",
  "type": "descriptive",
  "requires_api": false,
  "readiness": "stable",
  "tags": [
    "video",
    "ideation",
    "brainstorming",
    "creative",
    "descriptive"
  ],
  "trigger_keywords": [
    "video ideas",
    "content ideas",
    "brainstorm video",
    "video topics",
    "creative angles",
    "short video brainstorm"
  ],
  "max_files": 4,
  "language": "en",
  "safety": "document-only informational guidance"
}

FILE:README.md
# Short Video Idea Generator

Generates short-video topic ideas, creative angles, and format suggestions based on niche, trend, and audience.

## Target Users

- Content creators
- Social media managers
- Influencers
- Marketing teams
- Beginners

## When to Use

- Running out of content ideas
- Brainstorming a new content series
- Adapting trending topics to your niche
- Planning a themed content sprint

## Trigger Keywords

video ideas, content ideas, brainstorm video, video topics, creative angles, short video brainstorm

## Full Documentation

See [SKILL.md](./SKILL.md) for complete workflow, inputs, outputs, and examples.

---

*Generated for project short-video-skills-2026-04-27*

FILE:ACCEPTANCE.md
# Acceptance Checklist — Short Video Idea Generator

## Criteria

- [x] Document-only: no handler.py, scripts, APIs, or executable code
- [x] No network calls or credential handling
- [x] English-first documentation
- [x] File count ≤ 10 (target: exactly 4)
- [x] Includes safety disclaimer
- [x] skill.json is valid with `requires_api: false`
- [x] No drift from design-spec.md

## Files in This Skill

1. `SKILL.md` — Full workflow, inputs, outputs, examples, safety
2. `README.md` — Quick-start reference
3. `skill.json` — Machine-readable metadata
4. `ACCEPTANCE.md` — This checklist

## Verification Commands

```bash
# Count files in this directory
find /Users/jianghaidong/.openclaw/skills/sv-idea-generator -type f | wc -l
# Expected: 4

# Verify skill.json
cat /Users/jianghaidong/.openclaw/skills/sv-idea-generator/skill.json | grep requires_api
# Expected: "requires_api": false

# Verify no code files
find /Users/jianghaidong/.openclaw/skills/sv-idea-generator -name "*.py" -o -name "*.sh" | wc -l
# Expected: 0
```

---

*Generated for project short-video-skills-2026-04-27*

---
slug: legal-client-communication-drafter
version: "1.0.0"
type: descriptive
language: en
---

# Legal Client Communication Drafter

## Overview

Helps draft clear, professional, non-final client communication structures for updates, document requests, expectation setting, and next steps. 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 client update emails
- Requesting documents
- Explaining process steps in plain language
- Setting expectations on timing and next actions


## Target Users

- Attorneys
- Paralegals
- Client service teams
- In-house counsel


## 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. **Client-update structure** — provides structured prompts, checklists, and review fields for this area.
2. **Plain-language explanation prompts** — provides structured prompts, checklists, and review fields for this area.
3. **Document request format** — provides structured prompts, checklists, and review fields for this area.
4. **Expectation and next-step checklist** — provides structured prompts, checklists, and review fields for this area.
5. **Tone and sensitivity review** — 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

- Client email draft structure
- Document request checklist
- Plain-language summary
- Tone review notes

## Example Prompts

- "Draft a client update structure for a delayed court ruling."
- "Create a document request email template for a new matter."

## 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: Drafts are not final legal advice and must be reviewed for privilege, confidentiality, accuracy, and attorney-client relationship issues.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Client Communication Drafter

Helps draft clear, professional, non-final client communication structures for updates, document requests, expectation setting, and next steps.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Client-update structure
- Plain-language explanation prompts
- Document request format
- Expectation and next-step checklist
- Tone and sensitivity review

## Trigger Keywords

client update, legal email draft, document request email, plain language legal, legal-client-communication-drafter, legal client communication drafter

## Example Prompts

- "Draft a client update structure for a delayed court ruling."
- "Create a document request email template for a new matter."

## Outputs

- Client email draft structure
- Document request checklist
- Plain-language summary
- Tone review notes


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Client Communication Drafter",
  "slug": "legal-client-communication-drafter",
  "version": "1.0.0",
  "description": "Helps draft clear, professional, non-final client communication structures for updates, document requests, expectation setting, and next steps.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "client-communication",
    "plain-language",
    "law-firm",
    "descriptive"
  ],
  "trigger_keywords": [
    "client update",
    "legal email draft",
    "document request email",
    "plain language legal",
    "legal-client-communication-drafter",
    "legal client communication drafter"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-law-firm-ops-dashboard
version: "1.0.0"
type: descriptive
language: en
---

# Legal Law Firm Ops Dashboard

## Overview

Designs descriptive dashboards for law firm matter status, workload, deadlines, billing hygiene, client communication, and risk flags. 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

- Improving matter visibility
- Creating weekly practice reports
- Standardizing operational review meetings


## Target Users

- Law firm managers
- Practice group leaders
- Legal operations professionals
- Managing partners


## 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. **Matter status fields** — provides structured prompts, checklists, and review fields for this area.
2. **Workload and deadline indicators** — provides structured prompts, checklists, and review fields for this area.
3. **Billing and WIP hygiene prompts** — provides structured prompts, checklists, and review fields for this area.
4. **Client communication cadence tracker** — provides structured prompts, checklists, and review fields for this area.
5. **Risk escalation dashboard** — 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

- Dashboard field list
- Weekly report template
- Risk flag definitions
- Meeting agenda

## Example Prompts

- "Design a weekly litigation practice dashboard."
- "Create a law firm matter status dashboard template."

## 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: Operational guidance only; does not access billing systems or client data automatically.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Law Firm Ops Dashboard

Designs descriptive dashboards for law firm matter status, workload, deadlines, billing hygiene, client communication, and risk flags.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Matter status fields
- Workload and deadline indicators
- Billing and WIP hygiene prompts
- Client communication cadence tracker
- Risk escalation dashboard

## Trigger Keywords

law firm dashboard, matter status report, legal operations, billing hygiene, legal-law-firm-ops-dashboard, legal law firm ops dashboard

## Example Prompts

- "Design a weekly litigation practice dashboard."
- "Create a law firm matter status dashboard template."

## Outputs

- Dashboard field list
- Weekly report template
- Risk flag definitions
- Meeting agenda


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Law Firm Ops Dashboard",
  "slug": "legal-law-firm-ops-dashboard",
  "version": "1.0.0",
  "description": "Designs descriptive dashboards for law firm matter status, workload, deadlines, billing hygiene, client communication, and risk flags.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "law-firm",
    "legal-ops",
    "dashboard",
    "descriptive"
  ],
  "trigger_keywords": [
    "law firm dashboard",
    "matter status report",
    "legal operations",
    "billing hygiene",
    "legal-law-firm-ops-dashboard",
    "legal law firm ops dashboard"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-settlement-evaluation-framework
version: "1.0.0"
type: descriptive
language: en
---

# Legal Settlement Evaluation Framework

## Overview

Helps evaluate settlement options using exposure, evidence strength, litigation cost, non-monetary terms, timing, and uncertainty. 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

- Assessing settlement offers
- Preparing client recommendation memos
- Comparing litigation versus resolution options


## Target Users

- Litigators
- In-house counsel
- Claims teams
- Business stakeholders


## 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. **Exposure and damages range table** — provides structured prompts, checklists, and review fields for this area.
2. **Evidence strength factors** — provides structured prompts, checklists, and review fields for this area.
3. **Cost/time/risk comparison** — provides structured prompts, checklists, and review fields for this area.
4. **Non-monetary term checklist** — provides structured prompts, checklists, and review fields for this area.
5. **Decision memo template** — 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

- Settlement evaluation matrix
- Risk-adjusted comparison
- Client recommendation outline
- Open issues list

## Example Prompts

- "Build a settlement evaluation matrix for a contract dispute."
- "Help compare accepting an offer versus continuing litigation."

## 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 predict court outcomes or advise acceptance; final settlement decisions require attorney-client analysis.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Settlement Evaluation Framework

Helps evaluate settlement options using exposure, evidence strength, litigation cost, non-monetary terms, timing, and uncertainty.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Exposure and damages range table
- Evidence strength factors
- Cost/time/risk comparison
- Non-monetary term checklist
- Decision memo template

## Trigger Keywords

settlement evaluation, litigation exposure, settlement matrix, case risk, legal-settlement-evaluation-framework, legal settlement evaluation framework

## Example Prompts

- "Build a settlement evaluation matrix for a contract dispute."
- "Help compare accepting an offer versus continuing litigation."

## Outputs

- Settlement evaluation matrix
- Risk-adjusted comparison
- Client recommendation outline
- Open issues list


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Settlement Evaluation Framework",
  "slug": "legal-settlement-evaluation-framework",
  "version": "1.0.0",
  "description": "Helps evaluate settlement options using exposure, evidence strength, litigation cost, non-monetary terms, timing, and uncertainty.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "settlement",
    "litigation",
    "risk",
    "descriptive"
  ],
  "trigger_keywords": [
    "settlement evaluation",
    "litigation exposure",
    "settlement matrix",
    "case risk",
    "legal-settlement-evaluation-framework",
    "legal settlement evaluation framework"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-negotiation-position-planner
version: "1.0.0"
type: descriptive
language: en
---

# Legal Negotiation Position Planner

## Overview

Structures legal and commercial negotiation preparation around objectives, leverage, concessions, BATNA, risks, and communication strategy. 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 contract negotiations
- Planning settlement discussions
- Aligning legal and business positions


## Target Users

- Deal lawyers
- Litigators
- In-house counsel
- Business negotiators working with legal


## 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. **Objective and fallback map** — provides structured prompts, checklists, and review fields for this area.
2. **Issue-by-issue position table** — provides structured prompts, checklists, and review fields for this area.
3. **Leverage and risk assessment** — provides structured prompts, checklists, and review fields for this area.
4. **Concession strategy planner** — provides structured prompts, checklists, and review fields for this area.
5. **Communication and escalation plan** — 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

- Negotiation plan
- Issue/concession matrix
- Risk and leverage notes
- Meeting agenda

## Example Prompts

- "Create a negotiation position plan for a vendor agreement."
- "Help prepare settlement negotiation positions for a dispute."

## 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 provide coercive tactics or guarantee outcomes; negotiation must comply with law and professional ethics.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Negotiation Position Planner

Structures legal and commercial negotiation preparation around objectives, leverage, concessions, BATNA, risks, and communication strategy.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Objective and fallback map
- Issue-by-issue position table
- Leverage and risk assessment
- Concession strategy planner
- Communication and escalation plan

## Trigger Keywords

legal negotiation, BATNA, concession matrix, settlement position, legal-negotiation-position-planner, legal negotiation position planner

## Example Prompts

- "Create a negotiation position plan for a vendor agreement."
- "Help prepare settlement negotiation positions for a dispute."

## Outputs

- Negotiation plan
- Issue/concession matrix
- Risk and leverage notes
- Meeting agenda


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Negotiation Position Planner",
  "slug": "legal-negotiation-position-planner",
  "version": "1.0.0",
  "description": "Structures legal and commercial negotiation preparation around objectives, leverage, concessions, BATNA, risks, and communication strategy.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "negotiation",
    "contracts",
    "settlement",
    "descriptive"
  ],
  "trigger_keywords": [
    "legal negotiation",
    "BATNA",
    "concession matrix",
    "settlement position",
    "legal-negotiation-position-planner",
    "legal negotiation position planner"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-legal-writing-editor
version: "1.0.0"
type: descriptive
language: en
---

# Legal Writing Editor

## Overview

Improves legal writing structure by organizing issues, arguments, headings, authorities, clarity, tone, and reader-focused summaries. 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

- Revising memos, briefs, letters, or client updates
- Improving argument structure
- Making legal writing clearer for non-lawyers


## Target Users

- Lawyers
- Legal writers
- Law students
- In-house counsel


## 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. **Issue-framing check** — provides structured prompts, checklists, and review fields for this area.
2. **Argument structure review** — provides structured prompts, checklists, and review fields for this area.
3. **Heading and roadmap builder** — provides structured prompts, checklists, and review fields for this area.
4. **Authority integration checklist** — provides structured prompts, checklists, and review fields for this area.
5. **Plain-English rewrite prompts** — 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

- Revision checklist
- Suggested outline
- Plain-English summary
- Tone and clarity notes

## Example Prompts

- "Help improve the structure of this legal memo."
- "Turn this legal explanation into a clearer client update."

## 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 verify legal authorities or citations; users must confirm accuracy and ethics obligations.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Writing Editor

Improves legal writing structure by organizing issues, arguments, headings, authorities, clarity, tone, and reader-focused summaries.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Issue-framing check
- Argument structure review
- Heading and roadmap builder
- Authority integration checklist
- Plain-English rewrite prompts

## Trigger Keywords

legal writing, legal memo editor, brief structure, plain English legal, legal-legal-writing-editor, legal writing editor

## Example Prompts

- "Help improve the structure of this legal memo."
- "Turn this legal explanation into a clearer client update."

## Outputs

- Revision checklist
- Suggested outline
- Plain-English summary
- Tone and clarity notes


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Writing Editor",
  "slug": "legal-legal-writing-editor",
  "version": "1.0.0",
  "description": "Improves legal writing structure by organizing issues, arguments, headings, authorities, clarity, tone, and reader-focused summaries.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "writing",
    "memo",
    "brief",
    "descriptive"
  ],
  "trigger_keywords": [
    "legal writing",
    "legal memo editor",
    "brief structure",
    "plain English legal",
    "legal-legal-writing-editor",
    "legal writing editor"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-ip-portfolio-audit-guide
version: "1.0.0"
type: descriptive
language: en
---

# Legal IP Portfolio Audit Guide

## Overview

Helps organize intellectual property assets, ownership records, registrations, licenses, enforcement needs, and commercialization risks. 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 an IP audit
- Reviewing ownership before financing
- Organizing brand/patent/copyright assets


## Target Users

- IP lawyers
- Startup counsel
- Product teams
- Technology companies


## 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. **IP asset inventory** — provides structured prompts, checklists, and review fields for this area.
2. **Ownership and chain-of-title checklist** — provides structured prompts, checklists, and review fields for this area.
3. **Registration and renewal tracker** — provides structured prompts, checklists, and review fields for this area.
4. **License and encumbrance map** — provides structured prompts, checklists, and review fields for this area.
5. **Enforcement/commercialization issue 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

- IP inventory table
- Ownership gap list
- Renewal tracker
- License issue map

## Example Prompts

- "Create an IP portfolio audit checklist for a software startup."
- "Help organize trademarks, patents, and copyrights before fundraising."

## 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 file IP rights or determine validity; users must consult qualified IP counsel.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal IP Portfolio Audit Guide

Helps organize intellectual property assets, ownership records, registrations, licenses, enforcement needs, and commercialization risks.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- IP asset inventory
- Ownership and chain-of-title checklist
- Registration and renewal tracker
- License and encumbrance map
- Enforcement/commercialization issue list

## Trigger Keywords

IP audit, trademark portfolio, patent checklist, intellectual property assets, legal-ip-portfolio-audit-guide, legal ip portfolio audit guide

## Example Prompts

- "Create an IP portfolio audit checklist for a software startup."
- "Help organize trademarks, patents, and copyrights before fundraising."

## Outputs

- IP inventory table
- Ownership gap list
- Renewal tracker
- License issue map


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal IP Portfolio Audit Guide",
  "slug": "legal-ip-portfolio-audit-guide",
  "version": "1.0.0",
  "description": "Helps organize intellectual property assets, ownership records, registrations, licenses, enforcement needs, and commercialization risks.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "ip",
    "intellectual-property",
    "audit",
    "descriptive"
  ],
  "trigger_keywords": [
    "IP audit",
    "trademark portfolio",
    "patent checklist",
    "intellectual property assets",
    "legal-ip-portfolio-audit-guide",
    "legal ip portfolio audit guide"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-employment-policy-reviewer
version: "1.0.0"
type: descriptive
language: en
---

# Legal Employment Policy Reviewer

## Overview

Provides a structured framework for reviewing employee handbooks, workplace policies, HR procedures, and employment risk areas. 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

- Reviewing employee handbook updates
- Preparing HR policy audits
- Spotting employment-law risk areas


## Target Users

- Employment lawyers
- HR legal teams
- People operations leaders
- Compliance 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. **Policy inventory checklist** — provides structured prompts, checklists, and review fields for this area.
2. **Jurisdiction and workforce scope notes** — provides structured prompts, checklists, and review fields for this area.
3. **Required vs optional policy map** — provides structured prompts, checklists, and review fields for this area.
4. **Risk and consistency review** — provides structured prompts, checklists, and review fields for this area.
5. **Employee communication checklist** — 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

- Policy review checklist
- Risk issue log
- Update priority matrix
- Communication plan outline

## Example Prompts

- "Create an employment policy review checklist for a remote workforce."
- "Help audit handbook sections for legal risk areas."

## 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: Employment law is jurisdiction-specific; final policies require qualified local counsel review.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Employment Policy Reviewer

Provides a structured framework for reviewing employee handbooks, workplace policies, HR procedures, and employment risk areas.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Policy inventory checklist
- Jurisdiction and workforce scope notes
- Required vs optional policy map
- Risk and consistency review
- Employee communication checklist

## Trigger Keywords

employment policy review, employee handbook, HR legal checklist, workplace policy, legal-employment-policy-reviewer, legal employment policy reviewer

## Example Prompts

- "Create an employment policy review checklist for a remote workforce."
- "Help audit handbook sections for legal risk areas."

## Outputs

- Policy review checklist
- Risk issue log
- Update priority matrix
- Communication plan outline


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Employment Policy Reviewer",
  "slug": "legal-employment-policy-reviewer",
  "version": "1.0.0",
  "description": "Provides a structured framework for reviewing employee handbooks, workplace policies, HR procedures, and employment risk areas.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "employment",
    "hr-policy",
    "compliance",
    "descriptive"
  ],
  "trigger_keywords": [
    "employment policy review",
    "employee handbook",
    "HR legal checklist",
    "workplace policy",
    "legal-employment-policy-reviewer",
    "legal employment policy reviewer"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-privacy-impact-assessment-guide
version: "1.0.0"
type: descriptive
language: en
---

# Legal Privacy Impact Assessment Guide

## Overview

Guides privacy teams through data mapping, processing purposes, risks, safeguards, vendor issues, and privacy review documentation. 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

- Launching products using personal data
- Assessing vendors
- Documenting privacy reviews


## Target Users

- Privacy counsel
- Data protection officers
- Product legal teams
- Compliance 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. **Data inventory prompts** — provides structured prompts, checklists, and review fields for this area.
2. **Purpose and lawful-basis fields** — provides structured prompts, checklists, and review fields for this area.
3. **Risk and safeguard checklist** — provides structured prompts, checklists, and review fields for this area.
4. **Vendor/data transfer considerations** — provides structured prompts, checklists, and review fields for this area.
5. **Privacy review memo template** — 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

- PIA/DPIA-style checklist
- Data flow summary
- Risk/safeguard matrix
- Review memo outline

## Example Prompts

- "Create a privacy impact assessment template for a mobile app."
- "Help map privacy risks for a vendor using customer data."

## 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: Privacy laws vary widely; this does not replace GDPR/CCPA/PIPL or local legal analysis.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Privacy Impact Assessment Guide

Guides privacy teams through data mapping, processing purposes, risks, safeguards, vendor issues, and privacy review documentation.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Data inventory prompts
- Purpose and lawful-basis fields
- Risk and safeguard checklist
- Vendor/data transfer considerations
- Privacy review memo template

## Trigger Keywords

privacy impact assessment, DPIA, data protection, privacy review, legal-privacy-impact-assessment-guide, legal privacy impact assessment guide

## Example Prompts

- "Create a privacy impact assessment template for a mobile app."
- "Help map privacy risks for a vendor using customer data."

## Outputs

- PIA/DPIA-style checklist
- Data flow summary
- Risk/safeguard matrix
- Review memo outline


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Privacy Impact Assessment Guide",
  "slug": "legal-privacy-impact-assessment-guide",
  "version": "1.0.0",
  "description": "Guides privacy teams through data mapping, processing purposes, risks, safeguards, vendor issues, and privacy review documentation.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "privacy",
    "data-protection",
    "compliance",
    "descriptive"
  ],
  "trigger_keywords": [
    "privacy impact assessment",
    "DPIA",
    "data protection",
    "privacy review",
    "legal-privacy-impact-assessment-guide",
    "legal privacy impact assessment guide"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-regulatory-compliance-mapper
version: "1.0.0"
type: descriptive
language: en
---

# Legal Regulatory Compliance Mapper

## Overview

Helps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction. 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

- Building a compliance program
- Entering a regulated market
- Preparing an internal audit


## Target Users

- Compliance counsel
- In-house legal teams
- Risk managers
- Startup operators


## 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. **Regulatory obligation inventory** — provides structured prompts, checklists, and review fields for this area.
2. **Control-owner mapping** — provides structured prompts, checklists, and review fields for this area.
3. **Evidence and documentation tracker** — provides structured prompts, checklists, and review fields for this area.
4. **Review cadence planner** — provides structured prompts, checklists, and review fields for this area.
5. **Issue escalation matrix** — 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

- Compliance obligation map
- Controls tracker
- Evidence checklist
- Review calendar

## Example Prompts

- "Map compliance obligations for a fintech product launch."
- "Create a regulatory controls tracker for a healthcare startup."

## 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 determine full legal compliance; users must confirm obligations with qualified jurisdiction-specific professionals.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Regulatory Compliance Mapper

Helps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Regulatory obligation inventory
- Control-owner mapping
- Evidence and documentation tracker
- Review cadence planner
- Issue escalation matrix

## Trigger Keywords

regulatory compliance, obligation map, controls tracker, compliance program, legal-regulatory-compliance-mapper, legal regulatory compliance mapper

## Example Prompts

- "Map compliance obligations for a fintech product launch."
- "Create a regulatory controls tracker for a healthcare startup."

## Outputs

- Compliance obligation map
- Controls tracker
- Evidence checklist
- Review calendar


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Regulatory Compliance Mapper",
  "slug": "legal-regulatory-compliance-mapper",
  "version": "1.0.0",
  "description": "Helps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "compliance",
    "regulatory",
    "risk",
    "descriptive"
  ],
  "trigger_keywords": [
    "regulatory compliance",
    "obligation map",
    "controls tracker",
    "compliance program",
    "legal-regulatory-compliance-mapper",
    "legal regulatory compliance mapper"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-due-diligence-checklist
version: "1.0.0"
type: descriptive
language: en
---

# Legal Due Diligence Checklist

## Overview

Creates legal due diligence checklists for transactions, investments, acquisitions, vendor onboarding, and corporate housekeeping. 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 diligence requests
- Reviewing target company documents
- Organizing transaction risk findings


## Target Users

- Corporate attorneys
- M&A teams
- Startup counsel
- Investment 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. **Corporate records checklist** — provides structured prompts, checklists, and review fields for this area.
2. **Contracts and obligations review** — provides structured prompts, checklists, and review fields for this area.
3. **Employment/IP/compliance review** — provides structured prompts, checklists, and review fields for this area.
4. **Litigation and regulatory search plan** — provides structured prompts, checklists, and review fields for this area.
5. **Red-flag summary template** — 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

- Diligence request list
- Issue tracker
- Red-flag summary
- Document index

## Example Prompts

- "Create a legal due diligence checklist for a small acquisition."
- "Help organize diligence requests for a startup investment."

## 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: Framework only; diligence scope must be tailored by transaction counsel and local law experts.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Due Diligence Checklist

Creates legal due diligence checklists for transactions, investments, acquisitions, vendor onboarding, and corporate housekeeping.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Corporate records checklist
- Contracts and obligations review
- Employment/IP/compliance review
- Litigation and regulatory search plan
- Red-flag summary template

## Trigger Keywords

legal due diligence, M&A checklist, investment diligence, corporate records, legal-due-diligence-checklist, legal due diligence checklist

## Example Prompts

- "Create a legal due diligence checklist for a small acquisition."
- "Help organize diligence requests for a startup investment."

## Outputs

- Diligence request list
- Issue tracker
- Red-flag summary
- Document index


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Due Diligence Checklist",
  "slug": "legal-due-diligence-checklist",
  "version": "1.0.0",
  "description": "Creates legal due diligence checklists for transactions, investments, acquisitions, vendor onboarding, and corporate housekeeping.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "due-diligence",
    "transactions",
    "corporate",
    "descriptive"
  ],
  "trigger_keywords": [
    "legal due diligence",
    "M&A checklist",
    "investment diligence",
    "corporate records",
    "legal-due-diligence-checklist",
    "legal due diligence checklist"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-case-strategy-memo-builder
version: "1.0.0"
type: descriptive
language: en
---

# Legal Case Strategy Memo Builder

## Overview

Structures case strategy memos around facts, issues, claims, defenses, strengths, weaknesses, risks, and next actions. 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 internal case assessments
- Updating clients or supervisors
- Deciding litigation strategy


## Target Users

- Attorneys
- Legal teams
- Law firm partners
- In-house litigation managers


## 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 and issue summary** — provides structured prompts, checklists, and review fields for this area.
2. **Claims/defenses map** — provides structured prompts, checklists, and review fields for this area.
3. **Strengths and weaknesses analysis** — provides structured prompts, checklists, and review fields for this area.
4. **Risk and cost considerations** — provides structured prompts, checklists, and review fields for this area.
5. **Recommended next actions** — 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

- Strategy memo outline
- Risk matrix
- Action plan
- Client update skeleton

## Example Prompts

- "Build a case strategy memo template for a commercial dispute."
- "Help structure a litigation risk assessment for management."

## 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 predict outcomes with certainty; strategic decisions require attorney judgment and current law review.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Case Strategy Memo Builder

Structures case strategy memos around facts, issues, claims, defenses, strengths, weaknesses, risks, and next actions.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Fact and issue summary
- Claims/defenses map
- Strengths and weaknesses analysis
- Risk and cost considerations
- Recommended next actions

## Trigger Keywords

case strategy memo, litigation risk assessment, claims defenses, legal memo, legal-case-strategy-memo-builder, legal case strategy memo builder

## Example Prompts

- "Build a case strategy memo template for a commercial dispute."
- "Help structure a litigation risk assessment for management."

## Outputs

- Strategy memo outline
- Risk matrix
- Action plan
- Client update skeleton


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Case Strategy Memo Builder",
  "slug": "legal-case-strategy-memo-builder",
  "version": "1.0.0",
  "description": "Structures case strategy memos around facts, issues, claims, defenses, strengths, weaknesses, risks, and next actions.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "case-strategy",
    "litigation",
    "memo",
    "descriptive"
  ],
  "trigger_keywords": [
    "case strategy memo",
    "litigation risk assessment",
    "claims defenses",
    "legal memo",
    "legal-case-strategy-memo-builder",
    "legal case strategy memo builder"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-trial-preparation-checklist
version: "1.0.0"
type: descriptive
language: en
---

# Legal Trial Preparation Checklist

## Overview

Provides trial readiness checklists for exhibits, witnesses, motions, openings, closings, logistics, and daily courtroom workflow. 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 for trial
- Running pretrial readiness checks
- Coordinating courtroom logistics


## Target Users

- Trial lawyers
- Paralegals
- Litigation support 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. **Trial calendar and milestone checklist** — provides structured prompts, checklists, and review fields for this area.
2. **Exhibit and witness readiness** — provides structured prompts, checklists, and review fields for this area.
3. **Motions and orders tracker** — provides structured prompts, checklists, and review fields for this area.
4. **Courtroom logistics list** — provides structured prompts, checklists, and review fields for this area.
5. **Daily trial notebook structure** — 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

- Trial readiness checklist
- Trial notebook outline
- Logistics tracker
- Witness/exhibit status table

## Example Prompts

- "Create a 30-day trial preparation checklist."
- "Help me organize a trial notebook for a commercial dispute."

## 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: Court rules, judge-specific procedures, and evidentiary rulings must be verified by the legal team.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Trial Preparation Checklist

Provides trial readiness checklists for exhibits, witnesses, motions, openings, closings, logistics, and daily courtroom workflow.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Trial calendar and milestone checklist
- Exhibit and witness readiness
- Motions and orders tracker
- Courtroom logistics list
- Daily trial notebook structure

## Trigger Keywords

trial preparation, trial checklist, trial notebook, courtroom logistics, legal-trial-preparation-checklist, legal trial preparation checklist

## Example Prompts

- "Create a 30-day trial preparation checklist."
- "Help me organize a trial notebook for a commercial dispute."

## Outputs

- Trial readiness checklist
- Trial notebook outline
- Logistics tracker
- Witness/exhibit status table


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Trial Preparation Checklist",
  "slug": "legal-trial-preparation-checklist",
  "version": "1.0.0",
  "description": "Provides trial readiness checklists for exhibits, witnesses, motions, openings, closings, logistics, and daily courtroom workflow.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "trial",
    "litigation",
    "checklist",
    "descriptive"
  ],
  "trigger_keywords": [
    "trial preparation",
    "trial checklist",
    "trial notebook",
    "courtroom logistics",
    "legal-trial-preparation-checklist",
    "legal trial preparation checklist"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-deposition-prep-coach
version: "1.0.0"
type: descriptive
language: en
---

# Legal Deposition Prep Coach

## Overview

Builds deposition preparation outlines for witnesses, attorneys, themes, exhibits, and question sequences. 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 a witness for deposition
- Drafting deposition outlines
- Organizing exhibits and themes


## Target Users

- Litigators
- Witness preparation teams
- Paralegals


## 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. **Witness background checklist** — provides structured prompts, checklists, and review fields for this area.
2. **Theme and objective map** — provides structured prompts, checklists, and review fields for this area.
3. **Question sequence builder** — provides structured prompts, checklists, and review fields for this area.
4. **Exhibit reference list** — provides structured prompts, checklists, and review fields for this area.
5. **Preparation do/don’t reminders** — 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

- Deposition outline
- Witness prep checklist
- Exhibit/topic map
- Follow-up question bank

## Example Prompts

- "Create a deposition prep outline for a corporate witness."
- "Help organize topics for deposing a former employee."

## 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 coach false testimony or obstruction; all preparation must preserve truthfulness and comply with ethics rules.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Deposition Prep Coach

Builds deposition preparation outlines for witnesses, attorneys, themes, exhibits, and question sequences.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Witness background checklist
- Theme and objective map
- Question sequence builder
- Exhibit reference list
- Preparation do/don’t reminders

## Trigger Keywords

deposition prep, witness preparation, deposition outline, question sequence, legal-deposition-prep-coach, legal deposition prep coach

## Example Prompts

- "Create a deposition prep outline for a corporate witness."
- "Help organize topics for deposing a former employee."

## Outputs

- Deposition outline
- Witness prep checklist
- Exhibit/topic map
- Follow-up question bank


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Deposition Prep Coach",
  "slug": "legal-deposition-prep-coach",
  "version": "1.0.0",
  "description": "Builds deposition preparation outlines for witnesses, attorneys, themes, exhibits, and question sequences.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "deposition",
    "litigation",
    "witness-prep",
    "descriptive"
  ],
  "trigger_keywords": [
    "deposition prep",
    "witness preparation",
    "deposition outline",
    "question sequence",
    "legal-deposition-prep-coach",
    "legal deposition prep coach"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-discovery-request-planner
version: "1.0.0"
type: descriptive
language: en
---

# Legal Discovery Request Planner

## Overview

Helps litigation teams plan discovery objectives, request categories, custodians, objections, and production review workflows. 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

- Planning document requests
- Preparing interrogatory themes
- Coordinating eDiscovery scope


## Target Users

- Litigators
- Discovery counsel
- Paralegals
- eDiscovery managers


## 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. **Discovery objective map** — provides structured prompts, checklists, and review fields for this area.
2. **Request category planner** — provides structured prompts, checklists, and review fields for this area.
3. **Custodian/source inventory** — provides structured prompts, checklists, and review fields for this area.
4. **Objection and burden considerations** — provides structured prompts, checklists, and review fields for this area.
5. **Production review checklist** — 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

- Discovery plan
- Request category list
- Custodian map
- Review checklist

## Example Prompts

- "Plan discovery requests for a product liability matter."
- "Create a custodian and source map for eDiscovery."

## 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: Informational planning only; discovery requests and objections must comply with applicable rules and court orders.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Discovery Request Planner

Helps litigation teams plan discovery objectives, request categories, custodians, objections, and production review workflows.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Discovery objective map
- Request category planner
- Custodian/source inventory
- Objection and burden considerations
- Production review checklist

## Trigger Keywords

discovery plan, document requests, custodian map, eDiscovery, legal-discovery-request-planner, legal discovery request planner

## Example Prompts

- "Plan discovery requests for a product liability matter."
- "Create a custodian and source map for eDiscovery."

## Outputs

- Discovery plan
- Request category list
- Custodian map
- Review checklist


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Discovery Request Planner",
  "slug": "legal-discovery-request-planner",
  "version": "1.0.0",
  "description": "Helps litigation teams plan discovery objectives, request categories, custodians, objections, and production review workflows.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "discovery",
    "ediscovery",
    "litigation",
    "descriptive"
  ],
  "trigger_keywords": [
    "discovery plan",
    "document requests",
    "custodian map",
    "eDiscovery",
    "legal-discovery-request-planner",
    "legal discovery request planner"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-evidence-organization-matrix
version: "1.0.0"
type: descriptive
language: en
---

# Legal Evidence Organization Matrix

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Evidence Organization Matrix

Creates evidence organization frameworks linking documents, witnesses, issues, authenticity, relevance, and proof gaps.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Evidence inventory fields
- Issue-to-evidence map
- Witness/document cross-reference
- Authenticity and chain-of-custody notes
- Proof-gap tracker

## Trigger Keywords

evidence matrix, proof map, witness documents, chain of custody, legal-evidence-organization-matrix, legal evidence organization matrix

## Example Prompts

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

## Outputs

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


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Evidence Organization Matrix",
  "slug": "legal-evidence-organization-matrix",
  "version": "1.0.0",
  "description": "Creates evidence organization frameworks linking documents, witnesses, issues, authenticity, relevance, and proof gaps.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "evidence",
    "litigation",
    "case-prep",
    "descriptive"
  ],
  "trigger_keywords": [
    "evidence matrix",
    "proof map",
    "witness documents",
    "chain of custody",
    "legal-evidence-organization-matrix",
    "legal evidence organization matrix"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Litigation Timeline Builder

Organizes litigation facts, procedural events, deadlines, and evidence references into a coherent case timeline.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Fact chronology table
- Procedural deadline tracker
- Source/evidence reference field
- Disputed vs undisputed facts
- Gap and follow-up list

## Trigger Keywords

litigation timeline, case chronology, fact chronology, court deadlines, legal-litigation-timeline-builder, legal litigation timeline builder

## Example Prompts

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

## Outputs

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


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Litigation Timeline Builder",
  "slug": "legal-litigation-timeline-builder",
  "version": "1.0.0",
  "description": "Organizes litigation facts, procedural events, deadlines, and evidence references into a coherent case timeline.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "litigation",
    "timeline",
    "case-management",
    "descriptive"
  ],
  "trigger_keywords": [
    "litigation timeline",
    "case chronology",
    "fact chronology",
    "court deadlines",
    "legal-litigation-timeline-builder",
    "legal litigation timeline builder"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-clause-risk-spotter
version: "1.0.0"
type: descriptive
language: en
---

# Legal Clause Risk Spotter

## Overview

Guides reviewers through identifying common risk patterns in clauses such as indemnity, liability, termination, IP, confidentiality, and governing law. 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

- Screening a draft agreement for risk
- Training junior reviewers
- Preparing a clause issue list


## Target Users

- Lawyers
- Contract managers
- Legal operations professionals


## 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. **High-risk clause taxonomy** — provides structured prompts, checklists, and review fields for this area.
2. **Clause-by-clause issue prompts** — provides structured prompts, checklists, and review fields for this area.
3. **Business impact notes** — provides structured prompts, checklists, and review fields for this area.
4. **Fallback language considerations** — provides structured prompts, checklists, and review fields for this area.
5. **Escalation criteria** — 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

- Clause risk checklist
- Issue spotting matrix
- Escalation notes

## Example Prompts

- "Spot risks I should check in an indemnity clause."
- "Create a clause risk checklist for a master services agreement."

## 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 rewrite binding legal terms automatically; suggested considerations require attorney review.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Clause Risk Spotter

Guides reviewers through identifying common risk patterns in clauses such as indemnity, liability, termination, IP, confidentiality, and governing law.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- High-risk clause taxonomy
- Clause-by-clause issue prompts
- Business impact notes
- Fallback language considerations
- Escalation criteria

## Trigger Keywords

clause risk, indemnity checklist, liability cap, contract clauses, legal-clause-risk-spotter, legal clause risk spotter

## Example Prompts

- "Spot risks I should check in an indemnity clause."
- "Create a clause risk checklist for a master services agreement."

## Outputs

- Clause risk checklist
- Issue spotting matrix
- Escalation notes


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Clause Risk Spotter",
  "slug": "legal-clause-risk-spotter",
  "version": "1.0.0",
  "description": "Guides reviewers through identifying common risk patterns in clauses such as indemnity, liability, termination, IP, confidentiality, and governing law.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "contracts",
    "clause-analysis",
    "risk",
    "descriptive"
  ],
  "trigger_keywords": [
    "clause risk",
    "indemnity checklist",
    "liability cap",
    "contract clauses",
    "legal-clause-risk-spotter",
    "legal clause risk spotter"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-contract-review-playbook
version: "1.0.0"
type: descriptive
language: en
---

# Legal Contract Review Playbook

## Overview

Provides a structured contract review workflow covering parties, obligations, risk allocation, remedies, and negotiation notes. 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

- Reviewing commercial contracts
- Preparing markup notes
- Summarizing contractual risks for stakeholders


## Target Users

- Contract attorneys
- In-house counsel
- Procurement legal teams
- Business reviewers


## 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. **Contract metadata capture** — provides structured prompts, checklists, and review fields for this area.
2. **Key obligation map** — provides structured prompts, checklists, and review fields for this area.
3. **Risk clause checklist** — provides structured prompts, checklists, and review fields for this area.
4. **Fallback position notes** — provides structured prompts, checklists, and review fields for this area.
5. **Executive summary template** — 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

- Contract review checklist
- Issue list
- Negotiation note template
- Stakeholder summary

## Example Prompts

- "Give me a contract review checklist for a SaaS agreement."
- "Help structure a risk summary for this vendor contract."

## 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: Framework only; not a substitute for jurisdiction-specific legal review or attorney judgment.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Contract Review Playbook

Provides a structured contract review workflow covering parties, obligations, risk allocation, remedies, and negotiation notes.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Contract metadata capture
- Key obligation map
- Risk clause checklist
- Fallback position notes
- Executive summary template

## Trigger Keywords

contract review, agreement checklist, vendor contract, SaaS agreement, legal-contract-review-playbook, legal contract review playbook

## Example Prompts

- "Give me a contract review checklist for a SaaS agreement."
- "Help structure a risk summary for this vendor contract."

## Outputs

- Contract review checklist
- Issue list
- Negotiation note template
- Stakeholder summary


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Contract Review Playbook",
  "slug": "legal-contract-review-playbook",
  "version": "1.0.0",
  "description": "Provides a structured contract review workflow covering parties, obligations, risk allocation, remedies, and negotiation notes.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "contracts",
    "review",
    "commercial",
    "descriptive"
  ],
  "trigger_keywords": [
    "contract review",
    "agreement checklist",
    "vendor contract",
    "SaaS agreement",
    "legal-contract-review-playbook",
    "legal contract review playbook"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-matter-triage-framework
version: "1.0.0"
type: descriptive
language: en
---

# Legal Matter Triage Framework

## Overview

Helps legal teams triage incoming matters by urgency, risk, deadlines, forum, and required expertise. 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

- Sorting a queue of new requests
- Prioritizing legal work
- Escalating high-risk matters


## Target Users

- In-house counsel
- Law firm associates
- Legal operations 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. **Urgency/risk scoring** — provides structured prompts, checklists, and review fields for this area.
2. **Deadline and statute capture** — provides structured prompts, checklists, and review fields for this area.
3. **Practice-area routing** — provides structured prompts, checklists, and review fields for this area.
4. **Privilege/confidentiality caution points** — provides structured prompts, checklists, and review fields for this area.
5. **Next-action plan** — 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

- Matter priority matrix
- Escalation recommendations
- Initial next-step checklist

## Example Prompts

- "Triage these five incoming legal requests by urgency and risk."
- "Create a triage rubric for an in-house legal helpdesk."

## 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 decide legal rights or deadlines; users must verify all dates and legal requirements with qualified counsel.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Matter Triage Framework

Helps legal teams triage incoming matters by urgency, risk, deadlines, forum, and required expertise.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Urgency/risk scoring
- Deadline and statute capture
- Practice-area routing
- Privilege/confidentiality caution points
- Next-action plan

## Trigger Keywords

matter triage, legal request prioritization, legal helpdesk, risk scoring, legal-matter-triage-framework, legal matter triage framework

## Example Prompts

- "Triage these five incoming legal requests by urgency and risk."
- "Create a triage rubric for an in-house legal helpdesk."

## Outputs

- Matter priority matrix
- Escalation recommendations
- Initial next-step checklist


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Matter Triage Framework",
  "slug": "legal-matter-triage-framework",
  "version": "1.0.0",
  "description": "Helps legal teams triage incoming matters by urgency, risk, deadlines, forum, and required expertise.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "triage",
    "legal-ops",
    "risk",
    "descriptive"
  ],
  "trigger_keywords": [
    "matter triage",
    "legal request prioritization",
    "legal helpdesk",
    "risk scoring",
    "legal-matter-triage-framework",
    "legal matter triage framework"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}

---
slug: legal-client-intake-interview-builder
version: "1.0.0"
type: descriptive
language: en
---

# Legal Client Intake Interview Builder

## Overview

Builds structured intake interview plans for law firm consultations and new matter opening. 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 for a first client consultation
- Opening a new legal matter
- Standardizing intake questions across practice groups


## Target Users

- Attorneys
- Paralegals
- Legal intake teams
- Law firm operations managers


## 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. **Conflict and identity information checklist** — provides structured prompts, checklists, and review fields for this area.
2. **Matter background question tree** — provides structured prompts, checklists, and review fields for this area.
3. **Urgency and deadline capture** — provides structured prompts, checklists, and review fields for this area.
4. **Document request list** — provides structured prompts, checklists, and review fields for this area.
5. **Red-flag escalation prompts** — 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

- Intake interview agenda
- Question checklist
- Document request list
- Risk and deadline notes

## Example Prompts

- "Create an intake interview plan for a small business contract dispute."
- "Help me structure first-call questions for a potential employment termination matter."

## 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: Informational workflow support only; does not provide legal advice or determine whether representation should be accepted.

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

FILE:ACCEPTANCE.md
# Acceptance Criteria

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

## Package Rules

- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.
- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.
- The package must remain descriptive-only and English-first.

FILE:README.md
# Legal Client Intake Interview Builder

Builds structured intake interview plans for law firm consultations and new matter opening.

## What This Skill Does

This document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.

## Core Modules

- Conflict and identity information checklist
- Matter background question tree
- Urgency and deadline capture
- Document request list
- Red-flag escalation prompts

## Trigger Keywords

legal intake, client interview, new matter intake, law firm intake, legal-client-intake-interview-builder, legal client intake interview builder

## Example Prompts

- "Create an intake interview plan for a small business contract dispute."
- "Help me structure first-call questions for a potential employment termination matter."

## Outputs

- Intake interview agenda
- Question checklist
- Document request list
- Risk and deadline notes


## Safety

Informational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.

FILE:skill.json
{
  "name": "Legal Client Intake Interview Builder",
  "slug": "legal-client-intake-interview-builder",
  "version": "1.0.0",
  "description": "Builds structured intake interview plans for law firm consultations and new matter opening.",
  "author": "Pearl Team (OpenClaw)",
  "tags": [
    "legal",
    "law-firm",
    "intake",
    "client-service",
    "descriptive"
  ],
  "trigger_keywords": [
    "legal intake",
    "client interview",
    "new matter intake",
    "law firm intake",
    "legal-client-intake-interview-builder",
    "legal client intake interview builder"
  ],
  "language": "en",
  "outputs": "markdown",
  "requires_api": false,
  "readiness": "stable",
  "type": "descriptive",
  "legal_disclaimer": "Informational workflow support only; not legal advice."
}