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
npx skillsauth add lyndonkl/claude skills/product-hiding-scanInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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
**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}
testing
--- name: advisory-edit description: A strict advisory-only editing discipline for a writer who dictates ("speaks out") essays and wants help WITHOUT having their voice changed. The editor directs structure, flags grammar, and suggests strategic language — but never modifies the writer's text unless the writer explicitly says "apply" / "make that change" / "rewrite this." Produces a line-referenced, suggestion-only critique where every item is marked the writer's call. Four passes: structural, l
testing
Provides the house style for analyst-grade strategist writing — third-person register with sparing first-person, no em dashes, no "not X, not Y, not Z" negation cascades, numbered footnote citations rather than inline source parentheticals, specific opinion-signaling phrases, and topic-forward paragraph structure modeled on voice patterns observed in Damodaran's Musings on Markets and Thompson's Stratechery. Use when consolidating working notes into a finished long-form strategist or analyst report that must read as written by a senior human analyst rather than an AI assistant.
testing
Renders a markdown report to a PDF using pandoc with xelatex (11pt serif body, 1-inch margins, numbered footnotes, formal heading hierarchy). Requires a one-time install of pandoc and a LaTeX engine on the user's machine — basictex on macOS or texlive-xetex on Linux. Does not attempt automatic install. Fails loudly with the exact install commands if pandoc or xelatex is missing on the user's PATH. Use when producing a finished strategist or analyst report PDF from a polished markdown source.
testing
Produces step-by-step computational walkthroughs of vector and matrix operations as a sequence of numbered "frames", showing the explicit state at each step. The text-equivalent of a 3Blue1Brown animation — each frame shows what changed and why, so the learner can re-trace the operation by hand. Use when the learner needs to *see* a computation unfold (eigenvalue computation, attention with 3 tokens, gradient descent step, SVD on a 2×2, layer norm on a 3-vector, softmax of a small input), when an explanation has been given but the learner needs to ground it in a worked example, or when introducing an operation that's intimidating in symbol form but trivial in pencil-and-paper form.