Agent skill · Security

runtime-admissibility-review

Determines whether a specific AI-agent action, output, recommendation, or proposed commitment remains admissible for execution or institutional reliance under current authority, delegated scope, evidence, facts, policy, risk, escalation, and revocation conditions. Use this Skill before an enterprise or regulated AI agent executes, updates records, triggers workflows, communicates externally, or before an institution relies on an agentic output in a way that creates consequence.

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill runtime-admissibility-review-arkadiy-miteiko --agent claude-code

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

Facts
Files in the skill folder: 8
SKILL.md size: 40 KB
Bundled scripts: none
Path: skills/runtime-admissibility-review-arkadiy-miteiko/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.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Determines whether a specific AI-agent action, output, recommendation, or proposed commitment remains admissible for execution or institutional reliance under current authority, delegated scope, evidence, facts, policy, risk, escalation, and revocation conditions.

How it works

The Skill guides checking against a defined authority envelope and current state: compares the proposed action or reliance against the Agent Authority Charter and Agentic Delegation Audit inputs, then evaluates current facts, evidence, policy, risk, escalation, and revocation status to produce a structured Runtime Admissibility Determination intended for review by legal, compliance, risk, audit, and governance stakeholders. If artifacts like the Agent Authority Charter or Delegation Audit are available, use them as primary inputs; otherwise, proceed with provided context.

When to use it

Use this Skill before an enterprise or regulated AI agent executes, updates records, triggers workflows, communicates externally, or before an institution relies on an agentic output in a way that creates consequence. It applies when reviewing whether an AI agent may take a specific action or whether an institution may rely on a specific output, given current facts, authority, and conditions.

What it can touch

The Skill references inputs such as: Proposed Action, Agent Identity, Authority Source, Scope, Current Facts, Evidence Available, Human Approval Status, Escalation History, Revocation or Suspension Status, and Reliance / Consequence Context. It requires access to those inputs to generate the determination.

Caveats

Do not provide legal advice or a legal opinion. If the user asks for a final legal conclusion, state that the output is a governance drafting aid and must be reviewed by qualified counsel and the appropriate institutional authority. If authority sources are missing or unclear, mark the action as not admissible or requiring escalation, depending on severity.

From the SKILL.md

# Runtime Admissibility Review ## Purpose This Skill helps legal, compliance, risk, product, operations, audit, and AI governance teams determine whether a specific AI-agent action, output, recommendation, or proposed commitment remains admissible at runtime before execution or before institutional reliance. The purpose is not to decide whether an AI system was generally approved for deployment. The purpose is narrower and more operational: Determine whether this agent may take this specific action, or whether the institution may rely on this specific agentic output, under these current facts, with this authority, this delegated scope, this evidence, these constraints, this escalation posture, and this revocation status. The Skill produces a structured Runtime Admissibility Determination that can be reviewed by legal, compliance, risk, audit, technical, and business stakeholders. ## Core Principle Static authorization is not enough for agentic AI. An AI agent may have been approved for a workflow, and a delegated task may initially fit within the authority envelope, but a specific action or later institutional reliance can become inadmissible because conditions changed. Examples: -

What's inside
Steps it walks through
  1. Purpose
  2. Core Principle
  3. Relationship to Agent Authority Charter and Agentic Delegation Audit
  4. Key Distinction
  5. Execution and Reliance Boundary
  6. When to Use This Skill
  7. When Not to Use This Skill
  8. Definitions
  9. Agent
  10. Proposed Action
  11. Standing Authority
  12. Runtime Admissibility
  13. Institutional Reliance
  14. Reliance Context
Ships with 7 files
  • README.md
  • demo/01_demo_agent_authority_charter_excerpt.md
  • demo/02_demo_proposed_runtime_action_record.md
  • demo/03_demo_policy_and_threshold_excerpt.md
  • demo/04_demo_current_state_evidence_log.md
  • demo/05_demo_risk_and_escalation_notes.md
  • demo/README.md
More from awesome-legal-skills
All skills →
About this skill
What does the runtime-admissibility-review skill do?

Determines whether a specific AI-agent action, output, recommendation, or proposed commitment remains admissible for execution or institutional reliance under current authority, delegated scope, evidence, facts, policy, risk, escalation, and revocation conditions. Use this Skill before an enterprise or regulated AI agent executes, updates records, triggers workflows, communicates externally, or before an institution relies on an agentic output in a way that creates consequence.

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill runtime-admissibility-review-arkadiy-miteiko --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