{ "schemaVersion": "1.0", "item": { "slug": "pkm", "name": "Personal Knowledge Base", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/ivangdavila/pkm", "canonicalUrl": "https://clawhub.ai/ivangdavila/pkm", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/pkm", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=pkm", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/pkm" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/pkm", "agentPageUrl": "https://openagent3.xyz/skills/pkm/agent", "manifestUrl": "https://openagent3.xyz/skills/pkm/agent.json", "briefUrl": "https://openagent3.xyz/skills/pkm/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Core Behavior", "body": "User sends anything: link, idea, quote, snippet, question, rambling thought\nCapture first, organize second — never lose input while deciding where it goes\nCreate ~/kb/ as the workspace — flat folder of Markdown files initially\nInbox pattern: inbox.md for quick capture, process later into proper notes" }, { "title": "When User Sends Content", "body": "Link → fetch title and summary, save with source URL and capture date\nIdea/thought → save as atomic note with descriptive filename\nQuote → save with attribution, link to source if available\nQuestion → save as note, mark for future research\nLong rambling → extract key points, save as separate atomic notes" }, { "title": "File Naming Convention", "body": "Lowercase with hyphens: how-to-negotiate-salary.md\nDescriptive over date-based — findable by topic, not when captured\nNo rigid hierarchy initially — flat folder with good names beats complex structure\nDate prefix optional for journals: 2024-01-15-weekly-review.md" }, { "title": "Note Structure", "body": "Title as H1 — matches filename concept\nTags at top or bottom — #productivity #career for filtering\nSource/reference if applicable — where it came from\nRelated notes section — manual links build knowledge graph\nKeep notes atomic — one concept per note, link between them" }, { "title": "Inbox Processing", "body": "Periodically ask: \"Want to process your inbox?\"\nFor each item: create proper note, add tags, link to related notes\nDelete from inbox once processed — inbox should trend toward empty\nDon't force immediate organization — capture friction kills usage" }, { "title": "When To Add Structure", "body": "20+ notes: suggest consistent tagging system\n50+ notes: suggest index.md or MOC (Map of Content) for key topics\n100+ notes: suggest folder structure by domain if patterns emerge\nOnly add structure when navigation becomes painful" }, { "title": "Tagging Strategy", "body": "Start with 5-10 broad tags maximum — too many defeats purpose\nTags are for retrieval, not categorization — \"when would I search for this?\"\nMulti-tag allowed — note about salary negotiation: #career #communication\nReview and consolidate tags periodically — synonyms fragment knowledge" }, { "title": "Linking Between Notes", "body": "[[wiki-style]] links when supported, otherwise relative Markdown links\nLink liberally — connections are the value of knowledge base\nBacklinks show where note is referenced — surface hidden connections\nDon't force links — some notes are standalone" }, { "title": "What User Might Send", "body": "\"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\nRandom thought → inbox immediately, process later" }, { "title": "Searching and Retrieval", "body": "Full-text search with grep or specialized tool — must be fast\nSearch by tag: find all notes with specific tag\nRecent notes list — often want \"that thing I saved last week\"\nOffer to search when user asks a question — might already have the answer" }, { "title": "Progressive Enhancement", "body": "Week 1: inbox.md only, dump everything\nWeek 2: process inbox into atomic notes with tags\nWeek 3: start linking related notes\nMonth 2: create index/MOC for main topics\nMonth 3: folder structure if needed" }, { "title": "What NOT To Suggest Early", "body": "Complex folder hierarchies — flat with good names first\nDatabase or app — Markdown files work until they don't\nDaily notes system — unless they specifically want journaling\nTemplates — organic structure emerges, then standardize" }, { "title": "Sync and Backup", "body": "Cloud folder (Dropbox/iCloud) for multi-device access\nGit repo for version history — see how thinking evolved\nPlain Markdown ensures portability — not locked to any tool" } ], "body": "Core Behavior\nUser sends anything: link, idea, quote, snippet, question, rambling thought\nCapture first, organize second — never lose input while deciding where it goes\nCreate ~/kb/ as the workspace — flat folder of Markdown files initially\nInbox pattern: inbox.md for quick capture, process later into proper notes\nWhen User Sends Content\nLink → fetch title and summary, save with source URL and capture date\nIdea/thought → save as atomic note with descriptive filename\nQuote → save with attribution, link to source if available\nQuestion → save as note, mark for future research\nLong rambling → extract key points, save as separate atomic notes\nFile Naming Convention\nLowercase with hyphens: how-to-negotiate-salary.md\nDescriptive over date-based — findable by topic, not when captured\nNo rigid hierarchy initially — flat folder with good names beats complex structure\nDate prefix optional for journals: 2024-01-15-weekly-review.md\nNote Structure\nTitle as H1 — matches filename concept\nTags at top or bottom — #productivity #career for filtering\nSource/reference if applicable — where it came from\nRelated notes section — manual links build knowledge graph\nKeep notes atomic — one concept per note, link between them\nInbox Processing\nPeriodically ask: \"Want to process your inbox?\"\nFor each item: create proper note, add tags, link to related notes\nDelete from inbox once processed — inbox should trend toward empty\nDon't force immediate organization — capture friction kills usage\nWhen To Add Structure\n20+ notes: suggest consistent tagging system\n50+ notes: suggest index.md or MOC (Map of Content) for key topics\n100+ notes: suggest folder structure by domain if patterns emerge\nOnly add structure when navigation becomes painful\nTagging Strategy\nStart with 5-10 broad tags maximum — too many defeats purpose\nTags are for retrieval, not categorization — \"when would I search for this?\"\nMulti-tag allowed — note about salary negotiation: #career #communication\nReview and consolidate tags periodically — synonyms fragment knowledge\nLinking Between Notes\n[[wiki-style]] links when supported, otherwise relative Markdown links\nLink liberally — connections are the value of knowledge base\nBacklinks show where note is referenced — surface hidden connections\nDon't force links — some notes are standalone\nWhat 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\nRandom thought → inbox immediately, process later\nSearching and Retrieval\nFull-text search with grep or specialized tool — must be fast\nSearch by tag: find all notes with specific tag\nRecent notes list — often want \"that thing I saved last week\"\nOffer to search when user asks a question — might already have the answer\nProgressive Enhancement\nWeek 1: inbox.md only, dump everything\nWeek 2: process inbox into atomic notes with tags\nWeek 3: start linking related notes\nMonth 2: create index/MOC for main topics\nMonth 3: folder structure if needed\nWhat NOT To Suggest Early\nComplex folder hierarchies — flat with good names first\nDatabase or app — Markdown files work until they don't\nDaily notes system — unless they specifically want journaling\nTemplates — organic structure emerges, then standardize\nSync and Backup\nCloud folder (Dropbox/iCloud) for multi-device access\nGit repo for version history — see how thinking evolved\nPlain Markdown ensures portability — not locked to any tool" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/ivangdavila/pkm", "publisherUrl": "https://clawhub.ai/ivangdavila/pkm", "owner": "ivangdavila", "version": "1.0.1", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/pkm", "downloadUrl": "https://openagent3.xyz/downloads/pkm", "agentUrl": "https://openagent3.xyz/skills/pkm/agent", "manifestUrl": "https://openagent3.xyz/skills/pkm/agent.json", "briefUrl": "https://openagent3.xyz/skills/pkm/agent.md" } }