shimmy-init

Diagnose Podman readiness failures for Shimmy-backed CLI wrappers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps recover Shimmy-backed CLI tools when they fail because the local Podman engine is unavailable, unreachable, or not ready.

Core Features & Use Cases

  • Podman readiness checks: Confirms whether a tool resolved to a Shimmy wrapper and whether Podman can be reached.
  • macOS remediation guidance: Guides the user to start an existing Podman machine from a normal shell when the engine is stopped or inaccessible.
  • Safe retry workflow: Distinguishes between engine access issues and wrapper-specific failures so the right next step can be taken.
  • Use case: A developer runs a Shimmy-installed command like jq or rg and gets connection refused or stale socket errors, then uses this Skill to diagnose Podman access and recover safely.

Quick Start

Ask the assistant to verify Podman access for the failing Shimmy-backed tool and tell you whether you need to start or inspect a Podman machine.

Frequently Asked Questions about shimmy-init

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

FAQPage Schema
Why does my Podman CLI tool fail with a connection refused error on macOS?

Podman connection refused errors occur when the local engine is stopped or unreachable. This Skill diagnoses Podman readiness for Shimmy CLI wrappers and checks if the macOS machine needs starting.

How do I fix stale socket errors when running Shimmy-wrapped commands?

Stale socket errors indicate the Podman engine is not ready. This Skill verifies the wrapper path, checks podman info, and guides you through safe remediation steps to restore engine connectivity.

Does this Skill automatically start Podman to resolve CLI execution failures?

No, this Skill does not automatically install or start Podman. It diagnoses wrapper failures and guides safe user-side remediation, directing you to start an existing Podman machine from a normal shell.

What's the best way to diagnose Podman machine state issues on macOS?

The best way to diagnose macOS Podman machine state is verifying the wrapper path and checking podman info. This Skill distinguishes between engine access issues and wrapper-specific failures to determine the correct next step.

Can I use this to troubleshoot CLI tools that are not backed by Shimmy?

No, this Skill specifically diagnoses and resolves Podman readiness failures for Shimmy-backed CLI wrappers. It confirms whether a failing tool resolved to a Shimmy wrapper before providing remediation guidance.