lawve-ai/awesome-legal-skills/agentic-delegation-audit-adrian-lerer
Claude Code and agent skill by lawve-ai/awesome-legal-skills
- community
Checking that the SKILL.md file is still in the repository.
Use when a lawyer, legal team, or client needs to assess AI agents that can act on someone's behalf: send messages, search, draft, file, pay, delete, connect to accounts, use tools, or rely on external data. Produces a practical delegation, oversight, accountability, and control audit for legal operations.
Install
npx vskill@latest install lawve-ai/awesome-legal-skills/agentic-delegation-audit-adrian-lererSKILL.md
The same SKILL.md was published earlier as lawve-ai/awesome-legal-skills/agentic-delegation-audit-adrian-lerer.
Lawve Agentic Delegation Audit
Use this skill to help lawyers evaluate whether an AI agent workflow is safe enough to use in legal or business operations.
Core idea:
Use When
- A client wants to use an AI agent for legal, compliance, business, or administrative work.
- A product, law firm, or legal ops team is connecting an agent to email, files, CRM, court portals, payments, messaging, calendars, databases, browser tools, or code execution.
- A lawyer needs to explain the risks of agentic AI in practical governance terms.
- A workflow may send, file, delete, approve, purchase, publish, sign, deploy, or change access.
- A system claims to be "autonomous", "agentic", "assistant with tools", "AI employee", "legal copilot", or "workflow agent".
Do Not Use For
- Pure doctrinal legal research with no agentic action.
- Final legal opinions without jurisdiction-specific legal review.
- Technical implementation of an agent runtime.
- Approving production use of an agent without evidence, logs, and controls.
Intake
Collect only what is necessary:
- What task does the agent perform?
- Who is the human principal?
- Who deploys or operates the agent?
- What systems, accounts, files, channels, or tools can it access?
- What actions can it take without step-by-step approval?
- Which actions are irreversible, external, financial, legal, confidential, or reputation-sensitive?
- What logs exist and who can read them?
- How can the user pause, revoke, appeal, or correct the agent?
- What data can influence the agent, including emails, webpages, chats, files, tickets, and prompts?
Audit Steps
- Classify the autonomy level
answer_only: produces information only.draft_only: drafts but does not send or change records.approval_gated_actor: acts only after explicit approval.policy_bounded_actor: acts within predefined limits.long_running_actor: continues across time, sessions, or triggers.
- Map delegated authority
- Name the principal.
- Name the deployer/operator.
- List what authority the agent has.
- Separate read, draft, internal write, external write, financial, legal-sensitive, and privileged actions.
- Check observability
- Can the user see what the agent did?
- Are tool calls and external actions logged?
- Are logs understandable by a non-developer?
- Are source data and model inference separated?
- Check control and revocation
- Can the user pause the agent?
- Can permissions be narrowed?
- Can access be revoked quickly?
- Are irreversible actions previewed before execution?
- Check accountability
- Who is responsible if harm occurs?
- Is responsibility split across vendor, deployer, user, professional, and client?
- Is there a human review point before legal reliance or external action?
- Check attack surface
- Can untrusted content influence the agent?
- Does the agent process emails, webpages, chats, documents, tickets, or social posts as instructions?
- Are external content and system instructions separated?
- Are prompt injection, data exfiltration, and tool misuse considered?
- Apply legal uncertainty gate
- Use
PASS,ESCALATE, orBLOCKfor downstream legal/business reliance. - Do not hide material uncertainty in disclaimer text.
Output
Use this compact format:
Decision Rules
PASS: agent is draft-only or tightly approval-gated, logs are clear, permissions are scoped, and no material legal/client risk remains unmanaged.NEEDS CONTROLS: agent may be useful, but missing controls prevent safe operational reliance.BLOCK: agent can perform external, legal, financial, confidential, destructive, or privileged actions without adequate approval, logging, revocation, or accountability.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/agentic-delegation-audit-adrian-lerer/SKILL.md
Popularity
- Repository stars
- 689
- Repository forks
- 88
- 7-day trend score
- 33
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/lawve-ai/awesome-legal-skills/agentic-delegation-audit-adrian-lerer)