shimmy-tool-task

Maintain Shimmy Task tool workflows with context-first operational guidance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you use and maintain the Shimmy Task tool without manually tracing the repository layout, version metadata, or container-runtime conventions.

Core Features & Use Cases

  • Context-first workflow: Follows the linked repository context files so Task behavior stays aligned with the canonical source tree.
  • Version-aware maintenance: Works with the Task tool’s versioned runtime and preserves the expected local-image and host-mount behavior.
  • Operational support: Useful when updating task execution details, verifying mounts, or keeping nested Podman access consistent across changes.

Quick Start

Use the Task Shimmy skill to read the linked context files and update the Task tool workflow while preserving its documented mounts and runtime behavior.

Frequently Asked Questions about shimmy-tool-task

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

FAQPage Schema
How do I maintain Task tool versioned runtime behavior with Podman?

Maintain the Task tool versioned runtime by following context-first workflows that preserve documented local-image builds and host-path mounts. This ensures consistent Podman access across repository updates.

What is a context-first workflow for Task tool maintenance?

A context-first workflow reads linked repository context files to keep Task tool behavior aligned with the canonical source tree, preventing manual tracing of repository layout and version metadata.

Can I update task execution details without breaking host-path mounts?

Yes, you can update task execution details while preserving documented integration mounts. Keep canonical context files intact to ensure host-path mounts remain consistent across changes.

Does the Task tool support nested Podman access scenarios?

Yes, the Task tool supports nested Podman access scenarios. Preserve documented container-runtime conventions and canonical context files to keep nested access working consistently.

What's the best way to verify local-image builds in a Task workflow?

Verify local-image builds by following linked context files that document versioned runtime behavior and host-mount conventions. This keeps builds aligned with the canonical source tree.

Why do my Task tool mounts break after updating repository context?

Mounts break when canonical context files are altered or removed during updates. Preserve documented integration mounts and repository context files to maintain consistent host-path behavior.