world-firstlisted

Use when the goal is to produce and defensibly claim a genuine world-first, invention, novel algorithm/protocol/kernel/mechanism, or "nobody has done this" capability — and to prove the claim rather than assert it. Triggers on intent like "invent", "world-first", "first-ever", "beat the incumbent with something new", "break all dogma", "is this novel?", "prove this is new", or any push to build a mechanism a competitor structurally cannot. Also use to audit an in-flight "first" claim for overclaim before it ships, is committed, benchmarked-for-publication, or sent externally. This is the packaging of the INVENTION PLAYBOOK: confirmed-limit entry → TRIZ ideation → the removed-constraint test → refute-then-build vs a tuned baseline → provenance search → certify → kill failure modes. Reach for it by default on invention and novelty-claim work; skip only for routine feature work with no novelty claim attached.
88plug/world-first · ★ 0 · AI & Automation · score 58

Install: claude install-skill 88plug/world-first

# World-First An invention is a **measured delta past a confirmed limit, proven novel against a searched corpus, and reproducible by someone who is not you.** Everything in this skill exists to make each of those four clauses true *before* the word "first" is used. The failure mode this skill prevents is the confident-but-wrong "first-ever!" that dies in review — you would rather be slow-and-true than fast-and-impressive. This skill is the operational packaging of the invention pipeline. It **composes with `scientific-method`'s `invent.md`** (the falsification→invention engine, provenance protocol, certification ladder, claim charts) — read that reference for the deep machinery. What this skill adds is the *entry discipline* (a confirmed limit, never a hunch), the **removed-constraint test** (the single strongest generator of a real systems first), the **dogma-mining** move for finding unclaimed territory, and a **candidate-first template** you fill in. **Before writing any code against an API, kernel contract, or FFI boundary, invoke `read-the-damn-docs`.** Inventions die on stale-memory API guesses more than on bad ideas — a wrong launch contract produces garbage output that looks like a failed invention when it was a failed lookup. Ground the mechanism in what the docs/types/source actually say for the version in play, then cite it. ## The gate that comes first: a CONFIRMED limit Do not start an invention campaign from "wouldn't it be cool if." Start from a **measured