lyndonkl/skills/update-audience-notes
skills/update-audience-notes/SKILL.md
--- name: update-audience-notes description: Appends one structured YAML observation block to substacker shared-context/audience-notes.md iff the week produced at least one observation with confidence ≥ medium. Includes supporting evidence (post slugs + numbers) and reviewed_by_curator flag. Never rewrites or deletes prior entries. Append-only discipline protects downstream agents' shared context. Use at the end of each weekly pipeline after write-weekly-report. Trigger keywords: audience notes,
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude skills/update-audience-notesInstall 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:22 AM138.4s1 file scanned
SKILL.md
- name:
- update-audience-notes
- description:
- Appends one structured YAML observation block to substacker shared-context/audience-notes.md iff the week produced at least one observation with confidence ≥ medium. Includes supporting evidence (post slugs + numbers) and reviewed_by_curator flag. Never rewrites or deletes prior entries. Append-only discipline protects downstream agents' shared context. Use at the end of each weekly pipeline after write-weekly-report. Trigger keywords: audience notes, append observation, audience insight, confidence-rated.
Update Audience Notes
Workflow
At end of weekly pipeline:
- [ ] Step 1: Review attribution outputs for any pattern observed
- [ ] Step 2: Filter to confidence ≥ medium only (low is never appended)
- [ ] Step 3: Format as YAML block per schema
- [ ] Step 4: Append to shared-context/audience-notes.md
- [ ] Step 5: If no medium+ observation this week, log "no additions this week" to weekly report's data-caveats (not to audience-notes)
YAML block schema
- date: YYYY-MM-DD
week: YYYY-WW
observation: >
{plain English, ideally testable}
confidence: medium | high
evidence:
- slug: {post-slug}
metric: {value}
baseline: {value}
reviewed_by_curator: false
Example entries
- date: 2026-06-01
week: 2026-W22
observation: >
External restack from a larger ML account on Substack Notes is
the strongest sub-acquisition channel observed to date —
+49 subs from a single post vs ~+4 baseline, with 71% of the
new cohort landing in "active" tier immediately.
confidence: high
evidence:
- slug: why-your-embedding-search-melted-at-10pm
open_rate: 0.61
click_rate: 0.12
baseline_open: 0.49
baseline_click: 0.05
new_subs: 49
active_tier_of_new_subs: 35
external_restacks_observed: 2
reviewed_by_curator: false
Guardrails
- Append-only. Never rewrite or delete prior entries. Entries stand.
- Confidence floor: medium. Low-confidence observations stay in the weekly report body; never enter shared context.
- Evidence required. Every observation cites at least 2 posts (or 1 post + 1 external datum) with specific numbers.
reviewed_by_curator: falseon append; Curator flips totrueon its next monthly review.- Never append an observation identical to a prior entry. Dedupe by the
observationfield's content. - If >2 medium+ observations in one week, append all of them as separate blocks.
- Individual subscriber info (email, name) never in evidence — aggregate counts only.
Quick reference
- Append-only writes.
- Confidence floor: medium.
- Evidence: ≥2 posts / data points with numbers.
- Fires once per week at pipeline end; may write 0, 1, or 2+ blocks.
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