lyndonkl/skills/search-corpus
skills/search-corpus/SKILL.md
--- name: search-corpus description: Answers "what have I already thought about X?" by searching the substacker corpus (seeds, drafts, published) for seeds matching a topic, keyword, analogy, or author. Returns a ranked list of seeds with id, title, status, density score, and a one-line excerpt. Use when another agent (Intuition Builder, Editor) needs prior thinking before generating new material, or when the writer asks "have I written about X." Trigger keywords: search, find, what have I, alre
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude skills/search-corpusInstall 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:20 AM131.9s1 file scanned
SKILL.md
- name:
- search-corpus
- description:
- Answers "what have I already thought about X?" by searching the substacker corpus (seeds, drafts, published) for seeds matching a topic, keyword, analogy, or author. Returns a ranked list of seeds with id, title, status, density score, and a one-line excerpt. Use when another agent (Intuition Builder, Editor) needs prior thinking before generating new material, or when the writer asks "have I written about X." Trigger keywords: search, find, what have I, already thought, prior work, precedent, have I written about.
Search Corpus
Table of Contents
- Workflow
- Query forms
- Output format
- Worked example
- Guardrails
Related skills: Called by intuition-builder (before generating framings), editor (before reviewing a draft to surface prior thinking), writer directly. Read-only — no writes.
Workflow
Search corpus for query:
- [ ] Step 1: Parse query → topic tag, keyword, analogy term, or author
- [ ] Step 2: Grep corpus/{seeds,drafts,published}/**/*.md
- [ ] Step 3: Rank matches by signal
- [ ] Step 4: Format top 10 as a ranked list with id, status, density, excerpt
Query forms
The skill accepts three query shapes:
- Topic tag (e.g.,
dropout): grep frontmattertopics:for the tag; fallback to body keyword. - Freeform keyword (e.g.,
kv cache): grep body + title for the phrase. - Structured (e.g.,
{topics: [attention-mechanism], status: published}): direct filter.
Ranking
Rank by:
- Exact tag match > freeform body match.
- Density score descending.
- Recency (created date descending).
- Status priority:
published > draft > seed > dead.
Exclude corpus/dead/ always unless query includes include_dead: true.
Output format
Top 10 matches, one per line:
N. {id} | {status} | density={score} | "{first-sentence excerpt, ≤120 chars}"
If >10 results, show 10 and append: ... N more matches — narrow the query.
If 0 results: No matches. Candidate related searches: {suggest 2-3 alternate topic tags}.
Worked example
Query: dropout
Matches:
1. 2026-04-21-dropout-as-ensemble-thinned-networks | seed | density=7 | "had a thought while running — dropout is secretly an ensemble method."
2. 2026-02-08-bagging-in-deep-nets | draft | density=6 | "bagging is the thing dropout is trying to be."
3. 2025-11-14-noise-as-regularization | published | density=5 | "adding noise at training time prevents the model from memorizing."
Query: KV cache (freeform)
Matches:
No matches. Candidate related searches: attention-mechanism, inference, context-engineering
Guardrails
- Read-only. Never mutates seeds.
- Never returns seeds from
corpus/dead/unless query explicitly opts in. - Excerpt is verbatim from body — never a summary.
- If >10 matches, truncate and tell the caller.
- If 0 matches, suggest related searches; do not invent matches.
- Respect
manual_edits: true— do not reveal private-looking content beyond first-sentence excerpt without caller explicitly requesting full seed read.
Quick reference
- Input: query string or structured filter.
- Output: top-10 ranked matches with id, status, density, excerpt.
- Read-only, no side effects.
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