shimmy-tool-textual

Maintain the Textual Shimmy tool by preserving its context-first workflow and terminal-aware local-image runtime behavior.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you use and maintain the Textual Shimmy tool without losing the repository’s context-first workflow, so terminal-aware container behavior stays consistent across edits and runs.

Core Features & Use Cases

  • Context-aware maintenance: Follows the canonical guidance files for the Textual tool directory before making changes.
  • Local-image runtime support: Preserves the expected behavior for running the tool against local images in a TTY-sensitive shell environment.
  • Version-specific coordination: Aligns the agent workflow with the tool’s versioned context so updates remain compatible with the installed Shimmy layout.
  • Use case: When adjusting the Textual tool or diagnosing its runtime behavior, this Skill keeps the relevant instructions close to the implementation files and helps avoid breaking the container-based execution path.

Quick Start

Review the linked context files for the Textual tool and then update or operate the tool while preserving its terminal-aware local-image behavior.

Frequently Asked Questions about shimmy-tool-textual

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

FAQPage Schema
How do I maintain Textual tools without breaking container context?

To maintain Textual tools without breaking container context, read the canonical context hierarchy files before making repository edits. This ensures updates remain consistent with the tool’s container-based execution model and terminal-aware behavior.

Why does my Textual tool runtime break when running local images in a TTY shell?

Your Textual tool runtime breaks because updates may have broken the TTY-sensitive shell environment. You must preserve the context-first workflow and local-image runtime behavior by aligning agent workflows with the tool's versioned context files.

Do I need to read context files before diagnosing Textual tool runtime behavior?

Yes, you need to read context files before diagnosing Textual tool runtime behavior. Reviewing the linked versioned context files ensures diagnostic adjustments preserve the expected terminal-aware local-image execution path.

Can I use POSIX shell to run Textual tools against local images?

Yes, you can use POSIX shell to run Textual tools against local images. The Shimmy tool preserves a TTY-sensitive shell environment to maintain reliable container-based execution behavior across runs.

What is the best way to update a Textual tool directory while preserving its execution model?

The best way to update a Textual tool directory while preserving its execution model is following the canonical guidance files. This coordinates version-specific updates with the installed Shimmy layout to avoid breaking the container execution path.

What are the limitations of editing a Textual tool without versioned context coordination?

Editing a Textual tool without versioned context coordination risks breaking the container-based execution path. Updates bypassing the canonical context hierarchy will fail to preserve the terminal-aware local-image runtime behavior.