shimmy-tool-aws

Maintain the AWS CLI Shimmy tool with containerized runtime execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides the canonical workflow for using and maintaining the AWS CLI through Shimmy, so AWS tasks run with the expected config, credentials, and containerized runtime behavior.

Core Features & Use Cases

  • Context-first guidance: Points to the repository and tool-specific context files needed to understand the AWS setup before making changes.
  • Containerized runtime execution: Uses the defined concrete runtime so AWS commands run consistently through Podman with the correct mounts and environment forwarding.
  • Operational maintenance: Supports day-to-day work on the AWS tool directory, including validation, smoke checks, and preserving Shimmy conventions.
  • Use case: Update or troubleshoot the AWS Shimmy tool while keeping credential mounting and AWS environment propagation intact.

Quick Start

Use the AWS Shimmy skill to inspect the AWS tool context and follow its runtime instructions for safely running or updating the tool.

Frequently Asked Questions about shimmy-tool-aws

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

FAQPage Schema
How do I run AWS CLI commands in a containerized environment?

Running AWS CLI commands in a container requires a concrete runtime that executes AWS tasks through Podman, mounting AWS config files and forwarding AWS environment variables to maintain consistent operational behavior.

How do I preserve AWS credentials and config when running AWS CLI through Podman?

To preserve AWS credentials and config through Podman, you must maintain the defined runtime behavior that mounts the AWS config directory and forwards AWS environment variables during containerized command execution.

What is the best way to troubleshoot AWS CLI container runtime issues?

Troubleshooting AWS CLI container runtime issues involves inspecting tool-specific context files and following runtime instructions to perform validation and smoke checks while preserving Shimmy conventions.

Does the AWS CLI Shimmy tool support AWS environment variable forwarding?

Yes, the AWS CLI Shimmy tool supports AWS environment variable forwarding, allowing AWS_* variables to propagate through the Podman container runtime for proper authentication and configuration.

Can I update the AWS CLI tool directory without breaking the containerized workflow?

Yes, you can update the AWS CLI tool directory by following context-aware guidance that preserves the AWS config mounting, environment forwarding, and concrete runtime behavior required for the containerized workflow.