tool-help

Create and edit portable bash tools for the .spec-lite/tools/ directory.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/abranjith/spec-lite --skill tool-help
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-help
Source: https://github.com/abranjith/spec-lite/tree/main/skills/tool-help
Command: npx skills add https://github.com/abranjith/spec-lite --skill tool-help

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of creating project-specific bash utilities by turning repeated workflow needs into discoverable, standardized tools for spec-lite.

Core Features & Use Cases

  • Tool Creation: Writes new bash scripts for validation, analysis, build, database, or deployment tasks in .spec-lite/tools/.
  • Tool Editing: Updates existing tools while preserving the mandatory header convention and shell safety rules.
  • Environment-Aware Automation: Detects OS, CLI availability, package managers, and project structure before generating scripts.
  • Use Case: A developer needs a portable script to validate a workspace and checks it into the shared tools directory so other agents can run it automatically.

Quick Start

Use the tool-help skill to create a new bash tool for the current project that validates the environment and follows the standard spec-lite header format.

Frequently Asked Questions about tool-help

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

FAQPage Schema
How do I create reusable bash scripts for project automation?

You can create reusable bash scripts for project automation by generating portable tools in the .spec-lite/tools/ directory. These scripts include mandatory headers and POSIX-safe error handling for automatic discovery by other agents.

What is the best way to build environment-aware bash tools that detect OS and package managers?

Building environment-aware bash tools involves detecting the OS, CLI availability, package managers, and project structure before generating idempotent shell scripts. This ensures your portable automation scripts run safely across different environments.

Does spec-lite tooling require non-interactive shell scripts?

Yes, spec-lite tooling requires non-interactive shell scripts with POSIX-safe error handling and idempotent execution. This standardization prevents execution blocking and allows safe auto-discovery by other skills and agents.

Can I update existing bash tools without breaking the spec-lite header convention?

You can edit existing bash tools while preserving the mandatory header convention and shell safety rules. This ensures updated scripts maintain compatibility with environment detection and auto-discovery requirements.

Why do my custom bash automation scripts fail auto-discovery in spec-lite workflows?

Custom bash automation scripts fail auto-discovery if they lack mandatory tool headers, idempotent execution, or POSIX-safe error handling. Standardizing your scripts in the .spec-lite/tools/ directory fixes this auto-discovery failure.