lyndonkl/skills/cross-ref-topic-ledger
skills/cross-ref-topic-ledger/SKILL.md
--- name: cross-ref-topic-ledger description: For each Trend Scout candidate item, checks substacker shared-context/topic-ledger.md and tags with NEW | OVERLAPS seed:{slug} | OVERLAPS draft:{slug} | OVERLAPS published:{slug}. Adds a reinforcement_angle note for items overlapping with published posts ("external confirmation of X"). Read-only against the ledger. Use after summarize-signal, before rank-by-user-fit. Trigger keywords: cross-ref, ledger check, overlap, reinforcement, dedup external. -
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude skills/cross-ref-topic-ledgerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 10:11 AM150.0s1 file scanned
SKILL.md
- name:
- cross-ref-topic-ledger
- description:
- For each Trend Scout candidate item, checks substacker shared-context/topic-ledger.md and tags with NEW | OVERLAPS seed:{slug} | OVERLAPS draft:{slug} | OVERLAPS published:{slug}. Adds a reinforcement_angle note for items overlapping with published posts ("external confirmation of X"). Read-only against the ledger. Use after summarize-signal, before rank-by-user-fit. Trigger keywords: cross-ref, ledger check, overlap, reinforcement, dedup external.
Cross-Ref Topic Ledger
Workflow
Per candidate:
- [ ] Step 1: Parse topic-ledger.md into {slug, title, status, tags, last_touched} records
- [ ] Step 2: Extract 2-5 topic tags from the candidate's summary (reuse ledger vocabulary)
- [ ] Step 3: Match candidate to ledger entries by tag overlap (≥2 shared tags) OR semantic title similarity
- [ ] Step 4: Classify: NEW | OVERLAPS seed:{slug} | OVERLAPS draft:{slug} | OVERLAPS published:{slug}
- [ ] Step 5: If OVERLAPS published, generate reinforcement_angle (1 line)
- [ ] Step 6: Annotate candidate with dedup_status, overlap_slug, reinforcement_angle
Classification rules
- NEW: tag overlap <2 AND title similarity <0.4.
- OVERLAPS seed:{slug}: writer has a seed on this; mention is context but NOT a new seed candidate.
- OVERLAPS draft:{slug}: writer is actively working on this; may absorb external evidence.
- OVERLAPS published:{slug}: writer already shipped on this; becomes reinforcement material for future posts.
Reinforcement angle
When OVERLAPS published: generate a one-line angle the writer could use in a future post.
Example:
- Candidate: Transformer Circuits — "Attention as Soft Nearest-Neighbor Lookup"
- Overlaps: published
attention-as-kernel-regression - Reinforcement angle: "Anthropic's interp team came at this from circuits; I came at it from kernel regression — same answer."
Guardrails
- Read-only. Never mutate the ledger. Never propose ledger edits here.
- If ledger is stale (>60 days since last touch), emit a warning in digest appendix.
- Borderline matches → prefer
NEW; false negatives (a missed overlap) are worse UX than false positives (a buried genuine thread). - Reinforcement angles are drafts — writer refines on use. Keep ≤1 sentence.
- Never cross-reference with
corpus/dead/— dead ideas should stay dead for Trend Scout's purposes.
Related Skills
lyndonkl/skills/zettel-note
development
VerifiedTrustedCommunity
--- 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-
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-transfer-planner
development
VerifiedTrustedCommunity
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.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-tournament-state
testing
VerifiedTrustedCommunity
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.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-signal-emitter
development
VerifiedTrustedCommunity
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.
119SKILL.mdUpdated Jun 12, 2026