docs: add promotion log to root directory

- Move from docs/ (excluded) to root for public visibility - Track 8 waves of promotion activity across Reddit/X/Linux.do/GitHub - Current: 247 stars, 34 forks, PR #216 open
2026-09-14 19:09:17 +08:00 · 2026-04-12 21:18:25 +08:00
parent d8afa65f3e
commit b67de7e822
1 changed files with 256 additions and 0 deletions
@@ -0,0 +1,256 @@
+# Promotion Log — karpathy-llm-wiki
+
+All touchpoints by wave.
+
+---
+
+## Wave 1 (2026-04-05, comment/reply style)
+
+12 touchpoints:
+- Karpathy gist comment
+- X replies (7): Karpathy 2nd post, Karpathy 3rd post (BYOAI), lugaricano, jumperz, dongxi_nlp, kloss_xyz, DataChaz
+- Reddit comments (4): r/ClaudeCode, r/ClaudeAI, r/Rag, r/claude (skills recommendation post)
+- Jike (Chinese social app): standalone post + manual comment under Guizang's post
+
+## Wave 2 (2026-04-06, expanded coverage)
+
+Reddit new comments:
+- r/ClaudeAI "Vibe code inventor's second brain as a wiki" (92pt post)
+- r/LocalLLaMA "Llm wiki by karpathy" (9pt post)
+- r/ObsidianMD "Karpathy's workflow" (186pt post, wave 1 had earlier comment)
+- r/Rag "Do we actually need embeddings" (51pt post, wave 1 had earlier comment)
+
+X new replies:
+- coreyganim (199K views post, via opencli)
+- PawelHuryn (44K views post, via opencli)
+- jenzhuscott (22K views post, manual)
+
+## Wave 3 (2026-04-07, discussion-first style)
+
+Reddit new comments (all posted via opencli):
+- r/ClaudeCode "71.5x token reduction by compiling your raw folder into a knowledge graph" (843pt post by captainkink07/graphify)
+- r/AskVibecoders "Andrej Karpathy's LLM Knowledge Base system Diagram" (171pt post)
+- r/AI_Agents "Karpathy said there is room for an incredible new product" (85pt post by captainkink07/graphify)
+- r/ClaudeAI reply to fsharpman's response on "Vibe code inventor's second brain" thread (manual)
+
+Skipped (with reason):
+- r/learnmachinelearning "Andrej Karpathy describing our funnel" (174pt) — ModelBrew ad, hostile thread, off-topic
+- r/vibecoding crosspost (78pt) — competitor's promo, late
+- r/ObsidianMD "Implemented Karpathy's LLM knowledge base workflow" (0pt, 14 comments) — community hostile to concept, OP downvoted
+
+## Wave 4 (2026-04-08, follow-up threads + high-view X)
+
+Reddit new comments:
+- r/Rag "s the compile-upfront approach actually better than RAG for personal knowledge bases?" (posted via opencli, verified visible)
+- r/learnmachinelearning "Andrej Karpathy describing our funnel" (posted via opencli, verified visible)
+
+X new replies:
+- berryxia (57K views Chinese post)
+- akokoi1 (11K views Chinese post)
+- minchoi (161K views post)
+- karpathy reply on reading/thinking (84K views post)
+
+GitHub surface improvements:
+- Enabled GitHub Discussions
+- Added discovery topics: agent-skill, claude-code, codex, cursor, knowledge-base, llm, wiki
+- Created starter discussion thread for questions/examples/feedback
+
+## Wave 5 (2026-04-08, awesome-list submissions)
+
+GitHub awesome-list actions:
+- Opened PR: BehiSecc/awesome-claude-skills [#216], add `karpathy-llm-wiki` under Learning & Knowledge
+- Prepared manual-only submission package for travisvn/awesome-claude-skills
+- Prepared issue-form package for hesreallyhim/awesome-claude-code, earliest safe submit date: 2026-04-12 (ready to submit)
+
+Skipped or downgraded:
+- travisvn/awesome-claude-skills — explicit no AI-assisted PR rule, plus 100+ open PR backlog and one already-open similar “knowledge base compiler” PR
+- ComposioHQ/awesome-claude-skills — higher effort, requires vendoring a skill folder into their repo, not just adding an external link
+- kmaasrud/awesome-obsidian — weak fit, markdown-compatible but not primarily an Obsidian project
+
+## Wave 6 (2026-04-10, question-first Reddit threads)
+
+Reddit new comments (all posted via opencli, verified visible):
+- r/CRM "Can CRM be a collection of Markdown files?"
+- r/ClaudeAI "Llm wiki setup for Cowork users"
+- r/Rag "Is there anyone actually using a graph database?"
+- r/ClaudeAI "As a beginner with limited coding experience, all these GitHub’s about making Claude more efficient and cost less, how can I determine what’s safe to add and what’s malware?"
+- r/ClaudeAI "Claude and Obsidian for Second Brain"
+- r/AI_Agents "whats the best intersection of browser agents and knowledge bases?"
+
+Scan result:
+- X had no strong fresh clean target, mostly small explainers or competitor/product threads
+- Hacker News had no strong live opening, mostly older LLM wiki results or unrelated new posts
+
+## Coverage summary (as of wave 8)
+
+### Reddit — commented
+r/ClaudeCode x2, r/ClaudeAI x5 (+ fsharpman reply), r/Rag x4, r/claude, r/ObsidianMD, r/LocalLLaMA, r/AskVibecoders, r/AI_Agents x2, r/learnmachinelearning x2, r/CRM
+
+### Reddit — not commented (no good threads found or skipped due to competitor saturation)
+r/selfhosted, r/artificial, r/MachineLearning, r/pkm, r/Zettelkasten, r/productivity, r/ClaudeCode (saturated by Graphify), r/ObsidianMD (saturated by atomicmemory)
+
+### X — replied
+Karpathy x3, jumperz, kloss_xyz, DataChaz, coreyganim, PawelHuryn, jenzhuscott, lugaricano, dongxi_nlp, berryxia, akokoi1, minchoi, lxfater, tom_doerr, MushtaqBilalPhD
+
+### X — unreplied high-view posts
+alliekmiller (37K views "Claudeopedia"), garrytan (66K views YC president), elvissun (29K views)
+
+### Other platforms
+Karpathy gist comment, Jike x2, Linux.do x4
+
+### GitHub — ready to submit
+hesreallyhim/awesome-claude-code (37K stars, ready to submit via web UI issue form)
+
+### GitHub — active / prepared
+BehiSecc/awesome-claude-skills (8K stars, PR #216 open), travisvn/awesome-claude-skills (10K stars, manual-only package prepared, low priority), ComposioHQ/awesome-claude-skills (51K stars, optional higher-effort mirror submission), hesreallyhim/awesome-claude-code (37K stars, ready to submit)
+
+### Milestone
+- Crossed 100 stars on 2026-04-08
+- Crossed 200 stars on 2026-04-10
+- Current: 245 stars, 31 forks (2026-04-12)
+
+### Not yet tried
+Show HN standalone post, dev.to article
+
+## Wave 7 prep (prepared 2026-04-10, not yet executed)
+
+### Strategy shift
+
+Waves 1 through 6 were mostly comment and reply driven. That gave broad coverage across Reddit and X, plus one active awesome-list PR. As of 2026-04-12, the repo is at **245 stars** and **31 forks**, which is enough social proof to support a stronger owned-post round instead of another broad reply sweep.
+
+Recommended focus:
+- higher-intent discovery, not just opportunistic replies
+- clearer explanation of the workflow, not just the repo link
+- surfaces that can keep compounding after the initial post
+
+### Recommended channels
+
+Tier 1:
+- Show HN standalone post
+- dev.to article
+- V2EX post
+- `awesome-claude-code` manual submission on or after **2026-04-12**
+
+Tier 2:
+- Fresh Reddit threads in `r/pkm`, `r/productivity`, and `r/selfhosted` only when the thread is clearly about markdown knowledge bases, second brains, Obsidian, or AI-assisted note systems
+- Selective X replies only when the post is directly about personal knowledge systems, markdown workflows, or Karpathy's wiki idea
+
+### Message angle
+
+Lead with:
+- markdown-first workflow
+- raw sources compiled into a maintained personal wiki
+- readable artifacts in `raw/` and `wiki/`
+- portable across Claude Code, Cursor, Codex, and other Agent Skills tools
+
+Avoid leading with:
+- "another skill repo"
+- "RAG replacement"
+- generic agent or automation language
+
+### Ready drafts
+
+Show HN title:
+- `Show HN: karpathy-llm-wiki, a markdown-first workflow for building a personal LLM wiki`
+
+Show HN post opener:
+
+> I turned Andrej Karpathy's recent "LLM wiki" idea into a reusable skill and markdown workflow.
+>
+> The core pattern is simple:
+> - source material goes into `raw/`
+> - the LLM compiles and maintains `wiki/`
+> - queries are answered from the wiki, with citations
+> - linting keeps links, index entries, and cross-references healthy
+
+dev.to title:
+- `I turned Karpathy's LLM wiki idea into a reusable markdown workflow`
+
+dev.to opening:
+
+> Andrej Karpathy recently described an "LLM wiki" workflow where the LLM writes and maintains a personal wiki while the human mainly reads it and asks questions. I liked the idea because it shifts the output from chat transcripts to durable files. So I packaged the pattern into a reusable skill: sources go into `raw/`, knowledge gets compiled into `wiki/`, and the system keeps an index and log as the knowledge base grows.
+
+V2EX title:
+- `把 Karpathy 的 LLM Wiki 想法做成了一个可复用的 markdown 工作流`
+
+V2EX opener:
+
+> 最近 Karpathy 提了一个很有意思的想法，不是把 LLM 当聊天窗口，而是让它持续维护一个个人 wiki。
+>
+> 我把这个流程整理成了一个可复用的 skill / workflow：
+> - 原始资料放进 `raw/`
+> - LLM 把知识编译进 `wiki/`
+> - 查询时优先从 wiki 回答，并带引用
+> - 还能做 lint，检查链接、索引、交叉引用
+
+### Execution order
+
+1. Publish the dev.to article first so there is a durable explainer to link elsewhere
+2. Prepare the Show HN post and first comment in advance, then wait for a good posting window
+3. Publish the V2EX post with practical framing and less launch language
+4. Submit to `awesome-claude-code` (ready now), using the package in `docs/AWESOME_SUBMISSIONS.md`
+5. Use selective Reddit or X replies only to support the owned posts, not as the main event
+
+## Wave 7 (2026-04-10, Linux.do + Reddit + X follow-through)
+
+Reddit new comments (all posted via opencli):
+- r/LocalLLaMA "Anyone know if there are actual products built around Karpathy’s LLM Wiki idea?"
+- r/AI_Agents "How should I go about creating a Wiki for software system, as suggested by Andrej Karpathy?"
+- r/selfhosted "I built a 'Wiki Warden' on a local 3090 to automate my docs"
+- r/ClaudeAI "My Claude.md file"
+- r/ClaudeAI "Best way to get persistent memory in Claude right now (Apr 2026)? Practical setups?"
+
+Linux.do new replies:
+- `1934381` "LLM Wiki \"vibe coding\" 创造者 Andrej Karpathy 提出的“新”工作流"
+- `1921300` "Karpathy 的 LLM-wiki 实践"
+- `1907342` "把一堆乱七八糟的笔记，变成一个会自己生长的知识库-Karpathy"
+- `1944092` "LLM Wiki这个思路确实很强，怎么快速把我的语雀笔记和飞书笔记导入到llm wiki的raw文件夹"
+
+X new actions:
+- Posted milestone tweet after crossing 200 stars
+- Replied to eng_khairallah1's Graphify thread with a graph-vs-wiki distinction
+- User manually posted the follow-up repo reply under that thread
+- User manually posted selected drafted X replies, including devjuninho
+- Replied to lxfater (Chinese tutorial post), tom_doerr (Claude Code guidelines), MushtaqBilalPhD (18M+ views viral post)
+
+Channel updates:
+- Linux.do replaced V2EX in the practical plan because the user has a Linux.do account and no V2EX account
+- Dev.to still looks like the best remaining "other channel" for comments or an owned explainer post
+- Hacker News still looks better as a standalone Show HN than as a reply surface
+- Competitor saturation on Reddit/X reply threads means owned posts (Show HN, dev.to) are now higher priority than reply sweeps
+
+## Wave 8 (2026-04-11, targeted replies + high-signal threads)
+
+X new replies (all via opencli or manual):
+- lxfater (95K followers, 7K+ views, Chinese post about Obsidian + Claude Code Karpathy wiki tutorial)
+- tom_doerr (Claude Code guidelines based on Karpathy's LLM observations)
+- MushtaqBilalPhD (Karpathy's idea went viral 18M+ views, step-by-step tutorial for non-technical folks)
+
+Reddit new comments (all posted via opencli):
+- r/AskVibecoders "Andrej Karpathy's LLM Knowledge Base system Diagram" (293pt post)
+- r/learnmachinelearning "Karpathy's LLM Wiki and why it feels kind of a game changer" (120pt post, OP explicitly asked for GitHub repos)
+
+Linux.do new replies:
+- `1944092` "LLM Wiki这个思路确实很强，怎么快速把我的语雀笔记和飞书笔记导入到llm wiki的raw文件夹" (answered import workflow question)
+
+Scan results:
+- Competitor Graphify (captainkink07) and atomicmemory/llm-wiki-compiler are actively pushing across Reddit and X. We avoided direct confrontation and focused on workflow differentiation (markdown-first, maintenance automation, no knowledge graph overhead).
+- r/ObsidianMD and r/ClaudeCode threads heavily saturated by competitor promo. Skipped to avoid "repo war" perception.
+
+Coverage updates:
+- Reddit: +r/AskVibecoders, +r/learnmachinelearning
+- X: +lxfater, +tom_doerr, +MushtaqBilalPhD
+- Linux.do: +1944092 (Yuque/Feishu import workflow)
+
+## Current status snapshot (2026-04-12)
+
+- Repo status: **245 stars**, **31 forks**
+- GitHub list status: BehiSecc/awesome-claude-skills [#216] still **OPEN**, hesreallyhim/awesome-claude-code ready to submit
+- Current best owned-post opportunities: Show HN, dev.to article, awesome-claude-code submission
+- Strategy: Competitors are flooding reply threads. Next wave should pivot to owned posts (Show HN, dev.to article) to establish narrative control rather than chasing comment sections.
+
+## Notes
+
+- The milestone tweet was posted when the repo had just crossed 200 stars. Current verified count is now 245.
+- `docs/` is still excluded by `.git/info/exclude`, so this promotion log remains local-only unless the exclude rule changes.
+- Competitor activity (Graphify, atomicmemory) is high. Avoid direct thread overlap; focus on workflow differentiation and owned content.