Init Knowledge Vault logo

Init Knowledge Vault

Community
magickaichen
init-knowledge-vault

Set up a governed Markdown vault that is useful immediately by organizing existing authorized work; also conservatively adopt, register, or associate an existing vault.

Overview

Publishermagickaichen
Repositoryknowledge-loom
Skill nameinit-knowledge-vault
Stars
53
Forks
1
Bundled files
6
LicenseMIT
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.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Init Knowledge Vault 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/magickaichen/knowledge-loom/tree/main/skills/init-knowledge-vault
  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/magickaichen/knowledge-loom.git /tmp/knowledge-loom
mkdir -p .claude/skills
cp -r /tmp/knowledge-loom/skills/init-knowledge-vault .claude/skills/init-knowledge-vault
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Init Knowledge Vault 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 Init Knowledge Vault 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 Init Knowledge Vault 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.

Set up a useful knowledge vault

Requires Node.js 20+ and local file/command access.

Turn one setup request into a populated, registered vault through one previewed change.

Load authority

Resolve this SKILL.md to its canonical path, following symlinks. Set <skill-root> to the directory containing that canonical file. Read <skill-root>/references/protocol.md and <skill-root>/references/contract-schema.md completely before proposing changes.

Select the flow

For an ordinary setup or create request, run the protocol's Bootstrap a useful vault workflow. The invocation is the complete product input. Infer safe setup values and include them in the one preview; multiple registered vaults do not require a preliminary selection question. Ask separately only when no safe proposal can resolve identity, destination, privacy, or lifecycle authority.

Use contract-only governance initialization only when the user explicitly requests an empty contract. Use adoption mode for an existing non-empty vault. A standalone registration or project-association request skips bootstrap and changes only the requested registry state.

Prepare one preview

Map every required schema field to user input, repository or source evidence, or a named safe default. Default new and adopted vaults to proactive-durable-capture writes and maintain-after-material-change current-state maintenance. Keep explicit-only available when the user requests it. Never enable cross-vault access, remote sync, or backup implicitly.

Inspect the relevant CLI interfaces before constructing the preview:

bash
node "<skill-root>/scripts/knowledge-loom.mjs" init --help
node "<skill-root>/scripts/knowledge-loom.mjs" register --help
node "<skill-root>/scripts/knowledge-loom.mjs" associate --help

Run init without --apply. Before showing the preview, inspect the current registry and any active-project association so ID, path, and replacement conflicts are visible. Present the single bootstrap preview required by the protocol and apply only after the user approves that exact bundle.

Apply and finish

Rerun the exact previewed init command with --apply, then write the previewed contract details, canonical notes, navigation, and current focus. Preserve existing content during adoption.

Run registration and applicable association without --apply; apply each only when its output matches the approved preview. Stop on a conflict and preserve the valid partial result. A standalone registration or association request receives its own preview before application.

Run audit-knowledge-vault. If Git is enabled, preserve unrelated changes and follow the protocol's lifecycle rules. Report the exact discovery, preview, population, registration, association, audit, commit, sync, and backup state. Apply the protocol's completion condition; a placeholder index is not a completed setup.

Bundled files

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

Frequently asked questions

What does the Init Knowledge Vault AI skill do?

Set up a governed Markdown vault that is useful immediately by organizing existing authorized work; also conservatively adopt, register, or associate an existing vault.

Why use Init Knowledge Vault on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/magickaichen/knowledge-loom/tree/main/skills/init-knowledge-vault. 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 Init Knowledge Vault?

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 Init Knowledge Vault?

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

Is the Init Knowledge Vault AI skill free?

Yes. It is published on GitHub by magickaichen 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

Set up your own AI workspace now

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