What problem does it solve? Technical answers stated from memory are often wrong, outdated, or version-mismatched, and they fail silently in production months later. This Skill forces every load-bearing technical claim about a library, framework, or API to be traced back to the primary source that owns it — official docs, source code, specs, or a live API call — before you build on it. ## Core Features & Use Cases - Source-of-record ladder: Ranks sources from Tier 1 (running code, versioned official references, specs) down to Tier 4 (Stack Overflow, blogs, other AI answers), which may only be used as leads, never citations. - Trace-gate lint: Every load-bearing assertion must be traced to a Tier 1–2 authority, version-pinned with a permalink, checked against the running artifact where cheap, and flagged under-evidenced if it cannot be traced. - Two modes: A scrappy path for one-fact lookups (API signature, config default, deprecation check) and a rigor path for answers that gate shipped code or architecture decisions. - Use Case: Before forcing a tool call in an Anthropic Messages API router, verify the exact tool_choice object shape against the versioned API reference and one real call, then save the cited finding so the next build reuses it instead of re-researching. ## Quick Start Ask the agent to verify how a specific API or library feature behaves in your pinned version and save the answer as a cited Markdown file.
