skills/check-analogy-novelty/SKILL.md
--- name: check-analogy-novelty description: Cross-references each proposed analogy in a 5-framing set against substacker shared-context/analogy-catalog.md to flag reuse. Classifies each analogy as new, reused-from-catalog (and which entry), or adjacent-to-catalog (close to an existing entry but not identical). Prevents the writer from recycling "imagine a library" for the twentieth time. Use after generate-analogy-set and before presenting framings to the writer. Trigger keywords: novelty, cata
npx skillsauth add lyndonkl/claude skills/check-analogy-noveltyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Related skills: Called by the Intuition Builder after generate-analogy-set and before presenting framings. Reads shared-context/analogy-catalog.md. Does NOT write to the catalog — that's update-analogy-catalog's job, fired on publish.
For each of the 5 framings:
- [ ] Step 1: Extract the analogy's source domain (e.g., "library card catalog")
- [ ] Step 2: Extract the analogy's target concept (e.g., "KV cache")
- [ ] Step 3: Grep analogy-catalog.md for exact or near-exact source × target match
- [ ] Step 4: Classify: new | reused-from-catalog | adjacent-to-catalog
- [ ] Step 5: For reused/adjacent, cite the catalog entry with its post
"Close variant" = same source domain (library, immune system, bucket brigade) even if different specific instance.
Proposed framings for KV cache:
Catalog check:
library → KV cache, or ring buffer, or index.Output:
But: if the catalog had an entry "Library index → tokenizer vocabulary", framing 1's adjacency would trigger: "adjacent-to-catalog — library appears once for a different target". Flag softly.
new by definition. Note this once in the output.{new | reused-from-catalog | adjacent-to-catalog} with citation.development
--- name: zettel-note description: The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-
development
Plans between-round FIFA World Cup Fantasy transfers — budgets the round's free transfer(s), forces out players whose nation has been eliminated, chases fixture-swing drops, upgrades on value, and decides when a rebuild is large enough to fire the Wildcard instead of spending free transfers one at a time. Ranks candidate in/out pairs by EV gain over each player's remaining survival horizon (delta xEV weighted by progression_carry) MINUS transfer cost (a free transfer is cheap, a points hit is real, churning the squad for marginal swings is a critic flag), and tags forced/fixture/upgrade priority. Emits a `transfer-plan` signal. Use when called by wc-squad-architect (whose transfer work this skill is the engine for) and by the strategists in the populate stage when their candidate is transfer-adjacent rather than a full rebuild.
testing
Reads and updates the FIFA World Cup Fantasy tournament state machine (footballfantasy/context/tournament-state.md) — the temporal backbone tracking phase (pre-tournament → group MD1-3 → R32 → R16 → QF → SF → final), budget ($100m group / $105m knockouts), nation cap (3 group, loosening in knockouts), chips remaining, surviving nations, each owned player's elimination-risk horizon, and deadlines. Validates state on load (count/feasibility checks), applies phase transitions, and appends to the append-only state log (never silent overwrite). Use to load state at the start of a run and to commit state changes after the manager makes a move.
development
Validates and persists FIFA World Cup Fantasy signal files to signals/YYYY-MM-DD-<type>.md. Checks the required frontmatter (type, round, date, emitted_by, confidence, source_urls), range-checks declared numeric signals, confirms every factual claim carries a source URL or "manager-provided", rejects unknown signal types, and refuses to persist a signal that fails validation (logging the failure instead). Keeps the inter-agent signal layer auditable so downstream agents can trust what they read and never re-derive it. Use whenever an agent or skill writes a signal.