Llm Wiki

Community

tudoumashu

llm-wiki

Query and maintain the user's local LLM Wiki from any Codex or Claude Code conversation or project. Use when the user asks to search personal knowledge, recall prior research or decisions, answer from the wiki, create durable notes, ingest a source into the wiki, update topic/concept/entity/question pages, write back useful answers, or run wiki lint/reindex workflows.

Overview

Publisher	tudoumashu
Repository	`ai-memory-skillpack`
Skill name	`llm-wiki`
Stars	455
Forks	0
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by tudoumashu on GitHub. Read the source before you install it.

Installation

Install the Llm Wiki AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/tudoumashu/ai-memory-skillpack/tree/main/skills/llm-wiki
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/tudoumashu/ai-memory-skillpack.git /tmp/ai-memory-skillpack
mkdir -p .claude/skills
cp -r /tmp/ai-memory-skillpack/skills/llm-wiki .claude/skills/llm-wiki

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Llm Wiki in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Llm Wiki on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Llm Wiki is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

LLM Wiki

Core Rule

Use the local LLM Wiki as the durable knowledge source. Do not copy the wiki into this skill.

Paths on this machine:

text
VAULT_ROOT=/home/shiyi/Apps/Obsidian/vault
WIKI_ROOT=/home/shiyi/Apps/Obsidian/vault/60-Wiki
INDEX=/home/shiyi/Apps/Obsidian/vault/60-Wiki/index.md
LOG=/home/shiyi/Apps/Obsidian/vault/60-Wiki/log.md
QUERY=/home/shiyi/Apps/Obsidian/vault/70-System/scripts/query_wiki.sh
LINT=/home/shiyi/Apps/Obsidian/vault/70-System/scripts/lint_wiki.sh
REINDEX=/home/shiyi/Apps/Obsidian/vault/70-System/scripts/reindex_qmd.sh
EMBED_SAFE=/home/shiyi/Apps/Obsidian/vault/70-System/scripts/embed_qmd_safe.sh

Default wiki prose to Chinese. Keep commands, paths, filenames, config keys, API fields, code, package names, versions, URLs, and fixed English terms unchanged.

Obsidian Markdown Rules

Apply when creating or editing Markdown inside VAULT_ROOT, especially WIKI_ROOT.

Preserve existing YAML frontmatter. New wiki pages use the local schema keys: title, created, updated, kind, status, source_paths, tags, summary.
Every agent edit sets frontmatter updated_by: to the fixed actor string claude-code/fable-5 or codex/gpt-5.6-sol-pro, and refreshes updated.
Do not translate or rewrite frontmatter keys, wikilink targets, block IDs, embed targets, file paths, URLs, code blocks, JSON, or shell commands.
Use [[wikilinks]] for internal vault notes ([[path|display]] for Chinese labels); normal Markdown links for external URLs.
Prefer linking related source / topic / concept / entity / question pages over leaving isolated notes.
Embeds ![[...]], callouts, %% comments %%, Mermaid, math, footnotes: only when they add durable structure or evidence. Tags live in frontmatter tags, not inline.
After editing wiki Markdown, run lint_wiki.sh.

Query Workflow

Start from 60-Wiki/index.md.
If the query mentions a local project name or repo path, read the central project entity in 60-Wiki/entities/ first. Do not assume the entity file name matches the project name — locate it first with rg -ilF "<project-name-or-repo-path>" /home/shiyi/Apps/Obsidian/vault/60-Wiki/entities/; on multiple hits pick the page whose frontmatter source_paths contains the repo root (a body mention does not count, same criterion as $ai-project-memory), then read that page.
If the entity points to a repo docs/ai/, follow project read discipline — full read only project-card.md and handoff.md; targeted rg for architecture.md, runbook.md, gotchas.md, diagrams/README.md, current ADRs in decisions/; do not read history/, reports/, screenshots/, learning/, superseded ADRs (Status: superseded/deprecated), or deprecated ledger files by default(change-log 已停用 2026-07-28,git 提交即账本); on explicit user recall, targeted reads are allowed with cross-checking against current code.
Query the compiled wiki:

bash
/home/shiyi/Apps/Obsidian/vault/70-System/scripts/query_wiki.sh "<query>" --scope wiki

