# Send Personal Knowledge Base to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - 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. ## Suggested prompts ### New install ```text 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. ``` ### Upgrade existing ```text 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. ``` ## Machine-readable fields ```json { "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": { "downloadUrl": "/downloads/pkm", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=pkm", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "pkm", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T09:20:37.213Z", "expiresAt": "2026-05-07T09:20:37.213Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=pkm", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=pkm", "contentDisposition": "attachment; filename=\"pkm-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "pkm" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "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." ] } }, "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" } } ``` ## Documentation ### Core Behavior User sends anything: link, idea, quote, snippet, question, rambling thought Capture first, organize second — never lose input while deciding where it goes Create ~/kb/ as the workspace — flat folder of Markdown files initially Inbox pattern: inbox.md for quick capture, process later into proper notes ### When User Sends Content Link → fetch title and summary, save with source URL and capture date Idea/thought → save as atomic note with descriptive filename Quote → save with attribution, link to source if available Question → save as note, mark for future research Long rambling → extract key points, save as separate atomic notes ### File Naming Convention Lowercase with hyphens: how-to-negotiate-salary.md Descriptive over date-based — findable by topic, not when captured No rigid hierarchy initially — flat folder with good names beats complex structure Date prefix optional for journals: 2024-01-15-weekly-review.md ### Note Structure Title as H1 — matches filename concept Tags at top or bottom — #productivity #career for filtering Source/reference if applicable — where it came from Related notes section — manual links build knowledge graph Keep notes atomic — one concept per note, link between them ### Inbox Processing Periodically ask: "Want to process your inbox?" For each item: create proper note, add tags, link to related notes Delete from inbox once processed — inbox should trend toward empty Don't force immediate organization — capture friction kills usage ### When To Add Structure 20+ notes: suggest consistent tagging system 50+ notes: suggest index.md or MOC (Map of Content) for key topics 100+ notes: suggest folder structure by domain if patterns emerge Only add structure when navigation becomes painful ### Tagging Strategy Start with 5-10 broad tags maximum — too many defeats purpose Tags are for retrieval, not categorization — "when would I search for this?" Multi-tag allowed — note about salary negotiation: #career #communication Review and consolidate tags periodically — synonyms fragment knowledge ### Linking Between Notes [[wiki-style]] links when supported, otherwise relative Markdown links Link liberally — connections are the value of knowledge base Backlinks show where note is referenced — surface hidden connections Don't force links — some notes are standalone ### What User Might Send "Just learned that..." → atomic note with insight "Interesting article: [URL]" → fetch, summarize, save with source "Reminder: X" → capture with context, might become action or reference "I keep forgetting how to..." → create or update how-to note Random thought → inbox immediately, process later ### Searching and Retrieval Full-text search with grep or specialized tool — must be fast Search by tag: find all notes with specific tag Recent notes list — often want "that thing I saved last week" Offer to search when user asks a question — might already have the answer ### Progressive Enhancement Week 1: inbox.md only, dump everything Week 2: process inbox into atomic notes with tags Week 3: start linking related notes Month 2: create index/MOC for main topics Month 3: folder structure if needed ### What NOT To Suggest Early Complex folder hierarchies — flat with good names first Database or app — Markdown files work until they don't Daily notes system — unless they specifically want journaling Templates — organic structure emerges, then standardize ### Sync and Backup Cloud folder (Dropbox/iCloud) for multi-device access Git repo for version history — see how thinking evolved Plain Markdown ensures portability — not locked to any tool ## Trust - Source: tencent - Verification: Indexed source record - Publisher: ivangdavila - Version: 1.0.1 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-30T09:20:37.213Z - Expires at: 2026-05-07T09:20:37.213Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/pkm) - [Send to Agent page](https://openagent3.xyz/skills/pkm/agent) - [JSON manifest](https://openagent3.xyz/skills/pkm/agent.json) - [Markdown brief](https://openagent3.xyz/skills/pkm/agent.md) - [Download page](https://openagent3.xyz/downloads/pkm)