permissions-manager

Inspect provider-runtime authorization denials and apply permission profiles via the Ravi CLI.

6|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/filipexyz/ravi --skill permissions-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: permissions-manager
Source: https://github.com/filipexyz/ravi/tree/main/src/plugins/internal/ravi-system/skills/permissions
Command: npx skills add https://github.com/filipexyz/ravi --skill permissions-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves authorization denials and manages provider-runtime permissions for AI agents, preventing workflow interruptions caused by insufficient access rights.

Core Features & Use Cases

  • Permission Inspection: View active provider chains and verify current authorization decisions for specific subjects.
  • Denial Resolution: Resolve access denials by applying provider-owned profiles or tags without needing manual intervention.
  • Use Case: When an agent is blocked from executing a tool, use this skill to inspect the denial, identify the missing capability, and apply the correct permission profile to restore functionality.

Quick Start

Use the permissions manager to inspect the current authorization state for the main agent and resolve any pending denials.

Frequently Asked Questions about permissions-manager

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

FAQPage Schema
How do I resolve agent authorization denials in the Ravi ecosystem?

Resolve agent authorization denials by inspecting capability chains, materializing subject permissions, and applying provider-owned profiles to restore blocked tool execution within the Ravi ecosystem.

How do I inspect AI agent runtime permissions to identify missing capabilities?

Inspect AI agent runtime permissions by viewing active provider chains and verifying current authorization decisions for specific subjects to identify missing capabilities causing access blocks.

Why does my AI agent get blocked from executing a tool during a workflow?

Your AI agent gets blocked from executing a tool due to insufficient access rights, requiring permission updates to apply the correct provider-owned profiles or tags to restore functionality.

Can I apply permission profiles to resolve access denials without manual intervention?

You can resolve access denials automatically by applying provider-owned profiles or tags through the permissions manager, which interacts with the Ravi CLI to perform dry-run validations and persistent permission updates.

Does the Ravi CLI support dry-run validations for agent permission updates?

The Ravi CLI supports dry-run validations for agent permission updates, allowing you to test authorization changes and inspect capability chains before applying persistent access control modifications.

What is the best way to manage provider-runtime access control for AI agents?

The best way to manage provider-runtime access control for AI agents is to inspect capability chains, verify authorization decisions, and apply provider-owned profiles to prevent workflow interruptions from insufficient permissions.