Toolsmith Tools

Three tools

• ✓toolsmith.forge — Generate a direct-query tool spec from a natural language goal. Uses SchemaCache for custom field awareness, EBNF grammars for query validation, and LLM generation. Optionally saves as a reusable skill with CTC minting
• ✓toolsmith.temper — Modify an existing skill or tool. Transparent mode (owner) edits the full spec surgically. Opaque mode (non-owner or closed-source) generates fresh from annotations only — preventing source leakage through derivation chains. Supports update (in-place) and fork (new derived skill) modes
• ✓toolsmith.catalog — Browse and search available skills with filtering by name, integration, and source type. Opacity-aware redaction hides specs for closed-source skills while keeping annotations visible. Zero credits

Provenance and IP protection

Every forged or tempered skill carries a full provenance chain. The opaque lineage taint propagates through any derivation — if you fork a closed-source skill, the fork inherits the taint. This prevents "laundering" attacks where someone tempers a first-party skill, saves it, then tempers the saved version to reveal the original source.

Skills have a license field (open, closed, private) that governs visibility in the catalog and whether temper uses the transparent or opaque path. This is the foundation for a future skill marketplace.

Example: forge + temper

// Forge a new query tool from a natural language goal
{ "name": "data-grout@1/toolsmith.forge@1",
  "arguments": {
    "goal": "get leads created this week with email and company",
    "integration": "salesforce",
    "entity": "Lead",
    "save_as_skill": true,
    "skill_name": "Recent Leads"
  }
}

// Temper (modify) an existing skill with a new goal
{ "name": "data-grout@1/toolsmith.temper@1",
  "arguments": {
    "skill_id": "skill_abc123",
    "goal": "also filter by region = West",
    "mode": "fork",
    "save_as_skill": true
  }
}