permit

Define and evaluate type-safe policy rules for resource access.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zap-studio/skills --skill permit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: permit
Source: https://github.com/zap-studio/skills/tree/main/permit
Command: npx skills add https://github.com/zap-studio/skills --skill permit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Policies and permissions are often manually implemented, leading to inconsistencies and auditing gaps. This skill provides type-safe, declarative authorization policies for resources and actions, enabling consistent access control.

Core Features & Use Cases

  • Define and evaluate policy rules (allow/deny/when) for resources and actions.
  • Model role hierarchies and composable access rules with auditable policy definitions.
  • Replace ad-hoc checks with centralized, auditable policy logic to improve security and maintainability.

Quick Start

Define your first policy with createPolicy and test it against a user context to grant or deny access.

Frequently Asked Questions about permit

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

FAQPage Schema
How do I implement type-safe access control policies for resources?

Type-safe access control policies are implemented by defining declarative rules for resources and actions. You use createPolicy to establish allow, deny, or when conditions, replacing ad-hoc checks with centralized, auditable policy logic for consistent security.

What is the best way to model role hierarchies and permissions in a multi-tenant application?

Modeling role hierarchies in multi-tenant applications is done using composable policy rules. By defining RBAC and ABAC scenarios with declarative policies, you evaluate user context against actions and resource names to grant or deny access consistently.

How does rule composition work for authorization policies?

Rule composition for authorization policies works by combining rules with and, or, and not operators. This allows you to build complex, composable access logic that evaluates a defined policy against a specific context, action, and resourceName.

Can I replace ad-hoc permission checks with centralized authorization logic?

Yes, you can replace ad-hoc permission checks with centralized authorization logic. Defining declarative, type-safe policies ensures consistent access control across your application, improving security and maintainability while eliminating auditing gaps.

How do I evaluate a policy against a user context to grant or deny access?

Evaluating a policy against a user context involves testing the defined rules with the specific context, action, and resourceName. The policy evaluation returns an allow or deny decision, enabling you to enforce access control dynamically.