How do I install the Read Wiki skill?

Run npx skillmds@latest add yogiraja/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. Capability flags: docs only. 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?

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

Read Wiki by yogiraja — Agent Skill

Name: Read Wiki
Rating: 4.2 (5 reviews)
Author: YogirajA

Read Wiki

Query the knowledge base before doing work. Use when the user asks "what do we know about X", "get context before I update this", "have we seen this pattern", "what connects A and B", or any question that accumulated project or cross-project knowledge could answer. Also invoke proactively when starting a non-trivial code task in a project that has a wiki: read the relevant pages first before touching files. Strictly read-only: never writes to any wiki file. Triggers on /read-wiki or phrases like "check the wiki", "get context", "what's in the wiki about", "have we documented".

YogirajA Updated Sep 22, 2026

File contents

read-wiki: Query the Knowledge Base

Pure read. No writes. Never create, edit, or append to any wiki file during this skill.

Step 1: Find all known wikis

Read ~/.claude/CLAUDE.md and look for the ## Wikis section. It lists every wiki with a path to its index.md and a one-line description of what's in it. (A global SessionStart hook may already have injected the project and GK index maps into context at session start; if they are present, use them rather than re-reading.)

Also check if the current working directory has a ./knowledgebase/index.md: a project wiki wired by write-wiki. If it exists and is not already in the registry, use it anyway.

Step 2: Determine which wikis to read

Project wiki first. Match the current working directory against registry entries. If a project wiki exists for this folder, read it first.

GK wiki as fallback. If:

The question is cross-cutting (architecture patterns, methodology, prior engagement experience), OR
The project wiki doesn't have a relevant answer,

...also read the General Knowledge index.md whose path is given by the Wikis registry in ~/.claude/CLAUDE.md.

Both wikis can contribute to one answer. Synthesize across them, project content takes priority.

Step 3: Read and synthesize

Read index.md of the relevant wiki(s). Do not read every page: scan the index to find candidates.
Open only the pages that are relevant to the question. Follow [[wikilinks]] if they lead somewhere useful.
Synthesize a direct answer with citations: reference the wiki page (and through it, the raw source).

Format: answer first, citations at the end as a compact list. Keep it tight.

Step 4: Stop

Do not offer to update anything. Do not append to log.md. Do not create new pages. If the answer would be worth saving, say: "Want me to save this to the wiki? Run /write-wiki." If the wiki has no answer at all, say so, and point at /research as the way to go get one.

---name: read-wikidescription: Query the knowledge base before doing work. Use when the user asks "what do we know about X", "get context before I update this", "have we seen this pattern", "what connects A and B", or any question that accumulated project or cross-project knowledge could answer. Also invoke proactively when starting a non-trivial code task in a project that has a wiki: read the relevant pages first before touching files. Strictly read-only: never writes to any wiki file. Triggers on /read-wiki or phrases like "check the wiki", "get context", "what's in the wiki about", "have we documented".---# read-wiki: Query the Knowledge BasePure read. No writes. Never create, edit, or append to any wiki file during this skill.## Step 1: Find all known wikisRead `~/.claude/CLAUDE.md` and look for the `## Wikis` section.It lists every wiki with a path to its `index.md` and a one-line description of what's in it.(A global SessionStart hook may already have injected the project and GK index maps into context at sessionstart; if they are present, use them rather than re-reading.)Also check if the current working directory has a `./knowledgebase/index.md`: a project wikiwired by write-wiki. If it exists and is not already in the registry, use it anyway.## Step 2: Determine which wikis to read**Project wiki first.** Match the current working directory against registry entries.If a project wiki exists for this folder, read it first.**GK wiki as fallback.** If:- The question is cross-cutting (architecture patterns, methodology, prior engagement experience), OR- The project wiki doesn't have a relevant answer,...also read the General Knowledge `index.md` whose path is given by the Wikis registry in `~/.claude/CLAUDE.md`.Both wikis can contribute to one answer. Synthesize across them, project content takes priority.## Step 3: Read and synthesize1. Read `index.md` of the relevant wiki(s). Do not read every page: scan the index to find candidates.2. Open only the pages that are relevant to the question. Follow `[[wikilinks]]` if they lead somewhere useful.3. Synthesize a direct answer with citations: reference the wiki page (and through it, the raw source).Format: answer first, citations at the end as a compact list. Keep it tight.## Step 4: StopDo not offer to update anything. Do not append to log.md. Do not create new pages.If the answer would be worth saving, say: "Want me to save this to the wiki? Run /write-wiki."If the wiki has no answer at all, say so, and point at `/research` as the way to go get one.

Frequently asked questions