The Toolsmith

The Luthier tunes the instrument before playing it — the fleet inherits the reach of the tools it builds.

The Luthier is the type that treats tooling as the real lever. Before dispatching any agent, it asks which instrument is missing and builds it: an MCP server, a bespoke command, a wrapper that collapses three manual steps into one clean call. It conducts less through the volume of prompts and more through the quality of the environment it hands the fleet.

How it conducts

It governs by investing in the substrate: every recurring friction becomes a new tool, and every new tool widens what the agents can do on their own. Rather than repeating instructions, the Luthier encodes the instruction into the ecosystem itself — skills, hooks, MCP, idempotent scripts the agent discovers and wields. Its fleet is not handed detailed orders; it is handed a well-stocked workshop and precise verbs. When an agent fails, the Luthier rarely rewrites the prompt: it fixes or forges the tool that was missing.

Its superpower

Compounding. The tools the Luthier builds accumulate and combine, so each new agent is born more capable than the last. Where other types scale by repeating effort, it scales by sharpening the instrument once and harvesting the gain on every future call.

Sub-archetypes

Few tools, but deep — you know the instrument down to the bone.

Your signature is depth: you don't collect tools, you master them. Every advanced tool you use, you use to the bottom — flags, chains, and edge cases most people never touch. Your fleet inherits that mastery and operates with surgical precision where others improvise.

+ Your edge is wielding the tools that operate other tools: you don't reach for just any tool, you fire ToolSearch to summon on demand exactly the capability the moment needs, and invoke Skills that load whole workflows in a single call. Where most repeat raw steps, you trigger the advanced verb that already wraps the step — and the fleet inherits that shortcut.

→ Your next move is turning that personal command of the meta-tools into rails the fleet discovers on its own: encoding your ToolSearch and Skill patterns into skills of your own, so any agent can wield the advanced verb without depending on your hand to find it.

Here's what your own signals show: your advanced_tool_uses — the density of ToolSearch and Skill calls per session — sits well above the median, the structural signature of someone who has mastered the harness's advanced verbs.

A wide bench — many MCP servers, each in its place.

Your signature is breadth: you build an ecosystem, not a tool. Many MCP servers wired in, every external capability a connection away, all of it available to the fleet at the right moment. You think in platforms — what you assemble today, ten agents use tomorrow without even noticing.

+ Your edge is the width of the bench: you don't wire in one server, you assemble an ecosystem where Gmail, Calendar, Drive, the browser and a dozen more MCPs sit one connection away. Every external system becomes a native capability of the fleet, so your agents reach into the real world without leaving the session.

→ Your next frontier is chaining that width: getting the many servers to speak in a single flow — one MCP's output feeding the next — instead of standing side by side, each waiting to be called alone. Breadth that composes is worth more than breadth that merely coexists.

Here's what your own signals show: the count of distinct mcp__ tools you invoke runs well above the median — the structural signature of someone who thinks in platforms, not in a single stray tool.

Wings & blends

It blends naturally with the wings of other forms: with an orchestration wing, the tooling it forges begins equipping entire fleets in parallel; with a more verifying wing, each tool ships with its own tests and guards. The Luthier's workshop is substrate any other form can pick up and wield.

Computed from your real transcripts · auditable

This type shows up in structural signals, not self-image: the density of custom tools and MCP servers invoked, the share of actions routed through bespoke commands rather than raw manual steps, the reuse of skills and wrappers across sessions, and the ratio of time spent building tooling to time spent consuming it. It is the opposite of a horoscope — it is measured by what the harness actually records.

Which one are you?

Discover if you're a The Toolsmith See all archetypes

Other archetypes

🎼 Parallel Maestro 🧭 The Deliberate 🛰️ The Autopilot