Install the "vault-skill-factory" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/vault-skill-factory into .claude/skills/vault-skill-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-skill-factory", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add Ar9av/obsidian-wiki --skill vault-skill-factory -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "vault-skill-factory" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/vault-skill-factory into .agents/skills/vault-skill-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-skill-factory", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add Ar9av/obsidian-wiki --skill vault-skill-factory -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "vault-skill-factory" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/vault-skill-factory into .cursor/skills/vault-skill-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-skill-factory", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add Ar9av/obsidian-wiki --skill vault-skill-factory -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "vault-skill-factory" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/vault-skill-factory into .gemini/skills/vault-skill-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-skill-factory", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add Ar9av/obsidian-wiki --skill vault-skill-factory -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "vault-skill-factory" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/vault-skill-factory into .github/skills/vault-skill-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-skill-factory", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add Ar9av/obsidian-wiki --skill vault-skill-factory -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "vault-skill-factory" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/vault-skill-factory into .opencode/skills/vault-skill-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-skill-factory", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
vault-skill-factory
GitHub stars
3.5k
Token cost
~1.9k tokens
SKILL.md length
868 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
MIT
At a glance
Create a reviewable Agent Skill package from mature curated wiki pages.
Works in 5 steps: Choose the cluster → Design the skill → Write the skill to the review dir → …
Turning verified vault knowledge into a reusable skill
SKILL.md covers Hard guardrails (read first), Before You Start, Step 1: Choose the cluster and Step 2: Design the skill, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vault Skill Factory is an agent skill from Ar9av/obsidian-wiki. Create a reviewable Agent Skill package from mature curated wiki pages. Use when turning verified vault knowledge into a reusable skill. Reads the vault and writes only to a review directory; it does not install skills.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management, covering Skill management and LLM wikis. It works with Obsidian. The repository describes itself as: Framework for AI agents to build and maintain a digital brain through Obsidian wiki | Memory System for Agents. The licence is MIT.
When your agent uses it
Turning verified vault knowledge into a reusable skill
Tasks that involve Skill management
Tasks that involve LLM wikis
Example prompts
“/vault-skill-factory”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4a0630b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vault Skill Factory loads about 1.9k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 868 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~60
When it runs· the whole SKILL.md, loaded when a task matches
~1.9k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/vault-skill-factory/SKILL.md (or your agent's skills folder).
name
vault-skill-factory
description
Create a reviewable Agent Skill package from mature curated wiki pages. Use when turning verified vault knowledge into a reusable skill. Reads the vault and writes only to a review directory; it does not install skills.
Vault Skill Factory
You turn a cluster of mature, curated wiki pages into a portable Agent Skill: a
SKILL.md plus a references/ folder, written to a review directory for the human to inspect
and (only if they choose) install. This is the inverse of wiki-capture: capture turns a
conversation into a page; the factory turns a body of pages into a reusable skill.
Hard guardrails (read first)
Never write into .skills/ and never run setup.sh or create symlinks into any global
skill directory (~/.claude/skills, ~/.codex/skills, …). Generated skills go to the review
dir only. Installation is a separate, explicit human decision.
Never auto-install. End by telling the user where the skill is and how to install it
project-locally if they want — do not do it for them.
Source pages are trusted vault content, but do not invent capabilities: the generated skill must
reflect what the pages actually say.
Before You Start
Resolve config (Config Resolution Protocol in llm-wiki/SKILL.md): get OBSIDIAN_VAULT_PATH,
OBSIDIAN_WIKI_REPO, OBSIDIAN_LINK_FORMAT, the QMD vars, and:
SKILL_FACTORY_OUTPUT_DIR — where generated skills land. Default:
$OBSIDIAN_VAULT_PATH/_generated-skills (a vault-level, underscore-prefixed excluded dir —
like _raw/_staging/_sources, NOT the skills/ knowledge category). This co-locates
generated skills with the vault they were distilled from. Create it if missing.
Note: _generated-skills/ holds runtime Agent-Skill bundles (name + description frontmatter),
not wiki pages — never write them into skills/ (that category is for knowledge pages and
is graph-/lint-/index-tracked).
SKILL_FACTORY_MATURITY — comma list of lifecycle: values that count as "mature".
Default: reviewed,verified. Pages with tier: core also qualify.
Read index.md to understand what the vault holds.
Step 1: Choose the cluster
Decide which pages become the skill. The user may name a topic, tag, or project; otherwise propose
candidates.
Seed from the user's intent (a topic, tag, project, or a named page).
Expand the cluster:
If QMD is configured (QMD_WIKI_COLLECTION), run qmd query "<topic>" -c "$QMD_WIKI_COLLECTION" --files
(or vsearch) to gather semantically related pages — this is the intended way to find the
full cluster, not just exact-tag matches.
Otherwise Grep/Glob by tag and wikilink-neighbourhood (pages linked from the seed pages).
Filter by maturity: keep pages whose lifecycle: is in SKILL_FACTORY_MATURITYor
whose tier: is core. Drop draft pages unless the user explicitly includes them.
Confirm the cluster with the user (list page names + count) before generating. If fewer than
~3 mature pages match, say so — a skill from one thin page isn't worth it; offer to proceed anyway
or widen the net.
Step 2: Design the skill
From the cluster, decide:
name — kebab-case, derived from the cluster's subject (e.g. french-theory-expert,
peptide-protocols). Must not collide with an existing skill in .skills/.
description — the trigger. Write it "pushy" (per skill-creator): state when to use it
(all the phrasings a user might say) and what it does. This field is what makes the skill fire.
Reasoning approach — how an agent should use this knowledge: the questions it answers, the
method it applies, the caveats it respects. Distil this from the pages' synthesis, not a copy-paste.
Depth material — which page bodies become references/ files.
Show full SKILL.md (378 more words)Show less
Step 3: Write the skill to the review dir
Create $SKILL_FACTORY_OUTPUT_DIR/<name>/ with:
<name>/
├── SKILL.md # frontmatter (name + pushy description) + reasoning approach + key knowledge
├── references/ # depth material distilled from the cluster
│ ├── <topic>.md # one per sub-theme; declarative knowledge, not chat
│ └── sources.md # provenance: which vault pages this was built from (+ their sources)
└── SKILL_FACTORY.md # provenance manifest (see below) — NOT part of the installed skill
SKILL.md body should be lean (the trigger logic + a compact reasoning guide), pushing depth into
references/. Follow the structure of existing skills in this repo. Preserve ^[inferred] /
^[ambiguous] markers when carrying over uncertain claims — a generated skill must not launder
synthesis into fact.
references/sources.md lists every vault page used (by [[wikilink]]) and their upstream
sources: — so the skill stays auditable back to the vault and original sources.
SKILL_FACTORY.md (factory metadata, kept out of the installable skill) records: generation
date, the cluster pages + their lifecycle/tier, the maturity filter used, and the vault commit/hash
if available. This lets a regenerate-on-update workflow diff later.
Optional, if the user asks: append/update a marketplace.json entry in the output dir (the OpenKB
one-line-install convention) — still not an install, just a manifest.
Step 4: Optionally lean on skill-creator
skill-creator ships reusable scripts. Their path differs between a pip/uv install and a source
checkout, so check both layouts under $OBSIDIAN_WIKI_REPO and use the first that exists:
$OBSIDIAN_WIKI_REPO/skills/skill-creator/scripts/ — packaged install (OBSIDIAN_WIKI_REPO points
at the bundled _data/ dir, which ships the skills under skills/).
Vault Skill Factory next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…
Create a reviewable Agent Skill package from mature curated wiki pages. Vault Skill Factory is an agent skill from Ar9av/obsidian-wiki. Create a reviewable Agent Skill package from mature curated wiki pages.
When should I use Vault Skill Factory?
Vault Skill Factory fits situations like: turning verified vault knowledge into a reusable skill; tasks that involve Skill management; tasks that involve LLM wikis.
How do I install Vault Skill Factory in Claude Code?
Run `npx skills add Ar9av/obsidian-wiki --skill vault-skill-factory -a claude-code`. Or copy the skill folder (.skills/vault-skill-factory in Ar9av/obsidian-wiki) into .claude/skills/vault-skill-factory in your project. Claude Code loads it when a task matches its description.
How do I install Vault Skill Factory in Codex?
Run `npx skills add Ar9av/obsidian-wiki --skill vault-skill-factory -a codex`. Or copy the skill folder (.skills/vault-skill-factory in Ar9av/obsidian-wiki) into .agents/skills/vault-skill-factory in your project. Codex loads it when a task matches its description.
Can I use Vault Skill Factory in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ar9av/obsidian-wiki --skill vault-skill-factory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vault-skill-factory, .gemini/skills/vault-skill-factory, .github/skills/vault-skill-factory and .opencode/skills/vault-skill-factory in your project.
What does Vault Skill Factory need to run?
SKILL.md names no scripts, command-line tools or credentials: Vault Skill Factory is instructions for the agent only.
Does Vault Skill Factory access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vault Skill Factory safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vault Skill Factory use?
Vault Skill Factory is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vault Skill Factory use?
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vault Skill Factory?
Skills that share tags, products or a category with Vault Skill Factory: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), LLM Wiki (zosmaai/pi-llm-wiki, 608 stars), LLM Wiki (praneybehl/llm-wiki-plugin, 118 stars) and Karpathy Wiki (SherwinQ/karpathy-wiki, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vault Skill Factory?
Ar9av (a GitHub user) maintains it in Ar9av/obsidian-wiki, which has 3,544 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 8, 2026.
Source: Ar9av/obsidian-wiki on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
