ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

relativity-deposition-question-builder

Develop deposition question sets from Relativity-exported PDF productions using a user-provided legal theory. Use when tasks involve reviewing opponent-produced PDFs, extracting per-page document IDs from the bottom-right corner (if two numbers appear, use the smaller one), mapping document relevance to a legal theory, and drafting questions grouped by document ID with required rationale and supporting quotes.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/chipmunkrpa/deposition-question-skill
Or

Relativity Deposition Question Builder

Overview

Analyze one or more Relativity-exported PDF productions against a legal theory and generate deposition questions organized by document ID. Each question includes a reason for asking and a document quote that can be used if the witness denies.

Required Behavior

  • Ask for the legal theory first before producing analysis or questions.
  • Ask for PDF path(s) if not already provided.
  • Extract page-level document IDs from the bottom-right area of each page.
  • If two numeric IDs appear in that area, choose the smaller number as the page document ID.
  • Keep quotes verbatim and include source file plus page number for each quote.
  • Group outputs by document ID and place each question under its document ID heading.
  • Under every question, include:
    • Reason why we ask this question
    • Quote from the document to use in deposition in case the opponent party denies

Workflow

  1. Gather inputs.
    • Confirm the user's legal theory.
    • Confirm PDF source path(s).
    • Optionally gather witness name/role and priority topics.
  2. Extract per-page text and document IDs.
    • Run:
      python scripts/extract_relativity_pages.py \
        --input <pdf-folder-or-file> \
        --recurse \
        --output <relativity_pages.json>
      
    • Review pages where selected_document_id is null and flag for manual check.
  3. Build a relevance map for the legal theory.
    • For each page, classify relation to theory: supports, undermines, neutral.
    • Focus question drafting on supports pages first, then undermines pages for impeachment.
  4. Draft deposition questions grouped by document ID.
    • Use short, concrete, single-issue questions.
    • Start with authentication/foundation, then admission and contradiction questions.
    • Use direct quotes from page text for denial follow-up.
  5. Return output in required structure.
    • Follow references/deposition_output_template.md.
    • Keep document IDs in ascending numeric order.

Output Rules

  • Do not merge different document IDs into one section.
  • Do not omit Reason or Quote sections under any question.
  • If no reliable quote exists, mark:
    • Quote from the document to use in deposition in case the opponent party denies: [No direct quote located - manual verification required]
  • Prefer quotes that are short, specific, and tied to one factual proposition.

Resources

  • Extraction tool: scripts/extract_relativity_pages.py
  • Output template: references/deposition_output_template.md

Dependencies

Install once if missing:

python -m pip install --user pdfplumber

Metadata

Stars3683
Views0
Updated2026-04-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-chipmunkrpa-deposition-question-skill": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.

Related Skills

redline

Review and redline DOCX contracts paragraph by paragraph with tracked changes, clause-level risk analysis, and draft comment responses. Use when a user wants contract revisions that are specific to each paragraph or bullet, especially for privacy, security, data-processing, liability, AI, or other negotiated legal terms.

chipmunkrpa 3683

accounting-finance-system-research

Research and solve "how do I do this?" questions inside accounting and finance software systems (ERP, GL, AP/AR, billing, close, and reporting tools). Use when a user needs operational steps, setup guidance, or troubleshooting help in a specific system and wants the result documented as a quick memo or simple Q-and-A DOCX.

chipmunkrpa 3683

finresearchclaw

Finance, accounting, and investment research automation via the FinResearchClaw repo. Use when asked to run autonomous finance research workflows such as event studies, factor-model research, accounting regressions, forecast-error analysis, valuation research, or investment research pipelines. Prefer execution in this order: (1) Codex/ACP Codex when available, (2) Claude Code/ACP Claude, (3) direct API/config mode only as a fallback.

chipmunkrpa 3683

brd-reviewer

Review Business Requirements Documents in `.docx` format by reading the existing BRD, extracting paragraph-level context, drafting clarification questions for unclear statements, and producing a final Word document that combines comments and tracked changes. Use when the user wants a BRD reviewed, challenged for ambiguity, or redlined with proposed wording improvements while preserving Word-native review features.

chipmunkrpa 3683

form-1040-review

Review U.S. individual income tax returns (Form 1040/1040-SR) for the most recent tax year, compare major return items against current-year tax rules, check consistency across historical returns when multiple years are provided, generate a standalone DOCX risk register, and estimate audit likelihood from return content. Use when tasks involve 1040 compliance review, multi-year consistency analysis, tax-law validation, or audit-risk assessment.

chipmunkrpa 3683