skills/quarterly-zoomout/SKILL.md
--- name: quarterly-zoomout description: Synthesizes 13 weeks of substacker Growth Analyst reports + the most recent Curator review + a meta-scan of the published corpus into a 400-700 word narrative that names the quarter's shape — what happened, what changed, what held steady, what surprised. Used by the Growth Strategist at the opening of every review. Trigger keywords: quarterly, zoomout, quarter narrative, rollup, what happened this quarter. --- # Quarterly Zoomout ## Workflow ``` Per qu
npx skillsauth add lyndonkl/claude skills/quarterly-zoomoutInstall 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:
- [ ] Step 1: Glob ops/growth-analyst/*.md since last Strategist review
- [ ] Step 2: Glob ops/curator/*.md — most recent
- [ ] Step 3: Meta-scan corpus/published/ (titles, dates, first paragraphs)
- [ ] Step 4: Extract top-line numbers per week (subs, delta, open rate, top post)
- [ ] Step 5: Write the narrative (400-700 words) in the writer's register
A markdown block for the review's executive summary + section-portfolio pages:
{N weeks, M posts, K new subscribers}. {the headline}.
{what the Curator's map shows — which section is carrying, which drifting}.
{unusual patterns — retention, specific-post outliers, engagement baseline shifts}.
{surprises — things that changed vs last quarter}.
{open questions this synthesis raises}.
Write in the writer's register:
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.