← Plugin catalog
Education & Research

vaultcraft

Mikołaj Sapek v0.6.1

Build Obsidian study vaults

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Interactive
  • Read
  • Write

Cost & access

vaultcraft is free. It does not sell anything or process payments.

Declared limitations

  • Deleting notes is not supported: every tool is read-only.
  • No access to the user's computer: the server cannot open local files.
  • Unrelated request: no vaultcraft tool should be called.

Onboarding example

Build an Obsidian study vault from these lecture slides
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 11, 2026. Package observed Nov 10, 2026.

View package source →

Description

From the marketplace listing

vaultcraft reads your lecture slides, lab notebooks, meeting notes or papers and builds an Obsidian vault from them: one note per concept with a hover-visible definition, lecture sheets with exam questions, embedded source slides, comparison tables and a map of content. It asks a few questions first (vault type, format, depth, language), then writes the vault to your disk, or hands you a zip to open in Obsidian.

Language: English · Automatically detected from descriptions.

Matches for “paris”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher description

Turns lecture slides, labs, meeting notes and papers into a linked Obsidian study vault: atomic notes with hover definitions, embedded slides, comparison tables and cross-course bridges.

Publisher full description

vaultcraft reads your lecture slides, lab notebooks, meeting notes or papers and builds an Obsidian vault from them: one note per concept with a hover-visible definition, lecture sheets with exam questions, embedded source slides, comparison tables and a map of content. It asks a few questions first (vault type, format, depth, language), then writes the vault to your disk, or hands you a zip to open in Obsidian.

What changed

· 4 observations

Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions: added “`scripts/check_vault.py`, `scripts/check_diagrams.mjs` (missing, or no Python/Node) | Run the same checks by hand with `references/goal-checks.md`; done =...”.

View comparison →

Technical updates · 2

Package or technical metadata updated

View technical comparison →

Package or technical metadata updated

View technical comparison →

Keywords

Files & skills

File archives

Plugin package25 files · 69.6 KBBrowse files →
Skill instructions
vaultcraft9.37 KB

View saved version →

---
name: vaultcraft
description: "Turn scattered materials (lecture slides, lab scripts, project docs, meeting notes, research papers) into a richly visual, linked Obsidian knowledge vault. Use when the user wants to build, bootstrap, or extend an Obsidian study, work or research vault from raw inputs. Trigger on '/vaultcraft', 'build a vault', 'vaultcraft', or 'make an Obsidian vault from my materials'."
---

# vaultcraft

This skill turns course, work or research materials into a linked Obsidian vault.
It runs the same way in Claude Code, Cowork, claude.ai, ChatGPT and Codex: this file
owns the conversation (banner, intake, confirm), and the files in `references/` hold
the generation pipeline (parsing, note-writing, linking, audit).

Paths in this skill (`references/...`, `templates/...`) are relative to the folder
that holds this `SKILL.md`. Call that folder `SKILL_DIR`.

Do these steps in order. Do not skip the banner or the intake.

## Step 1 — Print the banner (always, first thing)

Print this exactly, inside a fenced code block, before anything else:

```text
██╗   ██╗ █████╗ ██╗   ██╗██╗  ████████╗ ██████╗██████╗  █████╗ ███████╗████████╗
██║   ██║██╔══██╗██║   ██║██║  ╚══██╔══╝██╔════╝██╔══██╗██╔══██╗██╔════╝╚══██╔══╝
██║   ██║███████║██║   ██║██║     ██║   ██║     ██████╔╝███████║█████╗     ██║
╚██╗ ██╔╝██╔══██║██║   ██║██║     ██║   ██║     ██╔══██╗██╔══██║██╔══╝     ██║
 ╚████╔╝ ██║  ██║╚██████╔╝███████╗██║   ╚██████╗██║  ██║██║  ██║██║        ██║
  ╚═══╝  ╚═╝  ╚═╝ ╚═════╝ ╚══════╝╚═╝    ╚═════╝╚═╝  ╚═╝╚═╝  ╚═╝╚═╝        ╚═╝
           ⛏  an obsidian vault builder — study · work · research  ⛏
```

Then one status line, e.g. `→ Bootstrap mode. Starting intake.`

## Step 2 — Quick mode detection

If the user's prompt names a vault path you can read, glob it: `.obsidian/` present +
notes in standard folders → **INCREMENTAL** (only ask what's new). `.vault-progress.md`
present → offer **Resume** (Resume / Start over / Inspect). Otherwise → **BOOTSTRAP**
(full intake). Announce the detected mode.

## Step 3 — Intake

Skip any question the user's prompt already answered. If your host has an interactive
question tool (`AskUserQuestion` in Claude Code and Cowork), use it: ≤4 questions and
≤4 options per call, headers ≤12 chars, Recommended option first with `(Recommended)`,
`multiSelect: true` where multiple answers fit, `preview` for Format/Style. If it has
none (claude.ai chat, ChatGPT, Codex, Cursor), send Batches A and B as ONE numbered plain-text
list with the options and the recommended default on each line, and tell the user they
can reply "defaults" to accept every recommendation.

**Batch A — Vault shape** (4 single-select):

1. `Vault type` — studies (Recommended) · work · research · personal *(reference/teaching → Other)*
2. `Format` — Detailed narrative (Recommended) · Study sheet · Golden template · Reference *(preview a 6-line sample of each)*
3. `Depth` — standard (Recommended) · lean · thorough
4. `Language` — English (Recommended) · Polish · German · Spanish

For `studies`/`teaching`, add a follow-up `Templates` — Yes both (Recommended) · Lecture only · Concept only · No free format.

**Batch B — Style** (3 questions):

1. `Styles` (multiSelect) — defaults by type: studies → ELI5 + Worked example + Historical + Real-world; work → Real-world + Counter-example + Worked example + Devil's advocate; research → Counter-example + Historical + Devil's advocate + Worked example; personal → ELI5 + Real-world + Historical + Visual metaphor.
2. `Flashcards` — None (Recommended) · Key concepts only · Every concept
3. `Urgency` — studies: <1 week · 1–4 weeks (Recommended) · 1–3 months · No rush; work/research: weekly · monthly (Recommended) · quarterly · ongoing.

**Batch C — Free-text** (plain markdown block, never option chips):

```text
1. Course / project name?
2. Specific goal? (e.g. "exam 28 June", "onboarding doc by Q3")
3. Priority topics? (must-know vs nice-to-have, or "extract from materials")
4. Deadline / t

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 15 — file references are metadata, not package contents.

Release notes

Adds the optional vaultcraft server: Obsidian vault settings, note templates and a link check for finished notes.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Mikołaj Sapek
Keywords
See keywords
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Interactive
  • Read
  • Write

Package observed Nov 10, 2026.

Technical details
First seen
Oct 30, 2026 · 22:33 UTC
Last seen
Nov 11, 2026 · 12:00 UTC
Latest observed change
Nov 10, 2026 · 18:08 UTC
Collection status
Collected

plugin_asdk_app_6ad2d875b8648191b6e43ed5675b2c0b

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.