Agent skill · Security

ai-audit-trail-larissa-meredith-flister

This skill builds a structured audit trail of an AI-assisted task: what the tool was asked to do, what materials it was given, what it produced, how the output was verified, and what was ultimately relied upon. It documents the workflow for supervision and later review without ruling on privilege or disclosure, so the record stays accurate rather than self-serving.

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill ai-audit-trail-larissa-meredith-flister --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 10 KB
Bundled scripts: none
Version: 2026-06-11
Declared author: Larissa Meredith-Flister
Path: skills/ai-audit-trail-larissa-meredith-flister/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# AI Audit Trail Builder ## Purpose A great deal of AI-assisted legal work leaves almost no record. The prompts are gone, the discarded drafts are gone, and there is no written trace of what was checked. That absence can become a problem later — under supervision review, in a regulatory enquiry, or where the provenance of a document is challenged in disclosure. This skill helps a lawyer create a careful, accurate record of an AI-assisted workflow so that what was done can be reconstructed and defended. The purpose is **not** to justify the use of AI. The purpose is to document it honestly: what was done, what materials were used, how the output was checked, and what was relied upon. You are acting as an experienced solicitor helping a legal team build this record. Be precise, cautious, and practical. Do not invent facts. Where information is missing, ask for it or flag it clearly rather than filling the gap. ## When the user has not given you enough If the user has not provided enough to build a meaningful trail, do not guess. Open by asking for what you need, using this checklist: 1. What legal task was the AI tool used for? 2. Which AI tool/model was used? 3. What prompts were en

What's inside
Steps it walks through
  1. Purpose
  2. When the user has not given you enough
  3. Output structure
  4. 1. Task summary
  5. 2. AI tool used
  6. 3. Materials provided to the AI tool
  7. 4. Prompts and instructions used
  8. 5. AI outputs generated
  9. 6. Human review and verification
  10. 7. Reliance and use
  11. 8. Risk flags
  12. 9. Missing information
  13. 10. Recommended audit trail record
  14. 11. Retention recommendation
Ships with 2 files
  • README.md
  • evals/evals.json
More from awesome-legal-skills
All skills →
About this skill
What does the ai-audit-trail-larissa-meredith-flister skill do?

This skill builds a structured audit trail of an AI-assisted task: what the tool was asked to do, what materials it was given, what it produced, how the output was verified, and what was ultimately relied upon. It documents the workflow for supervision and later review without ruling on privilege or disclosure, so the record stays accurate rather than self-serving.

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill ai-audit-trail-larissa-meredith-flister --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going