weekly-digest

After a reconcile run surfaces the week’s themes, this skill ghostwrites 0-n private articles in the user’s voice — first-person posts about what’s been on their mind, grounded in the week’s vault activity. The user reads them like personal blog posts they might have written themselves.

When to use

• Automatically, as the final step of reconcile (after the report is written).
• User runs /weekly-digest manually.
• User says “write digest posts for this week.”

Where posts live

6_Private/Digest/. One file per article:

6_Private/Digest/YYYY-Www-<topic-slug>.md

Example: 6_Private/Digest/2026-W19-concurrency-rabbit-hole.md

Workflow

1. Gather material

Use the reconcile report (or run recent-changes if invoked standalone) to identify the week’s touched-set. Read the actual pages — not just filenames — to understand what was added or changed.

2. Identify post-worthy themes

Not everything deserves a post. Apply editorial judgment:

Write about:

• A topic that received sustained attention (multiple notes, edits, or cross-references this week).
• A problem the user is clearly wrestling with — especially if the vault shows the thinking evolving.
• A project that hit a milestone or shifted direction.
• An interesting tension or connection between topics that emerged this week.
• A personal reflection or decision that the vault captured.

Skip:

• Mechanical changes (folder moves, frontmatter fixes, link cleanup).
• Topics that only got a single shallow mention.
• Things that were just clipped/ingested but not engaged with yet.

Aim for 1–3 posts in a typical week. Zero is fine if the week was quiet or purely mechanical. More than 3 is unusual — consolidate themes rather than writing many thin posts.

3. Check for prior digests on the same topic

ls 6_Private/Digest/

If a post on the same theme exists from the last ~4 weeks:

• Don’t rewrite from scratch. Instead, write a follow-up that references the earlier post ([[YYYY-Www-slug]]) and builds on it — what changed, what progressed, what shifted.
• If nothing meaningful changed since the last post on that topic, skip it this week.

4. Load voice references

Before drafting, invoke the write-post skill to load the essay-style voice signatures. Read at least one reference post from Posts tagged essay-style. The digest must sound like the user’s real writing, not like an LLM summary.

5. Write each post

Voice: Ghostwrite as the user. Essay-style, first person. The post reads like the user sat down and wrote about what’s actually on their mind — not like an agent summarizing what it found in the vault.

Key principles:

• Organize around ideas, not sources. Each paragraph advances an observation, a claim, or a scene. The vault notes are raw material — the post is a new piece of writing that happens to draw on them. You do not have to account for every note. Most of the week’s memos should leave no visible trace — only the ideas survive into the essay. If a paragraph exists mainly to register that a note happened (or when it was recorded), cut it.
• Grounded means the thoughts are real — every emotion, opinion, or conclusion traces back to something the user actually expressed in the vault this week. It does not mean “cite your sources.” Never invent feelings or thoughts the user didn’t express.
• Connective. The value is in drawing threads between things the user might not have connected themselves.
• No wikilinks in the body. The prose reads clean, like a blog post. Collect related vault pages in a ## References bullet list at the end — that’s where the graph connectivity lives. Keep References lean: link the few pages a reader would actually want to follow (roughly 3–8), not every memo the week touched. A 15-link reference dump is the “account for every note” instinct leaking out the bottom of the post.
• Open with a scene, observation, or tension — never with “This week I…” or “I’ve been thinking about…” A bare clock time (“Friday, 2:42 PM, I record the crisis”) is not a scene — it’s a log entry. Open with something that happened, not with when you pressed record.
• Short paragraphs. Often one or two sentences. Let the white space do work.

Structure of a post:

---
created: YYYY-MM-DD
lang: en
tags: [digest, <topic-tags>]
source: derived
draft: true
week: YYYY-Www
---
 
<article body — no title heading needed, the filename is the title>
 
## References
 
- [[related-page-1]]
- [[related-page-2]]

Rules for content:

• The thoughts and feelings must come from actual vault content. You may add connections, examples, or context that weren’t explicitly stated — drawing new threads is part of the value — but never invent emotions or opinions.
• Keep the body free of wikilinks. Collect related pages in a ## References section at the end.
• Always write in English. Even when the source material is in German or Japanese, the digest is English. Absorb the material, don’t transliterate it — if a German phrase captures something that English can’t, leave it as-is, but the surrounding prose is English. No code-switching mid-paragraph.
• No inline wikilinks in the body. The vault notes are raw material; the digest is the distilled version. If you want to link to related pages, collect them in a ## References bullet list at the end. The body text stands on its own.

Anti-patterns:

