lyndonkl/skills/product-hiding-scan
skills/product-hiding-scan/SKILL.md
--- name: product-hiding-scan description: Scans the substacker published corpus for clusters of posts that could become a product — a course, a book, a cohort, or a consulting offer. Produces at most 2 candidates with evidence + audience signal, or an honest "not yet" verdict if nothing qualifies. Typically fires once the writer has 30+ posts. Trigger keywords: product hiding, course from essays, book from essays, corpus to product, product scan. --- # Product Hiding Scan ## Workflow ``` Per
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude skills/product-hiding-scanInstall 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:18 AM89.9s1 file scanned
SKILL.md
- name:
- product-hiding-scan
- description:
- Scans the substacker published corpus for clusters of posts that could become a product — a course, a book, a cohort, or a consulting offer. Produces at most 2 candidates with evidence + audience signal, or an honest "not yet" verdict if nothing qualifies. Typically fires once the writer has 30+ posts. Trigger keywords: product hiding, course from essays, book from essays, corpus to product, product scan.
Product Hiding Scan
Workflow
Per quarterly run (with corpus ≥30 posts):
- [ ] Step 1: Cluster published corpus by theme (NOT by section — themes may cut across)
- [ ] Step 2: For each cluster with ≥5 posts, check product templates:
- Course: 5+ posts forming a progression
- Book: 15+ posts on one theme with coherent through-line
- Cohort: reader-demand signal in audience-notes
- Consulting: "can you help me do this" signal
- [ ] Step 3: For each qualifying cluster, write candidate block
- [ ] Step 4: If no cluster qualifies, say so plainly
Product templates
- Course: Shaan Puri's Power Writing on Maven — newsletter essays became the course syllabus. 5-8 posts forming a progression with exercises.
- Book: Paul Graham's Hackers & Painters — ~15 essays on adjacent themes, lightly edited. 15+ posts needed.
- Cohort / community: readers write back with their own versions of the problem → peer-learning value.
- Consulting / advisory: readers write back with "can you help me do this?" inquiries → productized consult.
Output per candidate
**Theme**: {name}
**Product type**: course | book | cohort | consulting
**Supporting posts**: {slug list}
**Minimum-viable product**: {1-2 sentences}
**Audience signal**: {what in the corpus or audience-notes suggests demand}
**Not yet if**: {the condition that would flip this from candidate to real}
Guardrails
- Max 2 candidates per review. More than 2 overwhelms.
- "No product is hiding yet. Come back at 30 posts" is a valid output.
- Require ≥5 posts on the theme before calling it a course.
- Require ≥15 posts on the theme before calling it a book.
- Audience signal is required. A cluster without reader demand is a future possibility, not a current candidate.
- Never propose a product the writer can't execute in 6 months (cohorts need infrastructure; books need a year).
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