{"skill":{"slug":"pkm","displayName":"Personal Knowledge Base","summary":"Help users build a personal knowledge base by organizing whatever they send into structured notes.","description":"---\nname: Personal Knowledge Base\ndescription: Help users build a personal knowledge base by organizing whatever they send into structured notes.\nmetadata: {\"clawdbot\":{\"emoji\":\"🧠\",\"os\":[\"linux\",\"darwin\",\"win32\"]}}\n---\n\n## Core Behavior\n- User sends anything: link, idea, quote, snippet, question, rambling thought\n- Capture first, organize second — never lose input while deciding where it goes\n- Create `~/kb/` as the workspace — flat folder of Markdown files initially\n- Inbox pattern: `inbox.md` for quick capture, process later into proper notes\n\n## When User Sends Content\n- Link → fetch title and summary, save with source URL and capture date\n- Idea/thought → save as atomic note with descriptive filename\n- Quote → save with attribution, link to source if available\n- Question → save as note, mark for future research\n- Long rambling → extract key points, save as separate atomic notes\n\n## File Naming Convention\n- Lowercase with hyphens: `how-to-negotiate-salary.md`\n- Descriptive over date-based — findable by topic, not when captured\n- No rigid hierarchy initially — flat folder with good names beats complex structure\n- Date prefix optional for journals: `2024-01-15-weekly-review.md`\n\n## Note Structure\n- Title as H1 — matches filename concept\n- Tags at top or bottom — `#productivity #career` for filtering\n- Source/reference if applicable — where it came from\n- Related notes section — manual links build knowledge graph\n- Keep notes atomic — one concept per note, link between them\n\n## Inbox Processing\n- Periodically ask: \"Want to process your inbox?\"\n- For each item: create proper note, add tags, link to related notes\n- Delete from inbox once processed — inbox should trend toward empty\n- Don't force immediate organization — capture friction kills usage\n\n## When To Add Structure\n- 20+ notes: suggest consistent tagging system\n- 50+ notes: suggest index.md or MOC (Map of Content) for key topics\n- 100+ notes: suggest folder structure by domain if patterns emerge\n- Only add structure when navigation becomes painful\n\n## Tagging Strategy\n- Start with 5-10 broad tags maximum — too many defeats purpose\n- Tags are for retrieval, not categorization — \"when would I search for this?\"\n- Multi-tag allowed — note about salary negotiation: #career #communication\n- Review and consolidate tags periodically — synonyms fragment knowledge\n\n## Linking Between Notes\n- [[wiki-style]] links when supported, otherwise relative Markdown links\n- Link liberally — connections are the value of knowledge base\n- Backlinks show where note is referenced — surface hidden connections\n- Don't force links — some notes are standalone\n\n## What User Might Send\n- \"Just learned that...\" → atomic note with insight\n- \"Interesting article: [URL]\" → fetch, summarize, save with source\n- \"Reminder: X\" → capture with context, might become action or reference\n- \"I keep forgetting how to...\" → create or update how-to note\n- Random thought → inbox immediately, process later\n\n## Searching and Retrieval\n- Full-text search with grep or specialized tool — must be fast\n- Search by tag: find all notes with specific tag\n- Recent notes list — often want \"that thing I saved last week\"\n- Offer to search when user asks a question — might already have the answer\n\n## Progressive Enhancement\n- Week 1: inbox.md only, dump everything\n- Week 2: process inbox into atomic notes with tags\n- Week 3: start linking related notes\n- Month 2: create index/MOC for main topics\n- Month 3: folder structure if needed\n\n## What NOT To Suggest Early\n- Complex folder hierarchies — flat with good names first\n- Database or app — Markdown files work until they don't\n- Daily notes system — unless they specifically want journaling\n- Templates — organic structure emerges, then standardize\n\n## Sync and Backup\n- Cloud folder (Dropbox/iCloud) for multi-device access\n- Git repo for version history — see how thinking evolved\n- Plain Markdown ensures portability — not locked to any tool\n","topics":["Knowledge Base"],"tags":{"latest":"1.0.1"},"stats":{"comments":0,"downloads":3681,"installsAllTime":138,"installsCurrent":17,"stars":5,"versions":2},"createdAt":1770766379701,"updatedAt":1778989687922},"latestVersion":{"version":"1.0.1","createdAt":1770766859608,"changelog":"Rename to Personal Knowledge Base","license":null},"metadata":{"setup":[],"os":["linux","darwin","win32"],"systems":null},"owner":{"handle":"ivangdavila","userId":"s178jdk12x4qj3gs2se3etxf3h83h7ft","displayName":"Iván","image":"https://avatars.githubusercontent.com/u/81719670?v=4"},"moderation":null}