policy-engine

Evaluate authorization, risk, and compliance policies to produce allow, deny, or approval-gated decisions.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill policy-engine-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: policy-engine
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/policy-engine
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill policy-engine-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need a consistent, auditable way to decide whether a proposed action is allowed, denied, or requires approval before it executes. This Skill evaluates centralized authorization, risk, compliance, escalation, and approval policies against a proposed action and produces a deterministic decision with a full rule trace, without ever executing the governed action itself. ## Core Features & Use Cases - Deterministic Policy Decisions: Parses request context into decision attributes and evaluates authorization rules, risk and compliance constraints, then escalation and approval requirements in a fixed order. - Traceable Outputs: Emits a decision report in JSON and Markdown plus an append-only decision log, including ordered rule traces, rationale, required controls, and provenance. - Fail-Closed Behavior: Blocks or denies when policy context or decision attributes are incomplete, never producing an implicit allow. - Use Case: Before a production deployment or destructive migration, submit the action request with actor, target, scope, and mutation level to receive a deny or require-approval decision with the exact controls and approvals needed. ## Quick Start Ask the agent to evaluate whether a proposed production deployment by a specific actor is allowed, denied, or requires security approval under the repository's policy set.

Frequently Asked Questions about policy-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether an action is allowed by policy before executing it?

Submit the proposed action with actor, target, scope, and intended mutation level along with the applicable policy set. The Skill evaluates authorization, risk, compliance, and approval rules in order and returns an allow, deny, or require-approval decision with a full rule trace.

What outputs does a policy evaluation produce?

Each evaluation writes a JSON report, a Markdown report, and an append-only JSONL decision log. These artifacts include the decision, ordered rule trace, rationale, required controls, and decision provenance.

Does the policy engine execute the action it approves?

No. The Skill only evaluates policies and records decisions; it never executes the governed action. Policy decisions also never substitute for explicit user approval.

What happens when policy context or input attributes are incomplete?

The Skill fails closed: it emits a blocked or deny decision with the unresolved input requirements listed. It never produces an implicit allow when the policy set or decision attributes are missing.

When should I not use a policy evaluation skill?

Do not use it to perform the governed action itself or to rewrite accepted event-stream records. It is a read-only decision layer, so use execution or deployment tooling for the actual mutation after approval.