mcpbeat Sign in

Decision Ownership Audit Ignacio Adrian Lerer Agent Skill

Audits AI-assisted legal, compliance, governance, and institutional decisions before reliance to determine whether the responsible human or institution has enough access to the evidence, reasoning basis, uncertainty, authority, and review path to genuinely own the decision rather than merely approve, sign, or transmit it.

2k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
616
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill decision-ownership-audit-ignacio-adrian-lerer

What comes with it

323 bytes besides the instruction
README.md

The instruction itself

14 sections, as written by the author

Decision Ownership Audit

What This Skill Does

This skill audits whether a person or institution can responsibly rely on an AI-assisted legal or governance output before approving, signing, filing, sending, enforcing, or otherwise acting on it.

It does not ask only whether the output is correct, plausible, well written, or formally reviewed. It asks whether the responsible actor has enough access to the basis of the decision to stand behind it as a professional or institutional judgment.

Use it for legal memos, litigation strategy, contract review, compliance decisions, regulatory responses, board materials, risk approvals, due diligence conclusions, policy determinations, and other outputs that may move from analysis into reliance.

Core Question

Can the responsible human or institution genuinely own this decision, or are they merely ratifying an output whose basis they cannot inspect, contest, or correct?

Audit Protocol

1. Responsible Actor Identification

Identify who is expected to own the decision.

Classify the actor as:

  • lawyer or legal team;
  • client or business decision-maker;
  • compliance officer;
  • board, committee, or management body;
  • public authority or institutional officer;
  • automated or semi-automated workflow with a named human sponsor.

If no responsible actor is identifiable, the output is not ready for reliance.

2. Decision Surface

State what the actor is being asked to do with the output:

  • read only;
  • use as background;
  • rely on for professional analysis;
  • recommend a course of action;
  • approve, sign, file, send, or enforce;
  • execute through an automated system;
  • affect third-party rights, duties, assets, deadlines, or legal position.

Higher-consequence uses require stronger ownership conditions.

3. Evidence Access

Check whether the actor can inspect the evidence supporting each material conclusion.

The output should expose:

  • source documents or legal authorities;
  • relevant clauses, facts, sections, pages, or records;
  • missing evidence;
  • conflicting evidence;
  • source reliability or currency concerns;
  • whether a conclusion is based on the document, external law, inference, professional judgment, or policy.

If the evidence cannot be inspected, mark the decision as ownership-deficient.

4. Reasoning Access

Check whether the actor can reconstruct the reasoning path at the level required for the decision.

The output should show:

  • the legal or operational issue;
  • the rule, standard, mandate, or criterion applied;
  • the material facts used;
  • the inference from facts to conclusion;
  • alternatives considered;
  • why rejected alternatives were rejected;
  • the limits of the analysis.

Do not treat a post-hoc explanation, summary, confidence score, or fluent conclusion as sufficient by itself.

5. Uncertainty Visibility

Identify uncertainty that affects ownership:

  • contested legal interpretation;
  • missing facts;
  • stale or unverified legal authority;
  • ambiguous document language;
  • dependency on assumptions;
  • jurisdictional mismatch;
  • unresolved factual or evidentiary conflict;
  • model, retrieval, or tool limitations.

Uncertainty must be visible enough to influence the decision before reliance occurs.

6. Authority and Competence

Check whether the actor has authority and competence for the specific decision.

Ask:

  • Does the actor have mandate, role, or delegation to make this decision?
  • Does the mandate cover this matter, jurisdiction, client, entity, or transaction?
  • Has the mandate expired, been limited, or been superseded?
  • Does the actor need specialist review?
  • Does the decision require client, board, court, regulator, partner, or supervisor approval?

Formal responsibility is not enough if the actor lacks authority or practical competence.

7. Contestability and Correction

Check whether the actor can challenge and correct the output before action.

The workflow should allow:

  • requesting source support;
  • correcting facts;
  • changing assumptions;
  • escalating uncertain issues;
  • rejecting unsupported conclusions;
  • preserving an audit trail of material changes.

If the workflow allows only accept/send/execute, ownership is weak.

Verdicts

Use one of these states:

  • PASS: the responsible actor can inspect evidence, reasoning, uncertainty, authority, and review path before reliance.
  • REVIEW: minor gaps exist, but the output is not yet being used for consequential action.
  • ESCALATE: specialist, supervisory, client, institutional, or procedural review is required before reliance.
  • BLOCK: the output is being used for consequential action while the responsible actor cannot inspect or contest its material basis.

Output Format

## Decision Ownership Audit

Verdict: PASS | REVIEW | ESCALATE | BLOCK

### Responsible Actor
| Actor | Expected role | Decision surface | Status |
|---|---|---|---|

### Ownership Conditions
| Condition | Finding | Status |
|---|---|---|
| Evidence access |  |  |
| Reasoning access |  |  |
| Uncertainty visibility |  |  |
| Authority and competence |  |  |
| Contestability and correction |  |  |

### Ownership Gaps
| Gap | Why it matters | Required fix |
|---|---|---|

### Reliance State
- What can be relied on now:
- What cannot be relied on yet:
- What must be reviewed or escalated:

### Required Next Step

Non-Negotiable Rules

  • Do not equate signature, approval, or human review with genuine decision ownership.
  • Do not treat fluency, confidence, or a polished explanation as evidence of ownership.
  • Do not allow consequential reliance when evidence, reasoning, authority, or uncertainty is inaccessible.
  • If the responsible actor cannot inspect and contest the material basis, say so directly.
  • The goal is not to eliminate AI assistance; it is to prevent formal accountability without substantive ownership.

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take lawve-ai/decision-ownership-audit-ignacio-adrian-lerer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.