shimmy-escalation

Request narrow approval for Shimmy wrapper commands invoking Podman.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/wadebee/shimmy --skill shimmy-escalation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shimmy-escalation
Source: https://github.com/wadebee/shimmy/tree/main/plugins/shimmy/skills/shimmy-escalation
Command: npx skills add https://github.com/wadebee/shimmy --skill shimmy-escalation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you request the narrowest possible approval when a Shimmy wrapper is blocked by sandboxing or when direct Podman access works but the exact wrapper command still needs permission.

Core Features & Use Cases

  • Wrapper-aware approvals: Targets the outer command that actually runs, rather than over-approving unrelated Podman actions.
  • Minimal-risk smoke testing: Recommends harmless checks like version or help commands for installed shims and source validation.
  • Profile-aware workflow: Keeps upstream profile testing and repository preflight checks aligned with Shimmy’s activation and runtime model.
  • Use Case: You want to verify jq through Shimmy, but the wrapper is blocked; this Skill guides you to request approval for the exact wrapper smoke command instead of broad engine access.

Quick Start

Ask for the smallest harmless approval needed to run the blocked Shimmy wrapper command you are testing.

Frequently Asked Questions about shimmy-escalation

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

FAQPage Schema
How do I get sandbox approval for a blocked Podman wrapper command?

To get sandbox approval for a blocked Podman wrapper command, request narrow permission for the exact outer shell command. This preserves the original execution context while using minimal non-mutating prefixes, avoiding broad engine access.

Why does my Podman wrapper fail smoke tests when direct access works?

Podman wrapper smoke tests fail when sandboxing blocks the outer shell interface, even if direct Podman access works. Wrapper execution differs from direct access, requiring specific narrow approval for the wrapper command to run successfully.

Can I request broad Podman approval for wrapper source validation runs?

You should not request broad Podman approval for wrapper source validation runs. Instead, target the specific outer wrapper command to preserve the exact execution context and maintain profile-aware checks aligned with runtime models.

Do I need to preserve the exact outer command when requesting wrapper approval?

Yes, you need to preserve the exact outer command when requesting wrapper approval. This ensures the permission targets the actual wrapper execution path rather than over-approving unrelated Podman actions or shell interfaces.

When should I avoid broad shell approval for profile-aware wrapper checks?

You should avoid broad shell approval for profile-aware wrapper checks when direct Podman access differs from wrapper execution. Always use minimal non-mutating prefixes to maintain narrow, targeted permissions for repository preflight checks.