shimmy-generic-shim-template

Scaffold a Shimmy tool directory template for Podman-based CLI wrappers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create a new Shimmy tool directory using the repository's context-first conventions, so a CLI can be wrapped in a predictable Podman-based runtime with the right metadata, guidance, and layout.

Core Features & Use Cases

  • Tool directory scaffolding: Define the required files for a self-contained tool directory, including configuration, guide, agent skill, and versioned runtime assets.
  • Runtime wrapper conventions: Preserve Shimmy's POSIX shell, /work mount, preview mode, and SHIMMY_ environment variable patterns.
  • Repository-aligned implementation: Apply the template when adding a new command wrapper or versioned tool implementation that must fit the existing Shimmy catalog and test flow.

Quick Start

Use this skill to scaffold a new Shimmy tool directory for a CLI you want to run through Podman.

Frequently Asked Questions about shimmy-generic-shim-template

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

FAQPage Schema
How do I scaffold a containerized CLI wrapper using Podman?

You scaffold a containerized CLI wrapper by generating a tool directory template that includes configuration, guides, agent instructions, and versioned runtime assets. This structure wraps CLI utilities in predictable Podman-based shims.

What is a context-first tool directory template for CLI runtimes?

A context-first tool directory template is a structured layout for self-contained CLI wrappers. It defines the required configuration, agent skills, and versioned runtime files to ensure new tools fit the existing catalog and test flow.

Do I need POSIX shell compatibility to build Podman-based shims?

Yes, POSIX shell compatibility is required to build Podman-based shims. The runtime wrapper conventions depend on POSIX shell behavior, /work mount paths, preview mode, and SHIMMY_ environment variable patterns.

What files are required to scaffold a self-contained tool directory for command wrappers?

Scaffolding a self-contained tool directory requires configuration files, guides, agent skill definitions, and versioned runtime assets. These files preserve the /work mount, preview mode, and SHIMMY_ environment variable patterns.

When should I use a repository-aligned template for adding new command wrappers?

Use a repository-aligned template when adding a new command wrapper or versioned tool implementation that must fit the existing Shimmy catalog. It ensures the scaffolded tool directory passes the repository test flow and maintains catalog consistency.