feat(skills): add email-curator and hugo-post-writer skills

cowork-complete-guide/skills/email-curator.md

@@ -0,0 +1,46 @@
+# Skill: Email Curator
+
+## Purpose
+Scan a batch of emails and identify which ones are worth turning into a blog post. Filters for tech, AI, and Java/Go content that is genuinely interesting — not just any email on the topic.
+
+## Trigger
+Use this when Tien wants to go through his emails and find the ones worth writing about.
+
+## Input
+A list or dump of emails — can be:
+- Pasted email content directly in the chat
+- A text file with multiple emails
+- A folder of .txt or .eml files
+
+## What "Interesting" Means for Tien
+An email is interesting if it contains:
+- **AI/ML news** – new models, research, tools, surprising capabilities or limitations
+- **Java or Go** – language updates, patterns, libraries, performance tips, ecosystem news
+- **Tech industry** – engineering culture, system design, developer tools, open source
+- **"Huh, I didn't know that"** signal – something surprising, counterintuitive, or newly discovered
+
+Skip emails that are:
+- Purely promotional/sales
+- Generic newsletters with no depth
+- Already well-known news with nothing new to add
+
+## Output
+A curated shortlist formatted like this:
+
+---
+**Interesting Emails for [Date]**
+
+1. **[Subject or derived title]**
+   - Source: [sender/newsletter name]
+   - Why interesting: [1–2 sentences on what makes it worth writing about]
+   - Key idea: [The core point in one sentence]
+
+2. [repeat for each interesting email]
+
+---
+Skipped: [count] emails (not relevant or not interesting enough)
+
+## Notes
+- Aim for quality over quantity — 2–5 good picks per batch is ideal
+- If unsure, err toward including it (Tien can decide)
+- Don't summarize everything — just enough to jog memory when writing the post

cowork-complete-guide/skills/hugo-post-writer.md

@@ -0,0 +1,63 @@
+# Skill: Hugo Post Writer
+
+## Purpose
+Turn a curated list of interesting emails into a Hugo blog draft — ready to drop into the content folder and release when enough drafts have accumulated.
+
+## Trigger
+Use this after running the Email Curator skill, or when Tien has a set of interesting emails he wants turned into a post.
+
+## Input
+- The curated email shortlist from the Email Curator skill, OR
+- Raw interesting emails pasted directly
+
+## Output
+A Hugo markdown file with proper frontmatter, saved as a draft.
+
+## Hugo Frontmatter Format
+```markdown
+---
+title: "[Generated title]"
+date: [today's date in YYYY-MM-DD format]
+draft: true
+tags: [relevant tags from: ai, java, go, tech, engineering]
+---
+```
+
+## Post Structure
+
+### 1. The Intro (most important part)
+Write an interesting, opinionated opening — NOT a summary. Options:
+- Start with a provocative question
+- Start with a surprising fact from one of the emails
+- Start with a short personal take ("I've been thinking about X...")
+- Make it feel like something Tien would actually say, not a newsletter blurb
+
+Aim for 2–3 sentences max. Make the reader want to keep going.
+
+### 2. The Items
+For each curated email, write a short section:
+
+**[Topic title]**
+2–4 sentences covering: what it is, why it matters, and optionally a quick personal angle or question it raises.
+
+Keep each item punchy. No padding.
+
+### 3. Closing (optional)
+If there's a natural thread connecting the items, end with a one-liner that ties them together. Skip if it feels forced.
+
+## Tone
+- Conversational, not formal
+- Direct — say what's interesting, don't hedge
+- Tech-native — no need to explain what Java or LLMs are
+- Tien's voice, not a content marketer's voice
+
+## File Naming
+`[YYYY-MM-DD]-digest.md`
+Example: `2026-03-10-digest.md`
+
+Save to: the Hugo content/posts folder (or ask Tien where if unsure)
+
+## Notes
+- Draft = true always. Tien releases manually when he has enough posts.
+- If only 1–2 items, still write it — small posts are fine
+- If something has a natural headline moment (big release, surprising news), lean into it in the intro