Wiki Ingest logo

Wiki Ingest

Community
bozhouDev
wiki-ingest

Use when adding a new source to a wiki — a paper, article, URL, file, transcript, or any document. One ingest may touch 10-15 wiki pages.

Overview

PublisherbozhouDev
Repositorybozhou-skills
Skill namewiki-ingest
Stars
78
Forks
7
Bundled files
Instructions only
Links
  • 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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by bozhouDev on GitHub. Read the source before you install it.

Installation

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

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/bozhouDev/bozhou-skills/tree/main/wiki-ingest
  4. 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.
2

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/bozhouDev/bozhou-skills.git /tmp/bozhou-skills
mkdir -p .claude/skills
cp -r /tmp/bozhou-skills/wiki-ingest .claude/skills/wiki-ingest
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Wiki Ingest 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 Wiki Ingest 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 Wiki Ingest 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.

Wiki Ingest

Add a source to the wiki. Read it, discuss with the user, write a summary page, update entity/concept pages, and maintain the index, overview, and log.

Pre-condition

Search for SCHEMA.md starting from the current directory and upward, or in common wiki locations (~/wikis/). If not found, tell the user to run wiki-init first.

Read SCHEMA.md to learn: wiki root path, page frontmatter format, cross-reference convention, log entry format, index category taxonomy.

Process

1. Accept the source

The source can be:

  • File path — read it directly; copy to raw/<filename> if not already there
  • URL — use the browse skill to fetch it; save to raw/<slug>.<ext>
  • Pasted text — use what was provided

2. Read the source in full

Read all content. For long sources, read in sections. Do not skip.

3. Surface takeaways — BEFORE writing anything

Tell the user:

  • 3-5 bullet points of key takeaways
  • What entities/concepts this introduces or updates
  • Whether it contradicts anything already in the wiki (read wiki/index.md and relevant pages to check)

Ask: "Anything specific you want me to emphasize or de-emphasize?"

Wait for the user's response before proceeding.

4. Generate the slug

Lowercase, hyphens, no special characters. Example: "Attention Is All You Need" → attention-is-all-you-need

5. Write the source summary page

Write wiki/pages/<slug>.md:

markdown
---
title: <source title>
tags: [<relevant tags>]
sources: [<slug>]
updated: <today>
---

# <Source Title>

**Source:** <original URL or file path>
**Date ingested:** <today>
**Type:** <paper | article | transcript | code | other>

## Summary

<2-3 paragraph synthesis — your own words, not abstract copy-paste>

## Key Takeaways

- <bullet>

## Entities & Concepts

<list of entities/concepts as [[slug]] links>

## Relation to Other Wiki Pages

<how this connects to or updates existing knowledge>

5b. Cite as you write — do not skip

While drafting the Summary, Key Takeaways, and any other prose section, every non-common-knowledge factual claim must carry a footnote. Read the Citations section in SCHEMA.md for the full convention.

Two citation kinds, three valid targets:

Quote:     [^N]: <target> <locator> — "<verbatim quote>"
Synthesis: [^N]: <target> <locator> [synthesis] — <what supports the claim>

<target> is one of:
  [[source-slug]]      — a source wiki page (preferred for the source you're ingesting)
  raw/<file>           — a path, for drive-by citations to other local files
  <URL>                — a live URL or post

For the source being ingested, use [[<this-source-slug>]] — wiki-ingest is creating that page now, so the target exists by the time the page is read.

If you cannot produce either citation kind for a claim, you do not have a citation. Find one, weaken the claim ("the paper suggests..."), or drop it.

Footnotes go at the bottom of the page, below all sections. Number them sequentially in order of first reference.

5c. Self-check before continuing

Re-read the draft once. Scan for unfootnoted factual claims — this is the most common failure mode in long ingest sessions. For each, add a footnote or revise the wording. Only then move on to entity pages.

6. Update entity and concept pages

For each entity/concept touched by this source:

  • Page exists: Read it, add to or update the relevant section, add this source to frontmatter sources list, update updated date
  • Page doesn't exist: Create it:
markdown
---
title: <Entity or Concept Name>
tags: [entity | concept]
sources: [<this-source-slug>]
updated: <today>
---

# <Name>

## Description

<synthesis across all sources that discuss this>

## Appearances in Sources

- [[source-slug]] — <one-line note>

## Related Concepts

- [[related-slug]] — <relationship>

7. Backlink audit — do not skip

Scan ALL existing pages in wiki/pages/ for any that mention this source's entities/concepts but don't yet link to the new page. Add [[new-slug]] references where appropriate.

This is the step most commonly skipped. A compounding wiki's value comes from bidirectional links.

8. Update wiki/index.md

Add an entry under the correct category:

- [[<slug>]] — <one-line summary> _(ingested <date>)_

For any new entity/concept pages created, add those too.

9. Update wiki/overview.md

Re-read the current overview. If this source:

  • Introduces a significant concept: add it to "Key Entities / Concepts"
  • Shifts the overall understanding: update "Current Understanding"
  • Raises a new question: add it to "Open Questions"

Update the frontmatter updated date.

10. Append to wiki/log.md

## [<today>] ingest | <source title>
Pages written: <slug>
Pages updated: <comma-separated list>

Common Mistakes

  • Appending chronological updates instead of editing in-place — Wiki pages are living documents, not journals. Do not add sections like ## April 27 update: or **Update:** followed by new content. Update the relevant section in-place, bump the updated frontmatter date, and record what changed in log.md. The log is the append-only record; pages are the current truth.
  • Skipping the backlink audit (step 7) — A wiki's value compounds through bidirectional links. Always scan existing pages for entities this source introduces.
  • Summarizing the abstract instead of synthesizing — The Summary section should reflect your own synthesis, not a rephrased abstract.

11. Report to user

  • Summary page: wiki/pages/<slug>.md
  • Entity/concept pages created or updated:
  • Pages that received backlinks:
  • Index and overview updated

Frequently asked questions

What does the Wiki Ingest AI skill do?

Use when adding a new source to a wiki — a paper, article, URL, file, transcript, or any document. One ingest may touch 10-15 wiki pages.

Why use Wiki Ingest on TypingMind?

Because you install it once and use it with any model. Wiki Ingest 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 Wiki Ingest in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bozhouDev/bozhou-skills/tree/main/wiki-ingest. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Wiki Ingest?

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 Wiki Ingest?

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

Is the Wiki Ingest AI skill free?

It is published on GitHub by bozhouDev. Check the repository for licensing terms. 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