write-weekly-report
$
npx mdskill add lyndonkl/claude/write-weekly-reportSynthesizes weekly analytics into a concise, formatted report.
- Generates final markdown reports from upstream data sources.
- Integrates ingest, baseline, and public-page outputs.
- Applies truncation logic to meet strict word budgets.
- Delivers YAML-frontmatter and seven-section markdown files.
SKILL.md
.github/skills/write-weekly-reportView on GitHub ↗
--- name: write-weekly-report description: Composes the substacker final ops/growth-analyst/YYYY-WW-report.md from ingest + baseline + attribute + per-section + public-page outputs. Enforces 400-800 word budget, YAML frontmatter schema, seven-section body structure. Truncates weakest sections first when over budget. Injects data-caveats from any degraded-mode flags upstream. Use as the final compose step of the weekly pipeline. Trigger keywords: weekly report, compose report, growth report, Monday report. --- # Write Weekly Report ## Workflow ``` Compose weekly report: - [ ] Step 1: Receive outputs from all upstream skills - [ ] Step 2: Draft YAML frontmatter (week, coverage, csv_source, subs, baselines, one_number_to_watch, confidence) - [ ] Step 3: Draft body in 7 sections (see format) - [ ] Step 4: Count words; if >800, truncate weakest sections first - [ ] Step 5: Voice-check pass (no vanity phrases, no AI-slop openers) - [ ] Step 6: Write file ``` ## Output schema ```markdown --- week: YYYY-WW reported_on: YYYY-MM-DD coverage: YYYY-MM-DD to YYYY-MM-DD publication: the-thinkers-notebook csv_source: inbox/substack-stats/substack-stats-YYYY-MM-DD.csv subscribers_start: N subscribers_end: N delta_subscribers: N open_rate_week: 0.NN open_rate_baseline_4w: 0.NN click_rate_week: 0.NN click_rate_baseline_4w: 0.NN posts_sent_this_week: N one_number_to_watch: subscribers confidence: high | medium | low --- ## Headline 1-2 sentences. The single thing worth knowing. ## Numbers in context Subs, delta, open rate, click rate paired with 4-week rolling. No external comparisons. ## What worked / what didn't Per outlier post: plain-English attribution with confidence label. ## Per section Only if sections populated. Table + 1-2 sentence narrative per section. ## Hypothesis for next week 1-2 specific, falsifiable things to test. ## Data caveats Missing columns, low-N warnings. Mandatory — say "no caveats" if empty. ``` ## Word budget Target 400–800 words. Hard ceiling 800. Truncation priority (drop first if over 800): 1. Per-section narrative (keep table; drop prose) 2. Data caveats (keep 1-line summary; move detail to a linked stub) 3. Numbers in context (tighten to single table) 4. Attribution (keep outliers, drop near-baseline posts) ## Voice rules - No "went viral" / "crushed it" / "blew up" / "massive week" - Use "overperformed by Xσ" / "breakout post" / "high-z outlier" - Anti-vanity framing throughout - `confidence: high` is rare — earn it with ≥2 channels converging ## Guardrails 1. Hard cap 800 words. 2. Every section present even if empty — mandatory schema. 3. No narrative where the underlying numbers are noise. In a quiet week, "A quiet, in-baseline week — nothing moved meaningfully" is the honest story. 4. Data caveats section is always present. 5. Voice-check pass before writing. 6. Frontmatter fields required: week, subscribers_start, subscribers_end, open/click rate + baselines, one_number_to_watch, confidence.
More from lyndonkl/claude
- abstraction-concrete-examplesBuilds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
- academic-letter-architectGuides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
- adr-architectureDocuments significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
- adverse-selection-priorProduces a Bayesian prior probability that an offered transaction is +EV for the recipient, given that the counterparty chose to propose it. Applies Akerlof market-for-lemons logic -- if they offered it, they believe it is +EV for them, so the prior that it is +EV for us is materially below 50%. Reusable across trade evaluation, waiver drops (another team dropping a player is also adverse selection), job-offer analysis, M&A, and any "someone offered me this" situation. Use when you receive an unsolicited trade/offer/proposal, analyzing incoming trade prior, evaluating why a counterparty proposed a deal, or when user mentions adverse selection, market for lemons, why did they offer this, incoming trade prior, they proposed it, Bayesian adjustment on received offer.
- alignment-values-north-starCreates actionable alignment frameworks that give teams a shared North Star (direction), values (guardrails), and decision tenets (behavioral standards). Enables autonomous decision-making while maintaining organizational coherence. Use when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
- analogy-weight-checkFor every analogy in a substacker draft, verifies it carries mechanical weight — the analogy does real work explaining the mechanism, not merely decorates it. Cross-references analogy-catalog.md for novelty (is this analogy reused from a prior post?) and domain fit (biology > organizational > sports preferred; physics/military disfavored). Use whenever an analogy appears in the draft. Trigger keywords: analogy weight, decorative, mechanical weight, reused analogy, catalog check, metaphor check.
- answer-uncomfortable-questionTakes one strategic question about substacker ("should we launch paid?", "is this section dead?", "are we writing for the wrong audience?") and produces the mandatory evidence + reasoning + downside triad plus a recommendation. Used 3 times per Growth Strategist review. Trigger keywords: uncomfortable question, strategic question, evidence reasoning downside, triad.
- attribute-performanceFor each substacker post that materially over- or under-performs the rolling baseline (|z| ≥ 1.0), produces a plain-English attribution paragraph with calibrated confidence (high / medium / low / unexplained). Considers subject-line effect, topic zeitgeist, external share, day-of-week, length effect, and audience-notes signals. Labels unexplained outliers explicitly rather than fabricating a story. Use after compute-baseline when outlier posts exist. Trigger keywords: attribution, why did this post work, outlier explanation, performance analysis.
- auction-first-price-shadingComputes the optimal shaded bid for a first-price sealed-bid auction given a true private value, an estimate of the number of competing bidders N, and a value-distribution assumption. Implements the `(N-1)/N` equilibrium shading rule for uniform private values, adjusts for log-normal or empirical value distributions, layers a risk-aversion adjustment, and caps output against the bidder's remaining budget. Domain-neutral auction theory reusable across fantasy sports (baseball FAAB, NBA/NHL waiver auctions), prediction-market limit sizing, sealed procurement bids, and any blind-bid context. Use when user mentions "first-price auction bid", "sealed bid shading", "(N-1)/N", "FAAB bid amount", "auction shading", "optimal bid first-price", "bid for sealed-bid", "blind bid sizing", or when downstream logic needs a principled shade factor rather than an ad-hoc heuristic.
- auction-winners-curse-haircutApplies a Bayesian haircut to a bid valuation for common-value auctions where winning is itself evidence the bidder over-estimated. Takes a raw valuation, a value-type classification (common_value / private_value / mixed), the number of informed bidders N, and a signal-dispersion estimate, and returns an adjusted valuation. Domain-neutral and reusable across fantasy FAAB, prediction markets, M&A bids, ad-auction budgets, and any generic bidding context. Use when user mentions "winner's curse", "common value auction", "valuation haircut", "adverse valuation", "Bayesian bid adjustment", or "over-paying in auction".