Tool Factory

Tool Factory

A self-healing lifecycle system for Claude Code tools. Build, score, refurbish, and manage skills, agents, hooks, commands, and MCP servers at scale.

The Problem

Claude Code's tool ecosystem grows fast. After months of building, you end up with hundreds of tools — skills, agents, hooks, commands, MCP servers, plugins — and no way to know which ones work, which are duplicates, and which are dead weight. Quality is inconsistent. Tools rot silently.

The Solution

Tool Factory treats tools like products. Born with standards, tested against criteria, refurbished when they drift, retired when they're obsolete. A machine that builds machines — and maintains them.

Architecture

Two layers, three spaces:

Layer 1: Factory (builds and maintains tools)
Layer 2: Tools  (the skills/agents/hooks that do actual work)

Factory Floor (generators/)  -- Creates new tools from templates
Range         (range/)       -- Scores tools against fitness criteria
Workshop      (workshop/)    -- Auto-retrofits failing tools

Directory Structure

tool-factory/
  generators/          # Tool creators (skill, agent, command, hook, MCP)
  range/               # Quality scoring (14 criteria, 100-point scale)
  workshop/            # Auto-retrofit for failing tools
  composer/            # Pipeline chaining (YAML compositions)
  registry/            # Tool inventory + intelligence + lifecycle
    index.json         # Single source of truth for all tools
    intelligence.sh    # Fleet health, usage, trends, dormant detection
    lifecycle.sh       # 4-phase maintenance cycle
    score-history.jsonl # Append-only score snapshots
    track-usage.sh     # Invocation logger
  lexicon/             # Constraint documents (best practices per vendor)
  scripts/             # Automation (scheduled lifecycle wrapper)
  lib/                 # Shared utilities (colors, etc.)
  validator/           # Structural validation
  VISION.md            # Where we're going (nort