Write a clear, factual witness statement or account of an incident — for an insurance claim, small claims, a workplace matter, or the police — that sticks to what you saw and holds up. Use when asked to write a witness statement, an account of what happened, a statement for [insurance/court/HR], or document an incident I witnessed. Produces a structured, chronological statement of facts (who, what, when, where), a clean separation of observation from opinion, the details that matter, and form...
Scanned 9/3/2026
Install to Claude Code
npx -y skills add mohitagw15856/pm-claude-skills --skill witness-statement-writer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Witness Statement Writer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mohitagw15856-witness-statement-writer)More formats (shields.io, HTML) on the badges page.
---
name: witness-statement-writer
description: "Write a clear, factual witness statement or account of an incident — for an insurance claim, small claims, a workplace matter, or the police — that sticks to what you saw and holds up. Use when asked to write a witness statement, an account of what happened, a statement for [insurance/court/HR], or document an incident I witnessed. Produces a structured, chronological statement of facts (who, what, when, where), a clean separation of observation from opinion, the details that matter, and formatting/sign-off basics — flagging that for legal proceedings you should follow the required format. Not legal advice."
homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/witness-statement-writer.html
metadata:
{
"openclaw": { "emoji": "⚖️" }
}
---
# Witness Statement Writer
A good witness statement is boring on purpose: a clear, chronological account of exactly what you observed, with facts kept separate from opinions and assumptions. That's what makes it credible and useful — for an insurance claim, a small-claims case, an HR matter, or the police. This helps you write one that's complete, factual, and hard to pick apart.
## What This Skill Produces
- **A structured statement** — your details, then a chronological account of what happened (who, what, when, where, how)
- **Facts vs. opinion, separated** — what you directly saw/heard, clearly distinguished from what you inferred or were told
- **The details that matter** — times, sequence, positions, conditions, exact words if quoted, and what you did/didn't see
- **Formatting & sign-off** — a clean, dated, signed format, with a note to follow any required official template
- **A scope flag** — for court/legal proceedings, use the prescribed format and consider legal guidance; not legal advice
## Required Inputs
Ask for these if not provided:
- **The purpose** — insurance claim, small claims/court, workplace/HR, police, or personal record
- **What happened** — the incident, in as much detail as you can recall
- **Your vantage** — what you personally saw/heard vs. what you were told or assumed
- **The specifics** — date, time, location, people involved, conditions
- **Any required format** — a template the recipient asked for
## Framework: Only What You Saw, In Order
1. **Anchor the facts.** Open with your identity and role, then the date, time, and place — the frame for everything.
2. **Tell it chronologically.** A clear sequence of what happened, step by step, is far more credible than a jumbled or conclusion-first account.
3. **Separate observation from inference.** State what you directly perceived; clearly label anything you assumed, concluded, or heard secondhand ("I saw…" vs. "I assumed…" vs. "X told me…").
4. **Be precise and honest about gaps.** Include the details that matter and say plainly what you *didn't* see or can't recall — guessing destroys credibility.
5. **Keep it neutral.** Factual and measured, no editorializing or emotion; the facts carry it.
6. **Format and sign properly.** Date and sign it; for legal use, follow the required template and note where formal wording may be needed.
## Output Format
### Witness statement — [purpose]
**Statement of [your name]**
- Who I am / my role: [x]. Date, time, place of incident: [x].
**What happened (in order)**
> [Chronological, factual account — what I personally saw and heard, step by step. Assumptions/second-hand info clearly labeled. Exact quotes where relevant.]
**What I did not see / cannot recall:** [honest gaps].
Signed: __________ Date: __________
> For court or legal proceedings, use the required statement format and wording (e.g. a statement of truth) and consider legal guidance. Not legal advice.
## Quality Checks
- [ ] Opens with identity, role, and the date/time/place
- [ ] Account is chronological and specific
- [ ] Clearly separates direct observation from inference/hearsay
- [ ] States honestly what wasn't seen or can't be recalled
- [ ] Neutral, factual tone — no editorializing
- [ ] Dated/signed, with a note to follow required legal formats
## Anti-Patterns
- **Leading with conclusions** instead of the observed sequence.
- **Blending assumption and hearsay** with what was actually seen.
- **Guessing** at details rather than admitting gaps.
- **Emotional or accusatory language.**
- **Ignoring a required official format** for legal use.
## Example Trigger Phrases
- "Help me write a witness statement for a car accident insurance claim."
- "I need to write an account of what I saw for small claims court."
- "Write a statement about an incident I witnessed at work."
- "Document what happened for the police."
- "How do I write a witness statement that's factual and credible?"
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!