carlosbuelvas1carlosbuelvas1/openclaw-skills/personal-knowledge-wiki/SKILL.md

personal-knowledge-wiki

Skill0 starsChanged 6 months agoMITView on GitHub

Use when Charlie wants OpenClaw to save, learn, organize, retrieve, or update long-term knowledge from notes, links, articles, transcripts, research, conversations, or agent outputs into a sourced personal wiki.

1 other project uses a version of this.

Adopted by

Most recently taken up by

puppyfront-web/social-publish-skillstheir own version, first seen Oct 17, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
puppyfront-web/social-publish-skills★ 14same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- approved-backlog-watchdogSkill
- context-engineeringSkill
- elon-operatorSkill
- goal-modeSkill
- image-readingSkill
- local-article-toolSkill
- mac-ttsSkill
- repurpose-funnelSkill
- skill-builderSkill
- swipefile-compilerSkill
- thumbnail-creatorSkill
- video-to-skillSkill
- visual-first-explainerSkill
- x-link-best-effortSkill
- youtube-learnSkill

The file

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. About 0 are common, 16 are distinctive, and 8 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific
could be automatic: a setting could enforce it

Distinctive:
Use this skill when Charlie says things like:
line 11
Very specific:
Read references/wiki-schema.md when creating or refactoring wiki pages.
line 27
Distinctive:
Do not invent sources, metrics, dates, names, or links.
line 32
Distinctive:
Do not overwrite raw evidence.
line 33
Very specific:
Use [[wikilinks]] for important entities, concepts, projects, decisions, and playbooks.
line 34
Distinctive:
Keep contradictions visible.
line 35
Distinctive:
Keep pages operational: short summaries, dated evidence, next actions, and links beat long essays.
line 36
Very specific:
When the input is an x.com or twitter.com status URL:
line 39
Very specific:
Use x_tweet_fetch first. Do not start with direct web fetch on X.
line 41
Very specific:
If x_tweet_fetch fails, try public syndication JSON, browser extraction, or available X/link recovery skills before creating a gap.
line 43
Distinctive:
Only ask Charlie for a screenshot or pasted text after all available read-only fetch paths fail.
line 44
Distinctive:
If a gap is created, label it as retrieval failure, not source truth, and include the exact tools attempted.
line 45
Very specific:
Create or append a source note in wiki/sources/YYYY-MM-DD-slug.md.
line 49
Distinctive:
Update existing pages first.
line 55
Distinctive:
Add provenance under each updated claim using source links or URLs.
line 56
Very specific:
Update wiki/index.md, wiki/overview.md, and wiki/log.md with the smallest useful change.
line 57
Distinctive:
If evidence conflicts, add or update a contradiction page and link both sides.
line 58
Distinctive:
If evidence is missing, add a gap entry with the next research step.
line 59
Very specific:
Search the wiki first with rg across ~/.openclaw/workspace/wiki.
line 62
Distinctive:
Prefer source-backed answers over memory.
line 63
Distinctive:
If the wiki has no evidence, say so and offer to research or create a new gap entry.
line 66
Distinctive:
Start with a 2-4 bullet summary.
line 69
Distinctive:
Use dated evidence sections.
line 70
Distinctive:
Keep claims atomic so later agents can update them without rewriting the page.
line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Personal Knowledge Wiki

Purpose

Maintain a local, interlinked, sourced knowledge base in ~/.openclaw/workspace/wiki. Copy the Journey Kit architecture pattern: ingest raw inputs, extract durable knowledge, connect it with wiki links, and keep contradictions/gaps visible.

Use this skill when Charlie says things like:

"wiki this", "save this", "learn this", "add this to memory", or "build our knowledge base".
"what do we know about..." or asks for a sourced answer from prior notes.
Provides notes, links, articles, X/YouTube research, meeting notes, agent outputs, decisions, or operating procedures that should compound over time.

Storage Map

wiki/raw/ - immutable pasted inputs, transcripts, scraped text, and original notes.
wiki/sources/ - one source note per artifact or URL.
wiki/entities/ - people, companies, tools, projects, accounts, competitors.
wiki/concepts/ - reusable ideas, frameworks, patterns, terms.
wiki/syntheses/ - cross-source analysis and higher-level conclusions.
wiki/playbooks/ - repeatable workflows and operating recipes.
wiki/decisions/ - decisions, rationale, owners, and reversal conditions.
wiki/contradictions/ - conflicts between sources or stale assumptions.
wiki/gaps/ - questions, missing evidence, and research backlog.

Read references/wiki-schema.md when creating or refactoring wiki pages.

Non-Negotiables

Preserve provenance. Every non-obvious claim must point to a source note, URL, file path, or dated user statement.
Separate fact from inference. Label inference explicitly when a conclusion is reasoned from evidence.
Do not invent sources, metrics, dates, names, or links.
Do not overwrite raw evidence. Add new raw files or append clearly dated notes.
Use [[wikilinks]] for important entities, concepts, projects, decisions, and playbooks.
Keep contradictions visible. Do not silently merge conflicting claims.
Keep pages operational: short summaries, dated evidence, next actions, and links beat long essays.

X/Twitter Ingestion

When the input is an x.com or twitter.com status URL:

Use x_tweet_fetch first. Do not start with direct web fetch on X.
Save fetched fields when available: author, username, source date, full text or note_tweet text, metrics, linked URLs, media URLs, and referenced posts.
If x_tweet_fetch fails, try public syndication JSON, browser extraction, or available X/link recovery skills before creating a gap.
Only ask Charlie for a screenshot or pasted text after all available read-only fetch paths fail.
If a gap is created, label it as retrieval failure, not source truth, and include the exact tools attempted.

Ingest Workflow

Identify input type: note, URL, article, transcript, conversation, research output, decision, or playbook.
Create or append a source note in wiki/sources/YYYY-MM-DD-slug.md. Put the raw pasted material in wiki/raw/YYYY-MM-DD-slug.md when the input is long or should remain immutable.
Extract durable items:
- Entities: people, companies, products, accounts, projects.
- Concepts: ideas, tactics, models, definitions.
- Decisions: commitments, architecture choices, tradeoffs.
- Playbooks: repeatable workflows.
Update existing pages first. Create new pages only when the item is likely to matter again.
Add provenance under each updated claim using source links or URLs.
Update wiki/index.md, wiki/overview.md, and wiki/log.md with the smallest useful change.
If evidence conflicts, add or update a contradiction page and link both sides.
If evidence is missing, add a gap entry with the next research step.

Retrieval Workflow

Search the wiki first with rg across ~/.openclaw/workspace/wiki.
Prefer source-backed answers over memory.
Return the answer with links or file paths to the supporting pages.
Include known contradictions and gaps when they change the answer.
If the wiki has no evidence, say so and offer to research or create a new gap entry.

Page Style

Start with a 2-4 bullet summary.
Use dated evidence sections.
Link aggressively with [[double brackets]].
Keep claims atomic so later agents can update them without rewriting the page.
End operational pages with Next actions when useful.

Output To Charlie

For save/update requests, respond briefly:

What was saved.
Which pages changed.
Any contradictions or gaps created.

For retrieval requests, answer directly and cite the wiki pages used.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free