with one click
adding-tweets
// 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".
// 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".
| name | adding-tweets |
| description | 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". |
| allowed-tools | Read, Write, Bash, Glob, Grep, Task, TaskOutput, WebSearch, AskUserQuestion |
Add tweets with author linking, tags, and personal annotations.
User provides:
x.com/*/status/* or twitter.com/*/status/*Example user input:
add this tweet https://x.com/naval/status/1234567890
my favorite way to use Claude Code is spec based
start with a minimal spec and ask Claude to interview you
Phase 1: Parse URL → Extract tweet ID and author handle
Phase 2: Parse Content → Extract text, date, author name from paste
Phase 3: Author Resolution → Check/create author profile
Phase 4: Generate Tweet File → Write to src/content/notes/tweets/
Phase 5: Suggest Editing → Tags, annotations, wiki-links
Phase 6: Quality Check → Run vp run check
Extract from URL using regex:
tweetId: The numeric ID from /status/{id}authorHandle: The username from x.com/{username}/status/Pattern: (?:x\.com|twitter\.com)/([^/]+)/status/(\d+)
Example: https://x.com/naval/status/1789234567890
→ authorHandle: "naval"
→ tweetId: "1789234567890"
From the pasted text:
If critical info is missing, use the AskUserQuestion tool to gather it:
question: "I need some missing tweet info. What is the tweet text?"
header: "Tweet Info"
multiSelect: false
options:
- label: "I'll provide it"
description: "Let me paste the tweet content"
For optional fields like date, ask separately if needed.
Check if author exists:
ls src/content/notes/authors/{authorHandle}.md
If not exists, create minimal profile:
---
name: "{Display Name or Handle}"
slug: { authorHandle }
socials:
twitter: "https://x.com/{authorHandle}"
---
For full author enhancement, suggest running /enhance-author {authorHandle}
Slug format: tweet-{tweetId}
File path: src/content/notes/tweets/tweet-{tweetId}.md
Frontmatter template:
---
type: tweet
title: "{First 50 chars of tweet}..."
tweetId: "{tweetId}"
tweetUrl: "{originalUrl}"
tweetText: "{full tweet text}"
author: { authorHandle }
tweetedAt: { YYYY-MM-DD }
tags:
- { suggested tags }
---
{ User's personal annotations go here }
After saving, inform user:
.claude/skills/adding-notes/scripts/list-existing-tags.sh for suggestions)Based on tweet content, suggest from existing tags:
.claude/skills/adding-notes/scripts/list-existing-tags.sh
Common tweet themes → tags:
mindset, philosophystartup, businesstech, programmingproductivity, habitclaude-code, ai-agents, prompt-engineeringBefore saving, verify:
tweetedAt is valid date formattweetText is not emptyRun linter and type check to catch any issues:
vp run check
If errors are found, fix them before completing the task.
Ingest 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".
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".