Tool Builder

Generate self-contained CLI tools from action-converter outputs and recurring manual tasks.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill tool-builder-atrium-hermes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Tool Builder
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/tool-builder
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill tool-builder-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning recurring manual tasks and action-converter insights into reusable CLI tools that future Aeon runs can reuse without rework.

Core Features & Use Cases

  • Identify automation opportunities from memory logs and action-converter outputs to seed new tools.
  • Design and gate a single, self-contained CLI tool per opportunity that passes defined quality gates and is safe to deploy.
  • Facilitate reuse by operator and automated runs, reducing manual toil and error-prone handoffs.

Quick Start

Identify an automation opportunity in memory or action-converter outputs and run the tool-builder workflow to generate a new, reusable CLI tool.

Frequently Asked Questions about Tool Builder

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

FAQPage Schema
How do I turn recurring manual tasks into reusable CLI tools?

To turn recurring manual tasks into reusable CLI tools, the system analyzes memory logs and action-converter outputs to identify automation opportunities, then generates a self-contained script passing defined quality gates.

How do I generate automation scripts from cron-like patterns?

Generating automation scripts from cron-like patterns involves analyzing these recurring schedules alongside memory logs to design an idempotent CLI tool with defined inputs, outputs, and standard exit codes.

What quality gates do generated CLI scripts need to pass?

Generated CLI scripts must pass defined quality gates by enforcing standard exit codes, idempotent behavior, and help, dry-run, and JSON modes within a self-contained tool using YAML frontmatter.

Do I need YAML frontmatter to build CLI automation tools?

Yes, you need YAML frontmatter to build CLI automation tools, as it requires defining the tool name, description, inputs, outputs, and dependencies to ensure proper execution and reuse.