lyndonkl/wc-signal-emitter
skills/wc-signal-emitter/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude wc-signal-emitterInstall 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: Jun 12, 2026, 7:33 AM184.8s1 file scanned
SKILL.md
- name:
- wc-signal-emitter
- description:
- 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.
wc-signal-emitter — validate + persist signals
Implements the persistence side of footballfantasy/context/frameworks/signal-framework.md. Agents communicate through structured signal files; this skill is the gate that keeps those files trustworthy, so downstream agents can read rather than recompute.
Workflow
- [ ] 1. Receive the signal (frontmatter + body) and its declared type
- [ ] 2. Validate frontmatter, type, numeric ranges, source citations
- [ ] 3. If valid → write to signals/YYYY-MM-DD-<type>[-<scope>].md and return the path
- [ ] 4. If invalid → do NOT persist; return the validation errors so the caller can fix and retry
Validation checklist
- Frontmatter present:
type,round,date,emitted_by,confidence(0–1),source_urls. - Type known: one of the registry in
signal-framework.md(scout,player-ev,clean-sheet,fixture,ownership,candidate,fitness,offspring,verify,chip-plan,transfer-plan,board). Reject unknown types. - Numeric ranges: any signal that declares a range is checked against it (probabilities ∈ [0,1]; ownership ∈ [0,100]; xEV ≥ 0; confidence ∈ [0,1]). Out-of-range → reject.
- Citations: every factual claim in the body traces to a
source_urlsentry or is explicitlymanager-provided. A signal asserting a predicted XI / injury / price / ownership with no URL → reject (or forceconfidence ≤ 0.35and a "needs confirmation" flag if the caller insists it's a best-effort estimate). - Confidence sanity: confidence matches the framework bands (unconfirmed load-bearing fact ⇒ ≤0.35).
On failure
Do not write the file. Return the specific errors. Optionally append a one-line note to tracker/calibration-review.md if a signal repeatedly fails validation (a sign an upstream agent is mis-formatting). The caller fixes and retries.
Naming
signals/YYYY-MM-DD-<type>.md, or signals/YYYY-MM-DD-<type>-<scope>.md for per-entity signals (e.g. -scout-musiala, -candidate-A2). Round id goes in frontmatter.
Guardrails
- No silent persistence of unvalidated signals. A bad signal poisons every downstream reader; reject it.
- Cite or cap. Uncited factual claims either don't persist or persist at
confidence ≤ 0.35with a flag — never as confident fact. - One signal, one file. Don't append unrelated signals into one file; downstream readers glob by type+round.
Related Skills
lyndonkl/conf-theme-clustering
testing
VerifiedTrustedCommunity
Cluster a conference's event records into a small set of coarse themes with finer sub-clusters, an explicit outlier bucket, and soft (multi-membership) affinities — using the hybrid embed-then-label pipeline (embed abstracts, reduce, density-cluster, then LLM-label the clusters) when embedding libraries are available, and an LLM-reasoned hierarchical fallback when they are not. Embeddings do the grouping; the LLM only names the groups. Conference-agnostic. Use when turning structured event records into a navigable theme map for preference elicitation and scheduling, when you need 6-8 reasonable themes rather than 20 muddy ones, or when overlapping talks must belong to more than one theme. Trigger keywords - theme clustering, cluster talks, embed then label, soft membership, outlier talks, conference themes, topic map.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-schedule-optimization
development
VerifiedTrustedCommunity
Build a personal conference schedule as a constraint-optimization problem — hard constraints (no time overlap, room-to-room travel time, capacity/registration, the attendee's own must-attends and blackouts) plus a user-owned weighted objective trading interest against breadth, pacing (maximize contiguous free time), and serendipity. Surfaces unbreakable conflicts (two high-value overlapping talks the model cannot rank) as decisions for the human rather than silently picking, and reports what each choice traded away. Conference-agnostic. Use to turn a preference profile plus a theme map into a day-by-day plan, to resolve overlapping sessions, or to balance a packed vs paced schedule. Trigger keywords - schedule optimization, conference schedule, constraint optimization, overlapping talks, contiguous free time, conflict surfacing, packed vs paced.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-program-extraction
development
VerifiedTrustedCommunity
Parse a heterogeneous conference program (markdown, HTML, PDF-derived text, or JSON) into normalized event records with per-field confidence scores and independent classification axes (topic, depth, format, prerequisites, recorded, capacity). Detects the program's format before extracting, treats every inferred field as uncertain (present vs inferred vs missing), and flags thin or missing abstracts so downstream enrichment can target them. Conference-agnostic. Use when ingesting a conference or event schedule into a structured store, normalizing a talk/session list, or extracting per-session metadata with calibrated confidence. Trigger keywords - program ingestion, parse schedule, session extraction, event records, conference program, talk metadata, per-field confidence.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-preference-elicitation
development
VerifiedTrustedCommunity
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it can actually ask the person. Conference-agnostic. Use to turn a theme map into a preference profile, to decide what to ask a conference attendee, or to elicit scheduling priorities. Trigger keywords - preference elicitation, ask few questions, information gain, choice-based questions, selection bias probe, objective weights, attendee preferences.
127SKILL.mdUpdated Jun 28, 2026