shimmy-tool-logmine

Guide Logmine Shimmy maintenance using canonical context files and local-image workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides the canonical instructions for using and maintaining the Logmine Shimmy tool so agents can work with the correct context-first setup without guessing at repository structure or runtime behavior.

Core Features & Use Cases

  • Context-first maintenance: Guides changes by pointing to the repository and tool-specific context files that define Logmine behavior.
  • Local-image workflow: Preserves the intended local-image build and execution flow for Logmine.
  • Minimal host integration: Ensures host mounts stay small and intentional when running the tool through Shimmy.

Quick Start

Use the Logmine Shimmy skill to follow the canonical context files and preserve local-image behavior while making changes or running the tool.

Frequently Asked Questions about shimmy-tool-logmine

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

FAQPage Schema
What is a context-first workflow for container tooling?

A context-first workflow guides repository edits and tool usage by pointing to canonical context files that define behavior, ensuring agents follow the correct local-image build and runtime setup without guessing.

How do I maintain a container tool using canonical context files?

To maintain a container tool using canonical context files, apply versioned guidance to repository edits and tool usage while strictly adhering to local-image behavior and minimal host-path mounts.

Do I need minimal host-path mounts to run tools in a container workflow?

Yes, you need minimal host-path mounts to keep host integration small and intentional, which preserves the intended local-image build and execution flow when running tools through a container manager.

Why does my local-image build break during container workflow repository edits?

Your local-image build breaks during repository edits when you deviate from canonical context files, because the context-first workflow requires strict adherence to defined local-image behavior and minimal host mounts.