Write Weekly Report
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.
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill write-weekly-reportgit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/write-weekly-report ~/.claude/skills/write-weekly-reportPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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.
Details
- Skill name
write-weekly-report- Repository
- lyndonkl/claude
- Path
skills/write-weekly-report/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Write Weekly Report skill do?
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.
How do I install the Write Weekly Report skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Write Weekly Report popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds 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 Architect
200lyndonkl/claude
Guides 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 Architecture
200lyndonkl/claude
Documents 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.
Writing Pre Publish Checklist
200lyndonkl/claude
Runs a comprehensive six-section quality checklist (content, structure, clarity, style, polish, final tests) before writing is shared or published, catching issues that revision and stickiness enhancement might miss. Use when performing final quality checks before sharing, publishing, or submitting writing, or when user mentions pre-publish, final check, ready to publish, last review, quality check, or about to share.
Write Weekly Digest
200lyndonkl/claude
Renders the Trend Scout ranked keep-and-drop lists into ops/trend-scout/YYYY-WW-digest.md using the agent voice profile and including an appendix of all sources surveyed. Use once per weekly run as the terminal skill. Trigger keywords — weekly digest, write digest, Trend Scout digest, Saturday morning digest.
Writing Revision
200lyndonkl/claude
Applies a systematic three-pass revision system (Zinsser, King, Pinker, Clark) to existing drafts — Pass 1 cuts clutter, Pass 2 reduces cognitive load, Pass 3 improves rhythm. Use when revising, editing, or polishing drafts, cutting word count, tightening prose, improving readability, or fixing flow, or when user mentions revision, editing, cut clutter, too wordy, improve readability, fix the flow, reduce word count.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.