skills/voice-fitness-check/SKILL.md
--- name: voice-fitness-check description: Ranks a proposed set of framings against the writer's voice profile, especially the analogy-direction priority — biology > organizational > sports, with physics/military as voice violations. Produces a tier rating per framing and flags any framing that would break voice. Use in the Intuition Builder pipeline after generating framings, to order them by fit with the writer's register. Trigger keywords: voice fit, analogy direction, biology to AI, organiza
npx skillsauth add lyndonkl/claude skills/voice-fitness-checkInstall 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 in the pipeline (step 5). Reads shared-context/voice-profile.md and shared-context/voices/{section}.md if a target section is specified.
From voice-profile.md section 9:
Everything else is Tier 4 (acceptable but not a voice signature).
Physics, military, warfare, weapons, combat — these are voice violations. Flag strongly. Propose a replacement in Tier 1–3 direction if one is available.
For each of the 5 framings:
- [ ] Step 1: Classify the source domain
- [ ] Step 2: Assign a tier (1-4) based on the priority table
- [ ] Step 3: Flag any Tier 4 or voice-violating framings
- [ ] Step 4: Rank the 5 framings overall (tier + craft quality)
- [ ] Step 5: Recommend first choice
Look at the source. Is it:
"Neural network" itself counts as biology — but only if the framing actually uses biological relations (neurons firing, learning as development), not just the name.
Topic: Multi-agent AI system.
5 framings (from generate-analogy-set):
Ranking:
Recommendation: First choice is the parliament contrarian. Swap framing 5 for the biological alternative.
voices/{section}.md) with different priorities, apply those on top of global.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.