Home
cd ../playbooks
Knowledge ManagementIntermediate

Tips & Knowledge Curator

Process emails containing tips and insights, assess quality with novelty and credibility ratings, and maintain a curated knowledge log.

15 minutes
By communitySource
#knowledge-management#tips#curation#email#learning#mcp
CLAUDE.md Template

Download this file and place it in your project folder to get started.

# Tips & Knowledge Curator

## Your Role
You process self-sent emails containing tips and insights, assess quality, and maintain a curated knowledge log.

## Required
- Gmail MCP

## Arguments
- `dryrun` — preview without saving or marking emails
- `limit:N` — batch size (default 5)
- `all` — process all unread in loops

## Instructions

### Step 0: Pre-checks
1. Read existing `collected-tips-log.md` to identify duplicates
2. Search for unread emails with the tips label
3. If none found, report "No new tips to process" and stop

### Step 1: Batch Fetch
Fetch up to N emails (default 5). For each, extract:
- Subject line
- Date
- Body text
- Any URLs

Skip emails whose subjects or URLs already appear in the tips log.

### Step 2: Classify and Enrich

Classify each email:
- **worth-reviewing** — contains actionable tips, workflow techniques, or useful patterns
- **not-relevant** — administrative, personal, or general news
- **needs-manual** — insufficient content to evaluate (paywalled, video-only, audio-only)

For worth-reviewing items:
- Fetch linked web content for enrichment
- NEVER attempt to fetch X.com/Twitter URLs (they always fail)
- Skip paywalled content gracefully

### Step 3: Rate Quality

Apply three quality questions:
1. **Novelty**: Genuinely new or repackaged documentation?
2. **Credibility**: Backed by production usage, or engagement-focused?
3. **Applicability**: Solves a real problem in existing workflows?

Rate:
- **High** — Novel + actionable + production-backed → Recommend
- **Medium** — Interesting but may lack direct applicability → Present for review
- **Low** — Already known, superficial, or vague → Treat as not-relevant

### Step 4: Present Recommendations

```
RECOMMENDED ACTIONS:
[Subject] (Rating) — [Key insight]
  Action: [Concrete change]
  Quality: [Credibility note]

SKIP:
[Subject] — [Reason]

NEEDS YOUR HELP:
[Subject] — [Issue: paywalled / video / insufficient]
```

Wait for user approval on which tips to save.

### Step 5: Save and Mark

For approved items:
1. Append to `collected-tips-log.md` with metadata (date, source, rating, insight, action)
2. Mark processed emails as read (except needs-manual items)
3. If `all` argument: loop through remaining batches

## Tips Log Format

```markdown
### [Date] — [Subject/Title]
- **Source:** [URL or email]
- **Rating:** [High/Medium]
- **Insight:** [Key takeaway]
- **Action:** [What to do with it]
```
README.md

What This Does

Processes self-sent emails containing tips, links, and insights. Classifies each one, enriches promising items with web content, rates quality based on novelty and credibility, and builds a curated knowledge log of actionable items.


Prerequisites

  • Gmail MCP (required)
  • A Gmail alias for self-sent tips (e.g., yourname+tips@gmail.com)

Quick Start

Step 1: Set Up Your Email Alias

Start forwarding interesting tips to yourself using a Gmail + alias:

yourname+tips@gmail.com

Gmail delivers these to your inbox with a label you can filter on.

Step 2: Download the Template

Click Download above, then save to your working directory.

Step 3: Run Claude Code

claude

Then: "Curate my tips"


The Curation Workflow

Step What Happens
Pre-check Read existing tips log, count unread tip emails
Batch fetch Retrieve up to N emails (default 5)
Classify Sort as worth-reviewing, not-relevant, or needs-manual
Enrich Fetch linked web content for promising items
Rate quality Score based on novelty, credibility, applicability
Present Show recommendations, wait for approval
Save Append approved items to knowledge log

Quality Rating Criteria

Rating Criteria Action
High Novel, actionable, backed by real usage Recommend saving
Medium Interesting but may lack direct applicability Present for review
Low Already known, superficial, or vague Treat as not-relevant

Three Quality Questions

  1. Novelty — Is this genuinely new or repackaged documentation?
  2. Credibility — Backed by production usage and real results, or engagement bait?
  3. Applicability — Does it solve an actual problem in your workflows?

Output Format

RECOMMENDED ACTIONS:
[Subject] (High) — [Key insight extracted]
  Action: [Concrete change to make]
  Quality: [Credibility note]

SKIP:
[Subject] — [Reason: already known / not relevant]

NEEDS YOUR HELP:
[Subject] — [Paywalled / video-only / can't assess]

Arguments

Flag Effect
dryrun Preview without saving or marking emails
limit:N Batch size (default 5)
all Process all unread tip emails in loops

Tips

  • Send tips to yourself throughout the week — process in batches
  • X.com/Twitter links are skipped — they can't be fetched, save the key insight in the email body instead
  • Paywalled content flagged — marked as "needs-manual" for you to review
  • Deduplication built in — won't re-process tips already in your log
  • Knowledge log grows over time — becomes a personal reference library

Troubleshooting

No emails found Check that your Gmail filter/label is set up correctly for the + alias

Web enrichment failing Some sites block fetching — the tip is still processed, just without enrichment

Too many "needs-manual" items Send the key takeaway in the email body, not just a link

$Related Playbooks