skills.rest
wadebee
wadebeeCOMMUNITY
Explore all skills by this author →
GitHub

shimmy-tool-local-build

Configure local image build routing and versioned Containerfiles for Shimmy shims.

2|Updated Feb 14, 2026
Search Tags:#podman#containerfile#cleanup automation#local build#shimmy#versioned shims
One-click install
npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-local-build
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shimmy-tool-local-build
Source: https://github.com/wadebee/shimmy/tree/main/.agents/skills/shimmy-tool-local-build
Command: npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-local-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain Shimmy tool shims that need local image builds, so new versioned tools can be added without breaking cleanup or repository naming conventions.

Core Features & Use Cases

  • Versioned shim setup: Defines how to add new kind and version entries to local build routing.
  • Containerfile enforcement: Ensures each supported version shim has a matching Containerfile in the expected images directory.
  • Image cleanup integration: Guides updates so newly added shims participate in cleanup logic for old local images.

Quick Start

Use this skill to update Shimmy so a new versioned tool shim builds locally and is included in the cleanup workflow.

Frequently Asked Questions about shimmy-tool-local-build

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

FAQPage Schema
How do I configure local image builds for versioned container shims?▼

To configure local image builds for versioned container shims, you update local build routing with new kind and version entries. This directs directory-based container construction and maintains consistent image repository naming.

Why does my new versioned shim build break the cleanup automation for old local images?▼

New versioned shim builds break cleanup automation when they are not integrated into the existing cleanup logic. You must update the cleanup automation workflow so newly added shims participate in removing old local images.

Do I need a Containerfile for every version when adding local Podman builds?▼

Yes, you need a matching Containerfile for every supported version shim. Containerfile enforcement requires each version to have a corresponding file in the expected images directory to build locally.

What is the best way to add a new versioned tool to local build routing?▼

The best way to add a new versioned tool to local build routing is to define the new kind and version entries, create the required directory-based Containerfile, and update the image cleanup integration simultaneously.

How does directory-based container construction maintain consistent image repository naming?▼

Directory-based container construction maintains consistent image repository naming by enforcing that each supported version shim has a matching Containerfile in the expected images directory, standardizing the build routing.

Related Skills

Explore More Software Engineering Skills→
openkaidenopenkaiden
10

working-with-podman-runtime-config

Generate dynamic Containerfiles and sudoers for Podman runtime configurations.

Official
Advanced
mikopbxmikopbx
569

log-analyzer

Analyze MikoPBX Docker logs to diagnose API, worker, and system issues.

Official
Intermediate
gparker97gparker97
4

deploy-prod

Commit, push, monitor CI, and deploy Vue and Astro production builds.

Community
Advanced
JylhisJylhis
1

nix-containers

Build reproducible OCI and NixOS container images with Nix.

Community
Advanced