Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Content Creation
Personal Knowledge Base
Help users build a personal knowledge base by organizing whatever they send into structured notes.
skill openclawclawhub Free
Help users build a personal knowledge base by organizing whatever they send into structured notes.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
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
Category context
Writing, remixing, publishing, visual generation, and marketing content production.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md