--- name: proof-kb description: Build and maintain an atomic First-Hand Proof Knowledge Base (seo/kb/) inside a repository, draft or upgrade pages with Consensus + Proof Card architecture, and propagate new benchmarks or facts across every matching page via route-fact. Use when scaffolding seo/kb/, extracting founder proof from transcripts or interviews, upgrading thin SEO posts with real receipts, or routing a new benchmark, customer win, or pricing change across multiple pages. metadata: author: illyism source: https://il.ly/skills/proof-kb version: 1.0.0 --- # First-hand proof knowledge base (`seo/kb/`) FAQ schema, fresh `updatedAt` dates, author bios, and word counts no longer separate ranking pages from AI-generated commodity posts, because every competitor copies them in seconds. Pages that hold top-3 Google positions and get cited by ChatGPT, Claude, and Perplexity do two things a competitor cannot copy: 1. **Open with a concrete first-hand receipt in the first 2 sentences** (an exact test count, latency delta, dollar figure, or production dataset). 2. **Stack at least 4 of the 5 proof categories** below across the body. Store every verifiable fact once in `seo/kb/` and wire those atomic proof files into money pages, comparisons, and blog posts. Agents writing from one fact store stop inventing specs and quoting stale prices. ## Workflow routing decision tree Walk this tree on every invocation: ``` Does `seo/kb/brand-ssot.md` exist? ├── No -> Workflow 1: `init`, then continue down this tree └── Yes ├── Did the user just ship a benchmark, customer win, pricing change, or release? │ └── Yes -> Workflow 4: `route-fact` ├── Does the user want a site-wide proof gap audit? │ └── Yes -> Workflow 2: `interview` across the top 5 money/blog pages in `seo/kb/pages-index.md` └── Is the user drafting or upgrading a specific page? ├── Fewer than 4 proof categories in `seo/kb/proof/` match this page's topic? │ └── Yes -> Workflow 2: `interview`, then Workflow 3 └── 4 or more -> Workflow 3: `draft` / `upgrade` ``` ## The 5 categories of first-hand proof Every commercial guide, comparison page, or benchmark post ships with at least **4 of these 5 categories**. One claim type repeated five times still reads as thin marketing copy to buyers and retrieval models. | Category | Location | Example (`querybench.dev` / `deployfast.dev`) | | --- | --- | --- | | **1. Benchmarks and controlled tests** | `seo/kb/proof/benchmarks/` | Tested 14 Postgres connection poolers at 10,000 concurrent connections on an `m7g.xlarge`; PgBouncer held p99 at `4.2ms` vs `19.8ms` unpooled. | | **2. Customer outcomes and migrations** | `seo/kb/proof/customers/` | `invoicekit.io` moved 42,000 recurring billing webhooks from AWS Lambda to `deployfast.dev` workers and cut monthly compute from `$1,840` to `$290`. | | **3. Real screenshots and short videos** | `public/blog//` + proof ID | Real Playwright capture of the terminal trace or a 9-second `