// Generate a weekly newsletter summarizing resources added last week. Use when asked to "weekly newsletter", "newsletter", "what did I add this week", "generate newsletter", or "Monday newsletter".
| name | weekly-newsletter |
| description | Generate a weekly newsletter summarizing resources added last week. Use when asked to "weekly newsletter", "newsletter", "what did I add this week", "generate newsletter", or "Monday newsletter". |
| allowed-tools | Read, Write, Glob, Grep, Bash, AskUserQuestion |
Generate a newsletter summarizing public notes added during the previous week (Mon-Sun), grouped by content type. Designed for Monday publishing.
src/content/notes/newsletter-drafts/Run the CLI script to collect all notes added this week:
node .claude/skills/weekly-newsletter/scripts/collect-weekly-notes.mjs
The script outputs JSON with:
week - ISO week (e.g., "2026-W05")weekStart - Monday dateweekEnd - Sunday datenotes - Array of notes with slug, title, type, summary, url, tagstweets - Array of tweets (if any)For a specific week:
node .claude/skills/weekly-newsletter/scripts/collect-weekly-notes.mjs --week 2026-W04
Organize notes from the JSON output into sections based on their type field:
| Type | Section Header |
|---|---|
| book | Books |
| article | Articles |
| podcast | Podcasts |
| youtube | Videos |
| talk | Talks |
| github | GitHub Repos |
| Reddit Threads | |
| tweet | Tweets |
| newsletter | Newsletter Issues |
| course | Courses |
| movie | Movies |
| tv | TV Shows |
| manga | Manga |
| note | Notes |
| evergreen | Evergreens |
| quote | Quotes |
Only include sections that have content.
---
title: "Weekly Digest: {Week Start} - {Week End}"
date: { Today YYYY-MM-DD }
week: { YYYY-Www }
---
# Weekly Digest
_Resources added {Week Start} - {Week End}_
## Summary
This week I added **{total count}** resources to my knowledge base:
{type counts, e.g., "3 articles, 2 podcasts, 1 book"}
---
## {Section Header}
### [[{note-slug}|{title}]]
{summary or "[No summary]" if missing}
**Tags:** {tags as comma-separated list}
**Source:** {url if present}
---
{repeat for each note in section}
{repeat for each section with content}
---
## Stats
- Total resources: {count}
- Most active type: {type with most entries}
- Top tags: {3 most frequent tags}
[[slug|title]] format for internal referencesPresent the generated newsletter:
question: "Does this newsletter look ready?"
header: "Review"
options:
- label: "Save"
description: "Save to newsletter-drafts folder"
- label: "Edit"
description: "Make changes before saving"
- label: "Regenerate"
description: "Try generating again with different options"
mkdir -p src/content/notes/newsletter-drafts
Filename: {YYYY-Www}.md (ISO week number from JSON output)
Path: src/content/notes/newsletter-drafts/{YYYY-Www}.md
Display:
| Situation | Handling |
|---|---|
| No notes added this week | Inform user, offer to check previous week |
| Week already has newsletter | Offer to overwrite or append |
| Note missing summary | Use "[No summary]" |
| Mixed public/private notes | Script excludes private by default |
Before saving:
YYYY-Www.md format[[slug|title]] formatIngest a new source into the LLM Wiki. Save the full captured resource under src/content/notes/sources/ first, then create or update the maintained wiki summary/synthesis entry, index, and log. Trigger on "add", "save", "capture", "note this", "take notes on", or any request to record content in the knowledge base.
Query the maintained wiki layer first, then fall back to sources when needed. Use when asked to "ask my notes", "what do I know about", "query my knowledge", "/ask", or when the user has a question that the wiki might answer.
Summarize the past week's daily journal entries. Use when asked to "weekly review", "review the week", "summarize this week", or "week summary".
Curate wiki maps and clustering pages for the LLM Wiki. Use when asked to "curate MOCs", "update maps", "find clusters", "what MOCs need updating", or "organize my notes".
Audit the maintained wiki for quality and maintenance issues. Use when asked to "review notes", "check content quality", "audit my knowledge base", or "find broken links".
Add tweets to the Second Brain. Use when the user provides a Twitter/X URL and pasted tweet content, asking to "add a tweet", "save this tweet", or "capture this tweet".