If insufficient, widen scope:

bash
/home/shiyi/Apps/Obsidian/vault/70-System/scripts/query_wiki.sh "<query>"
/home/shiyi/Apps/Obsidian/vault/70-System/scripts/query_wiki.sh "<query>" --scope raw

Read cited wiki pages directly before making important claims.
If wiki evidence is stale or insufficient, say so and use source pages, raw sources, project-local docs/ai/, or current web search when required.

Writeback Workflow

Write back only when the answer or change has durable value. Choose the smallest correct destination:

60-Wiki/questions/: reusable answer. 60-Wiki/topics/: cross-source synthesis. 60-Wiki/concepts/: reusable method, pattern, term. 60-Wiki/entities/: person, company, tool, project, system. 60-Wiki/sources/: single-source summary.

When writing back:

Prefer updating an existing page over creating a duplicate.
Preserve frontmatter and wikilinks; set updated_by per the rule above.
Add or update source_paths; link related pages.
Update 60-Wiki/index.md when navigation changes.
log.md is newest-first: agents log content changes only(ingest、writeback、页面重构)by inserting a ## [YYYY-MM-DD] <kind> | <slug> entry above the first existing ## heading. Never hand-write query or lint entries; lint_wiki.sh itself inserts a daily lint | wiki-health entry and writes a report under 70-System/reports/ — tool behavior, not a violation; do not remove those entries.
Keep uncertainty explicit with inferred, unknown, or open questions.
Never write secret values into any wiki page.
The vault is a git repository — after content writebacks, commit with an explicit file list including lint by-products(the updated log.md and the new 70-System/reports/wiki-lint-<date>.md)(git 即账本,不积压未提交改动).

For a user-owned project with repo-local docs/ai/, the central project entity stays lightweight and points to the repo pack: repo path, docs/ai/ path, key file links, short summary, important gaps. Never copy full docs/ai/ content into the wiki; sync only on entity-level changes.

Ingest Workflow

Read the source.
Create or update a source page in 60-Wiki/sources/.
Extract durable points; update relevant topic / concept / entity / question pages — do not stop after only a source page when clear updates exist.
Update 60-Wiki/index.md; add a content entry to 60-Wiki/log.md per Writeback rule 5(newest-first, same header format).
Run lint and reindex.

Validation

bash
/home/shiyi/Apps/Obsidian/vault/70-System/scripts/lint_wiki.sh
/home/shiyi/Apps/Obsidian/vault/70-System/scripts/reindex_qmd.sh llm-wiki

Lint is required after any wiki edit. Reindex only when future search should find new or changed Markdown. Do not run qmd embed by default; run embedding only for immediate vector-search freshness or batch maintenance:

bash
/home/shiyi/Apps/Obsidian/vault/70-System/scripts/embed_qmd_safe.sh llm-wiki

Avoid npx --yes @tobilu/qmd ... embed(version drift, startup cost). Large high-churn files(central log.md, project handoff.md, generated reports)cause repeated expensive embedding — keep entities lightweight and avoid embedding large dumps when a link is enough. Status check: QMD_LLAMA_GPU=false qmd --index llm-wiki status.

Final Response

Mention: wiki pages read; wiki pages changed; validation commands run; any source gaps, uncertainty, or stale information.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Llm Wiki AI skill do?

Why use Llm Wiki on TypingMind?

Because you install it once and use it with any model. Llm Wiki is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Llm Wiki in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/tudoumashu/ai-memory-skillpack/tree/main/skills/llm-wiki. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Llm Wiki?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Llm Wiki?

As many as you like. As long as a model supports skills, you can use Llm Wiki with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Llm Wiki AI skill free?

Yes. It is published on GitHub by tudoumashu under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Algorithmic Art

anthropics

OrganizationPopular

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or…

Doc Coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This…

Authoring Skills

How to create and maintain agent skills in .agents/skills/. Use when creating a new SKILL.md, writing skill descriptions, choosing frontmatter fields, or deciding what content belongs in a skill vs…

Dce Edge

DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render /…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

LLM Wiki

Core Rule

Obsidian Markdown Rules

Query Workflow

Writeback Workflow

Ingest Workflow

Validation

Final Response

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now