tools

Generate CLI tool code and documentation under docs/tools within plan-exec-loop workflows.

Updated May 2, 2026
One-click install
npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill tools-tacuchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tools
Source: https://github.com/Tacuchi/agent-workflow-cli/tree/main/skills/w/roles/tools
Command: npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill tools-tacuchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Tools authoring capability automates the creation of tooling utilities and their documentation within a plan-driven workflow, reducing manual setup and ensuring consistent structure.

Core Features & Use Cases

  • Structured tool skeletons: code and docs produced under docs/tools/ as part of plan-exec-loop tasks.
  • Tooling templates: quick generation of CLIs, helpers, and automation scripts with reusable configurations.
  • Use Case: When a plan task needs a new automation utility, generate the tool code and its docs in a consistent layout, ready for deployment.

Quick Start

Invoke a plan task to generate a new tool (CLI or helper) and automatically create its code alongside documentation under docs/tools/.

Frequently Asked Questions about tools

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

FAQPage Schema
How do I automate CLI creation and generate documentation in a consistent layout?

CLI creation and documentation are automated by generating a structured tool skeleton, placing reusable code and docs under docs/tools/ to ensure consistent layout during plan executions.

What is the best way to generate automation scripts within a plan-driven workflow?

Generating automation scripts within a plan-driven workflow is best handled by applying tooling templates that produce reusable configurations and helper code alongside their documentation automatically.

Can I use this tooling workflow to create reusable configurations for new utilities?

Yes, you can create reusable configurations for new utilities by invoking a plan task that generates a structured tool skeleton with consistent code and documentation output.

Does this automation approach place tool code and docs in a specific workspace location?

This automation approach enforces a consistent workspace location by placing all generated tool code and its accompanying documentation under the docs/tools/ directory.

Why do I need a structured tool skeleton for generating automation utilities?

A structured tool skeleton is needed for generating automation utilities because it reduces manual setup, enforces a consistent layout, and integrates generated code directly with the workspace's skills system.

When should I not use automated tooling templates for creating helpers and CLIs?

Automated tooling templates should not be used for creating helpers or CLIs when a plan task does not require a new automation utility or when custom code placement outside docs/tools/ is needed.