How do I install the Read Wiki skill?

Run npx skillmds@latest add jasonkneen/read-wiki in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Read Wiki safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Read Wiki?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Read Wiki free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Read Wiki?

jasonkneen (@jasonkneen) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Read Wiki by jasonkneen — Agent Skill

Name: Read Wiki
Author: jasonkneen

Read Wiki

Use when a task references a specific project, person, or note the user has saved (e.g. "about my project X", "what did I say about Y", "who is Z to me"). The user's overall voice/tone/personality is already loaded into the system prompt automatically and does NOT require this skill — only reach for read-wiki when the task names a specific entity that lives in the wiki. Read-only counterpart to the `save-wiki` skill (which writes to the wiki).

jasonkneen 1225d4d 3.8 KB Updated Sep 17, 2026

File contents

read-wiki

OpenClicky maintains a local personal wiki of plain markdown notes the user (and OpenClicky) has written about their projects, the people they care about, references, and anything else worth remembering across agent runs.

The user's overall personality / voice / tone (Personality.md) is already inlined into your system prompt at startup, so you do NOT need this skill for tone matching. Use it only when a task references a specific named project, person, or note.

Where it lives

Wiki content (curated notes): ~/Library/Application Support/OpenClicky/wiki/wiki/
Raw saves (auto-captured snippets): ~/Library/Application Support/OpenClicky/wiki/raw/
Index: ~/Library/Application Support/OpenClicky/wiki/wiki/_index.md
Backlinks graph: ~/Library/Application Support/OpenClicky/wiki/wiki/_backlinks.json

How to use it

This is a read-only skill. Don't create, edit, or delete anything in the wiki — the user has separate flows for that.

Start with the index:

cat "$HOME/Library/Application Support/OpenClicky/wiki/wiki/_index.md"

The index is structured as [[Title]] (relative/path.md) — short description plus an also: line listing aliases. Use the aliases to match user phrasings ("my tone", "how I write", "my project", a person's nickname, etc.) — they're there exactly so you don't have to guess at filenames.

Then read only the targeted note(s). Examples:

# Writing in the user's voice / matching tone / personality-sensitive task
cat "$HOME/Library/Application Support/OpenClicky/wiki/wiki/Personality.md"

# Drafting about a project
cat "$HOME/Library/Application Support/OpenClicky/wiki/wiki/projects/openclicky.md"

# Mentioning a person they know
cat "$HOME/Library/Application Support/OpenClicky/wiki/wiki/people/farza-majeed.md"

If you don't know which note applies, grep:

grep -rli "<keyword>" "$HOME/Library/Application Support/OpenClicky/wiki/wiki/"

When to consult it

Reach for the wiki when the task asks for user-specific color rather than general knowledge:

"Write/draft/reply to an email/message/post" → read Personality.md so the voice matches.
"About my project X / my company / my work on Y" → read the matching projects/*.md.
"Write something for/about [person]" or "What did I say about [person]" → read the matching people/*.md.
"What's my take on X" / "How do I usually phrase Y" → grep the wiki for X/Y.
Tasks where a generic answer would feel impersonal or off-brand for the user.

Skip the wiki for purely factual, mechanical, or generic tasks (math, public knowledge, code refactors, file ops with no tone implications).

How to apply what you find

Don't paste wiki text verbatim into the user-facing output. Internalize it, then write naturally in their voice.
Don't surface the existence of the wiki to the user ("according to your wiki...") unless they ask. The wiki is a backstage memory layer, not a citation source.
If the wiki contradicts something in the user's current request, follow the current request — the wiki is context, not a constraint.
If a relevant note is missing or empty, proceed without it instead of stalling.

Efficiency

Read targeted files only. Don't cat every note "just in case" — that wastes tokens and adds latency. The pattern is: index → 1-2 specific reads → done.

---name: read-wikidescription: Use when a task references a specific project, person, or note the user has saved (e.g. "about my project X", "what did I say about Y", "who is Z to me"). The user's overall voice/tone/personality is already loaded into the system prompt automatically and does NOT require this skill — only reach for read-wiki when the task names a specific entity that lives in the wiki. Read-only counterpart to the `save-wiki` skill (which writes to the wiki).---# read-wikiOpenClicky maintains a local personal wiki of plain markdown notes the user (and OpenClicky) has written about their projects, the people they care about, references, and anything else worth remembering across agent runs.The user's overall personality / voice / tone (`Personality.md`) is already inlined into your system prompt at startup, so you do NOT need this skill for tone matching. Use it only when a task references a specific named project, person, or note.## Where it lives- Wiki content (curated notes): `~/Library/Application Support/OpenClicky/wiki/wiki/`- Raw saves (auto-captured snippets): `~/Library/Application Support/OpenClicky/wiki/raw/`- Index: `~/Library/Application Support/OpenClicky/wiki/wiki/_index.md`- Backlinks graph: `~/Library/Application Support/OpenClicky/wiki/wiki/_backlinks.json`## How to use itThis is a **read-only** skill. Don't create, edit, or delete anything in the wiki — the user has separate flows for that.Start with the index:```bashcat "$HOME/Library/Application Support/OpenClicky/wiki/wiki/_index.md"```The index is structured as `[[Title]] (relative/path.md) — short description` plus an `also:` line listing aliases. Use the aliases to match user phrasings ("my tone", "how I write", "my project", a person's nickname, etc.) — they're there exactly so you don't have to guess at filenames.Then read only the targeted note(s). Examples:```bash# Writing in the user's voice / matching tone / personality-sensitive taskcat "$HOME/Library/Application Support/OpenClicky/wiki/wiki/Personality.md"# Drafting about a projectcat "$HOME/Library/Application Support/OpenClicky/wiki/wiki/projects/openclicky.md"# Mentioning a person they knowcat "$HOME/Library/Application Support/OpenClicky/wiki/wiki/people/farza-majeed.md"```If you don't know which note applies, grep:```bashgrep -rli "<keyword>" "$HOME/Library/Application Support/OpenClicky/wiki/wiki/"```## When to consult itReach for the wiki when the task asks for *user-specific* color rather than general knowledge:- "Write/draft/reply to an email/message/post" → read `Personality.md` so the voice matches.- "About my project X / my company / my work on Y" → read the matching `projects/*.md`.- "Write something for/about [person]" or "What did I say about [person]" → read the matching `people/*.md`.- "What's my take on X" / "How do I usually phrase Y" → grep the wiki for X/Y.- Tasks where a generic answer would feel impersonal or off-brand for the user.Skip the wiki for purely factual, mechanical, or generic tasks (math, public knowledge, code refactors, file ops with no tone implications).## How to apply what you find- Don't paste wiki text verbatim into the user-facing output. Internalize it, then write naturally in their voice.- Don't surface the existence of the wiki to the user ("according to your wiki...") unless they ask. The wiki is a backstage memory layer, not a citation source.- If the wiki contradicts something in the user's current request, follow the current request — the wiki is context, not a constraint.- If a relevant note is missing or empty, proceed without it instead of stalling.## EfficiencyRead targeted files only. Don't `cat` every note "just in case" — that wastes tokens and adds latency. The pattern is: index → 1-2 specific reads → done.

Frequently asked questions