Tool Builder

Generate CLI tool scripts from action-converter suggestions and manual tasks.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/aeoncity-demo/myaeon --skill tool-builder-aeoncity-demo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Tool Builder
Source: https://github.com/aeoncity-demo/myaeon/tree/main/skills/tool-builder
Command: npx skills add https://github.com/aeoncity-demo/myaeon --skill tool-builder-aeoncity-demo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of building CLI tools based on action-converter suggestions and recurring manual tasks, saving time and reducing errors.

Core Features & Use Cases

  • Automated Script Generation: Automatically generates scripts for CLI tools based on patterns and tasks identified by the system.
  • Reusability: Generates scripts that can be reused by multiple skills or operators.
  • Quality Gates: Ensures that all generated scripts pass quality gates before being shipped.

Quick Start

Run the Skill with the name of a specific tool to build it, or without a name to automatically select an opportunity from recent action-converter outputs and logs.

Frequently Asked Questions about Tool Builder

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

FAQPage Schema
How do I automate script generation for recurring manual CLI tasks?▼

Automate script generation for CLI tasks by processing action-converter suggestions to create small, self-contained tools. The system handles script generation, applies quality gates, and verifies outputs before shipping.

What is the best way to ensure generated CLI scripts pass quality gates before shipping?▼

Ensuring generated CLI scripts pass quality gates before shipping requires an automated builder that validates self-contained tools against predefined checks. This guarantees reusability and reduces manual errors before deployment.

Do I need bash and jq installed to build self-contained CLI tools from action-converter outputs?▼

Yes, building self-contained CLI tools from action-converter outputs requires bash, jq, gh, curl, and date installed in your execution environment to process and verify the generated scripts.

Can I generate reusable CLI scripts automatically without specifying a tool name?▼

Yes, you can generate reusable CLI scripts automatically without a specific name. Running the builder without a name automatically selects an opportunity from recent action-converter outputs and logs.

What are the limitations of generating self-contained CLI tools from recurring manual tasks?▼

Limitations of generating self-contained CLI tools include dependency on bash, jq, gh, curl, and date for execution. It primarily targets small scripts from action-converter suggestions rather than complex application architectures.