Tool Anatomy

Install in one command

mkdir -p ~/.claude/skills/tool-anatomy && curl -fsSL https://eliteaiadvantage.com/skills/tool-anatomy/SKILL.md -o ~/.claude/skills/tool-anatomy/SKILL.md

Tool Anatomy is for the moment a customer just hit an error and you need to triage in under two minutes. It resolves the tool slug (fuzzy-matched), discovers its surface (route, page, prompts, components, schema, marketing copy), runs the live failure query against error_reports and api_logs, builds a Symptom-to-Likely-Cause-to-Where-to-Look table, maps the fallback chain, and pulls the recent commits that touched the tool.

The output is decision-grade: triage info goes UP TOP, reference info (anatomy, prompts, helpers) goes below. Persists to docs/tool-anatomy/<slug>.md by default so the report becomes durable artifact, not a chat scrollback. Two modes: full anatomy (default) or --triage with an error string for a focused diagnosis. Critically, it does NOT auto-suggest fixes, anatomy reports get treated as authoritative and 'fix suggestions' become footguns. The skill surfaces symptom, cause, and location; the fix decision belongs to you.

• →Resolves a vague complaint ('the keyword tool isn't working') into a structured brief with file:line answers in seconds.
• →Runs the live failure query against error_reports and api_logs so the report reflects what's actually happening, not just the code.
• →Builds a Symptom-to-Likely-Cause-to-Where-to-Look table, the killer feature for under-2-minute triage.
• →Maps the fallback chain (Tier 1 success, Tier 2 degraded, Tier 3 user-facing error).
• →Pulls recent commits touching the tool so you can suspect the change before suspecting the bug.
• →Persists to docs/tool-anatomy/<slug>.md, durable artifact, not chat scrollback.

• •A customer just hit an error and you need to triage in under two minutes.
• •Onboarding a new operator who needs to understand a tool's surface fast.
• •Auditing a tool's fallback chain to confirm degraded modes still serve the user.
• •Suspecting a recent commit broke a tool, the recent-commits section answers in one read.
• •Building runbook docs for a SaaS where every tool needs a known anatomy.
• •Running --triage with a specific error string when the customer pasted you the message.

Without this skill, Claude reads the route file, then the page, then the prompts, then asks where the error logs live. Tool Anatomy reshapes the workflow into a parallel discover-and-query pass that produces a decision-grade brief with triage at the top. You stop getting 'let me look around the codebase' and start getting 'Symptom: 502 from /api/tools/keyword-research. Likely cause: DataForSEO timeout. Where to look: route.ts:142 withDeadline call. Last touched: c7a4f1 yesterday, added the timeout, may be too tight.'