skills/structural-review/SKILL.md
--- name: structural-review description: Performs pass-1 structural review of a substacker essay draft — argument flow, out-of-order moves, buried topic sentences, missing pivots, weak signposting, paragraph-logic issues. Emits the "Argument flow" and "Structural blockers" sections of the Editor artifact. Use when reviewing a draft's macro-structure before addressing voice, when a draft feels like it meanders, or when the user asks whether the argument lands. Trigger keywords: structure, argumen
npx skillsauth add lyndonkl/claude skills/structural-reviewInstall 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.
Related skills: Called by the Editor as the first structural skill. Runs before voice-check, hedge-detector, slop-detector. Pairs with paragraph-rhythm-check (paragraph logic) and opener-critique / closer-critique.
Structural review of draft D:
- [ ] Step 1: Extract paragraphs as an array. For each: first-sentence topic + word count
- [ ] Step 2: Produce a 1-line-per-paragraph outline of the draft AS READ
- [ ] Step 3: Compare to expected essay shape (see below)
- [ ] Step 4: Flag out-of-order moves, buried topic sentences, walls, missing pivots, weak signposts
- [ ] Step 5: Per flag: tier (1 or 2), paragraph index, quote, reason, ≤2 suggested rewrites
Writer's signature shape (from voice-profile signature moves + opening/closing patterns):
1. Confession / concrete admission (opener)
2. Reframe / thesis
3. Exposition (mechanism, data, arithmetic)
4. Pivot (usually a one-sentence paragraph)
5. Applied case / example (often the IPL/Kalshi trade or a pathology slide)
6. Bolded maxim or forward-looking close
Not every essay hits every beat — short reflective posts skip steps 3 and 5. Series-log posts compress 2-3 and always include a scoreboard in 6.
Flag if:
opener-critique).Draft outline (as Editor reads it):
Flags (structural):
series: {slug}) get a special-case: step 5 often IS the scoreboard+trade narration, not an extended applied case. Don't flag absence.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.