skills/update-watchlist/SKILL.md
--- name: update-watchlist description: Proposes adds and removes to the Trend Scout watchlist based on consecutive-failure sources, repeated-reference external authors, and user-added feedback markers. Emits a proposed diff at ops/trend-scout/watchlist-proposed-diff.md for user review. On explicit approval, applies the diff. Monthly cadence. Trigger keywords: watchlist update, add source, remove source, watchlist review, monthly review, source pruning. --- # Update Watchlist ## Workflow ```
npx skillsauth add lyndonkl/claude skills/update-watchlistInstall 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.
Monthly (first weekly run of the month):
- [ ] Step 1: Read last 4-8 weekly digests' appendices
- [ ] Step 2: Identify sources with ≥3 consecutive fetch failures (remove candidates)
- [ ] Step 3: Identify external authors/URLs referenced by watchlist sources ≥3 times in a month (add candidates)
- [ ] Step 4: Parse any user-added markers in digest bodies (<!-- scout: drop-this-source --> / <!-- scout: add {url} -->)
- [ ] Step 5: WebFetch each proposed add to validate it returns content
- [ ] Step 6: Emit ops/trend-scout/watchlist-proposed-diff.md
- [ ] Step 7: On user approval (.approved file or explicit trigger), apply diff; append changelog to watchlist.md
# Watchlist changes proposed 2026-W17
+ ## people
+ - name: "Interconnects (Nathan Lambert)"
+ url: https://www.interconnects.ai/archive
+ source_type: blog
+ essential: false
+ rationale: "Referenced 6x in last 4 weeks from Raschka, Willison, Transformer Circuits."
- ## blogs
- - name: "someblog"
- url: https://someblog.example/
- source_type: blog
- rationale: "4 consecutive fetch failures."
essential: true sources without explicit user approval.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.