• Source-organized paragraphs. “In the May 1 memo, I said X. In the May 3 memo, I said Y.” This is a summary, not an essay. Restructure: lead with the observation, weave in the detail.
• Recording-log recap — the timestamp form of the same sin, and the one that keeps creeping back. Walking through the day’s voice memos in the order they were recorded, with clock times as the spine: “Friday, 2:42 PM, I record the crisis. Forty seconds later I record the backstory. Ten minutes after that, the plan. At 1:44 AM I’m back.” Dropping the [[wikilinks]] does not fix this — it is still organized around the making of the notes, not around ideas, and it reads like a transcript of a recording session with insights sprinkled between. Symptoms: clock times or “I record/wrote/jotted X” as paragraph openers; one memo per beat; “six positions in thirteen hours” framings that secretly map one source note to one paragraph; an arc narrated date-by-date (“May 26… the next day… then May 28…”). Fix: throw the timeline away. Find the one or two ideas the day actually produced and build the essay around those. A timestamp earns its place only as part of a lived scene (“5 AM, couldn’t sleep”), never as a citation for when a thought got logged.
• Changelog voice. “This week, the vault saw activity in…” — write an article, not a diff.
• Third-person references. “The user seems to feel…”, “Alex has been working on…” — this is first-person ghostwriting.
• Forced narrative arc. If the week’s notes don’t tell a story, write separate observations. Don’t manufacture coherence.
• Inventory paragraphs. Listing several small observations in a row (“the cigarette smoke, the vomit, the trash heap, the rule-breaking corners”) to jam them into the post. If a detail doesn’t earn its own sentence in context, drop it. The notes are material, not a checklist to exhaust.
• Agent-brain details. Facts the agent noticed while cross-referencing (a number mismatch between two notes, a date discrepancy, a metadata inconsistency) don’t belong in a diary-style post. The user wouldn’t write “I noticed I said 25h in one place and 30h in another.” That’s an observation about the vault, not about life.
• Rehashing the reconcile report. The report is a checklist; the digest is a read.
• “As I wrote in X…” / “I mentioned in Y…” — the reader doesn’t care about the agent’s research trail. Write about the idea, not where you found it.
• Language mixing. Don’t alternate between English and German/Japanese mid-paragraph. The digest is English. A single untranslatable phrase is fine; a sentence in German followed by one in English is not.

Before vs. After:

Bad (summary structure — paragraphs organized around source notes):

In the May 1 memo, the Airbnb area is described as grim. In the May 3 memo, the coworking space has acquired an antagonist. In the friend update, the tone is upbeat.

Good (essay structure — paragraphs organized around the observation, no inline links, English throughout):

Both versions are true. That’s the part that lands when I read them next to each other. The friend-update isn’t a lie — the Airbnb really is modern, the coworking space really does have nice people. I selected one half and sent that. The voice memos aren’t a lie either. I selected the other half and recorded that.

References

• 2026-05-01-Airbnb area shame, hairstyle pending, and 10ten leadership doubts
• 2026-05-02-One month in Japan update - coworking, 25h job, Golden Week

Bad (recording-log structure — paragraphs organized around when each memo was recorded):

Friday afternoon, 2:42 PM, I record the crisis. Forty seconds later I record the backstory. Ten minutes after that, the plan. Then nothing for eleven hours. At 1:44 AM I’m back. At 6:04 AM I record the patience pole.

Good (idea structure — the timeline thrown away, built around what the day produced):

The previous versions of this crisis had been one voice running the same loop. This one had six voices arguing — vibe against understanding, obligation against authenticity. The day didn’t hand me a decision; it handed me a vocabulary, and a compromise that keeps the exit warm.

6. Log

Append to log:

## [YYYY-MM-DD] weekly-digest | Week YYYY-Www
- Posts written: N
- Topics: <comma-separated list>
- Skipped topics: <any themes considered but dropped, with one-word reason>

Integration with reconcile

In the reconcile workflow, this skill runs after step 8 (Notify). It is a self-contained final step:

1. Reconcile completes its report + notification.
2. weekly-digest reads the report + the actual touched pages.
3. Writes 0-n digest posts.
4. Logs the run.

If reconcile had an empty diff (no activity), skip the digest entirely.

Rules

• 0 posts is valid. Don’t force content.
• No fabricated emotions or thoughts. Grounded in vault content only.
• Private by design. All posts get draft: true and live in 6_Private/. Never route these to a public location.
• Don’t duplicate. Check prior digests before writing. Build on existing posts rather than repeating.
• Don’t cover everything. A post about one well-developed theme beats three shallow posts about everything that happened.
• Essay, not summary. Organize around ideas. No inline wikilinks — references go at the end. Never reproduce vault content wholesale.
• English only. Source material may be German/Japanese; the digest is always English. Keep a foreign phrase only when it’s untranslatable.

Verification

• Posts exist in 6_Private/Digest/ with conformant frontmatter (lang: en).
• Body text contains zero [[wikilinks]]. All links are in the ## References section at the end.
• Body text is English throughout (stray foreign phrases only where untranslatable).
• Paragraphs are organized around ideas/observations — no paragraph opens with “In source-note…”
• The post reads like an essay the user wrote, not a summary an agent compiled.
• No paragraph is organized around when a note was recorded. No clock-time or “I record/wrote/jotted X” paragraph openers; the day’s timeline is not the essay’s spine.
• The ## References list is lean (roughly 3–8 links), not an exhaustive dump of every memo touched.
• No post covers a topic already covered in a digest from the past 4 weeks (unless it’s explicitly a follow-up that references the prior post).
• log has the entry.
• No pages outside 6_Private/Digest/ and 7_Agent/log were modified.