vault

Name: vault
Author: pariyar07

18stars2forks

How to install vault?

pariyar07/ariadne/vault

$npx -y skills add pariyar07/ariadne --skill vault

Installs into the current project.

Summary

Bootstrap an agentic Markdown knowledge vault for projects, research, learning, life systems, and other long-running knowledge work. Use when creating a new vault, installing the base folder structure, templates, AGENTS.md, CLAUDE.md, Agent navigation files, and optional Obsidian

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Vault
2
3	Use this skill to create or refresh a durable, agent-maintained Markdown knowledge vault. Obsidian is an optional, recommended frontend rather than a runtime requirement.
4
5	This skill complements Obsidian mechanics skills:
6
7	- Use `obsidian-markdown` for notes, properties, wikilinks, embeds, and callouts.
8	- Use `obsidian-bases` for `.base` views.
9	- Use `json-canvas` for `.canvas` maps.
10	- Use `defuddle` for clean Markdown extraction from web pages.
11	- Use `obsidian-cli` when Obsidian is open and CLI interaction is useful.
12
13	It also has workflow companion skills:
14
15	- `ariadne:knowledge-capture` for raw inputs, links, documents, and brain dumps.
16	- `ariadne:global-discovery` for registering existing vaults so cold agents can find them from any workspace.
17	- `ariadne:workspace-instructions` for creating or updating workspace-level `AGENTS.md`, `CLAUDE.md`, or `GEMINI.md` files that connect a workspace to registered Ariadne context.
18	- `ariadne:research-ingest` for cold-start research sources, target confirmation, and write-set orchestration.
19	- `ariadne:research-synthesis` for multi-source research disposition and inquiry history.
20	- `ariadne:research-stewardship` for audit-first research-boundary health and allowlisted repairs.
21	- `ariadne:research-pipeline` for adding research intake and synthesis infrastructure inside an existing scope.
22	- `ariadne:workstream-tracking` for Kanban work boards, Dataview dashboards, and workstream status tracking.
23	- `ariadne:closeout` for post-work capture, checkpoints, handoffs, and safe-to-close decisions.
24	- `ariadne:maintenance` for health checks and recurring maintenance.
25	- `ariadne:navigation` for hubs, routing, workstream graphs, and Base/view-layer changes.
26
27	## Prerequisites
28
29	Before bootstrapping or refreshing a vault, confirm the user has:
30
31	- A target vault folder available on disk.
32	- Optional: Obsidian installed when the user wants its native frontend.
33	- Optional: Obsidian Bases enabled when the vault should render `.base` dashboards.
34	- Node.js available for the validator and `scripts/register_vault.js`.
35	- A skills-capable agent runtime.
36
37	For full Obsidian mechanics coverage, recommend installing `https://github.com/kepano/obsidian-skills` alongside Ariadne when equivalent skills are not already available. Those companion skills cover Markdown, Bases, JSON Canvas, clean web extraction, and Obsidian CLI interaction.
38
39	## Core Model
40
41	The vault is the memory. The skill is the setup and maintenance procedure.
42
43	The human curates direction. Agents compile raw material into a linked Markdown wiki. Any filesystem-capable agent can operate the source directly. Obsidian is a recommended readable frontend; Bases and canvases are optional view layers over the Markdown source of truth and never replace it.
44
45	For multi-area vaults, model the vault as a recursive scope tree. The root scope owns global policy and shared view layers. Each child scope inherits parent rules and adds only local deltas — it never repeats the parent and never ignores it.
46
47	The design principles behind these patterns are documented in the skill references:
48
49	- `references/knowledge-processing-architecture.md` — intake interfaces, processing passes, and the raw → compiled pipeline
50	- `references/recursive-scopes.md` — scope inheritance, the includes-and-transcends model, wikilink resolution
51	- `references/vault-operating-model.md` — the three-layer vault model and navigability rules
52
53	These are reference documentation for skill users. They are not files to bootstrap into the target vault — the principles are encoded in how the skills work.
54
55	This skill bootstraps the system. Use the companion skills for ongoing ingest, synthesis, navigation changes, and maintenance.
56
57	## Start Workflow
58
59	Before writing, read applicable existing root and ancestor instructions. When refreshing a multi-scope vault, require a current-turn named or confirmed target and state an explicit `allowed_write_set`; name every out-of-target hub, routing matrix, or Base formula separately.
60
61	1. Determine the vault path and purpose.
62	2. Classify the vault mode:
63	- `project` - shipping/building something.
64	- `research` - studying a topic.
65	- `learning` - building durable understanding.
66	- `life` - personal operating system, admin, goals, habits.
67	- `system` - procedures, workflows, infrastructure, automation.
68	- `mixed` - more than one of the above.
69	3. Create or update the base folder structure.
70	4. Add core files from `assets/templates/`. A new vault must include the schema-v1 root checkpoint (`00 Index.md`, `AGENTS.md`, `Agent/00 Agent Navigation.md`, and `Agent/Task Routing Matrix.md`) plus `Bases/Sco

People who liked this also viewed

6 picks

Type

vault

18stars2forks

View on GitHub

How to install vault?

pariyar07/ariadne/vault

$npx -y skills add pariyar07/ariadne --skill vault

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Vault
2
3	Use this skill to create or refresh a durable, agent-maintained Markdown knowledge vault. Obsidian is an optional, recommended frontend rather than a runtime requirement.
4
5	This skill complements Obsidian mechanics skills:
6
7	- Use `obsidian-markdown` for notes, properties, wikilinks, embeds, and callouts.
8	- Use `obsidian-bases` for `.base` views.
9	- Use `json-canvas` for `.canvas` maps.
10	- Use `defuddle` for clean Markdown extraction from web pages.
11	- Use `obsidian-cli` when Obsidian is open and CLI interaction is useful.
12
13	It also has workflow companion skills:
14
15	- `ariadne:knowledge-capture` for raw inputs, links, documents, and brain dumps.
16	- `ariadne:global-discovery` for registering existing vaults so cold agents can find them from any workspace.
17	- `ariadne:workspace-instructions` for creating or updating workspace-level `AGENTS.md`, `CLAUDE.md`, or `GEMINI.md` files that connect a workspace to registered Ariadne context.
18	- `ariadne:research-ingest` for cold-start research sources, target confirmation, and write-set orchestration.
19	- `ariadne:research-synthesis` for multi-source research disposition and inquiry history.
20	- `ariadne:research-stewardship` for audit-first research-boundary health and allowlisted repairs.
21	- `ariadne:research-pipeline` for adding research intake and synthesis infrastructure inside an existing scope.
22	- `ariadne:workstream-tracking` for Kanban work boards, Dataview dashboards, and workstream status tracking.
23	- `ariadne:closeout` for post-work capture, checkpoints, handoffs, and safe-to-close decisions.
24	- `ariadne:maintenance` for health checks and recurring maintenance.
25	- `ariadne:navigation` for hubs, routing, workstream graphs, and Base/view-layer changes.
26
27	## Prerequisites
28
29	Before bootstrapping or refreshing a vault, confirm the user has:
30
31	- A target vault folder available on disk.
32	- Optional: Obsidian installed when the user wants its native frontend.
33	- Optional: Obsidian Bases enabled when the vault should render `.base` dashboards.
34	- Node.js available for the validator and `scripts/register_vault.js`.
35	- A skills-capable agent runtime.
36
37	For full Obsidian mechanics coverage, recommend installing `https://github.com/kepano/obsidian-skills` alongside Ariadne when equivalent skills are not already available. Those companion skills cover Markdown, Bases, JSON Canvas, clean web extraction, and Obsidian CLI interaction.
38
39	## Core Model
40
41	The vault is the memory. The skill is the setup and maintenance procedure.
42
43	The human curates direction. Agents compile raw material into a linked Markdown wiki. Any filesystem-capable agent can operate the source directly. Obsidian is a recommended readable frontend; Bases and canvases are optional view layers over the Markdown source of truth and never replace it.
44
45	For multi-area vaults, model the vault as a recursive scope tree. The root scope owns global policy and shared view layers. Each child scope inherits parent rules and adds only local deltas — it never repeats the parent and never ignores it.
46
47	The design principles behind these patterns are documented in the skill references:
48
49	- `references/knowledge-processing-architecture.md` — intake interfaces, processing passes, and the raw → compiled pipeline
50	- `references/recursive-scopes.md` — scope inheritance, the includes-and-transcends model, wikilink resolution
51	- `references/vault-operating-model.md` — the three-layer vault model and navigability rules
52
53	These are reference documentation for skill users. They are not files to bootstrap into the target vault — the principles are encoded in how the skills work.
54
55	This skill bootstraps the system. Use the companion skills for ongoing ingest, synthesis, navigation changes, and maintenance.
56
57	## Start Workflow
58
59	Before writing, read applicable existing root and ancestor instructions. When refreshing a multi-scope vault, require a current-turn named or confirmed target and state an explicit `allowed_write_set`; name every out-of-target hub, routing matrix, or Base formula separately.
60
61	1. Determine the vault path and purpose.
62	2. Classify the vault mode:
63	- `project` - shipping/building something.
64	- `research` - studying a topic.
65	- `learning` - building durable understanding.
66	- `life` - personal operating system, admin, goals, habits.
67	- `system` - procedures, workflows, infrastructure, automation.
68	- `mixed` - more than one of the above.
69	3. Create or update the base folder structure.
70	4. Add core files from `assets/templates/`. A new vault must include the schema-v1 root checkpoint (`00 Index.md`, `AGENTS.md`, `Agent/00 Agent Navigation.md`, and `Agent/Task Routing Matrix.md`) plus `Bases/Sco

People who liked this also viewed

6 picks

Type