Agent skill

Vault Ops

Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions.

MITAuto-check passed

Install Vault Ops

skills CLI

$ npx skills add kv0906/pm-kit --skill vault-ops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install kv0906/pm-kit vault-ops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/kv0906/pm-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/vault-ops .claude/skills/vault-ops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "vault-ops" agent skill from https://github.com/kv0906/pm-kit/tree/main/.claude/skills/vault-ops into .claude/skills/vault-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-ops", 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.

$skill-installer

$skill-installer install https://github.com/kv0906/pm-kit/tree/main/.claude/skills/vault-ops

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 kv0906/pm-kit --skill vault-ops -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install kv0906/pm-kit vault-ops --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kv0906/pm-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/vault-ops .agents/skills/vault-ops && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "vault-ops" agent skill from https://github.com/kv0906/pm-kit/tree/main/.claude/skills/vault-ops into .agents/skills/vault-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-ops", 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 kv0906/pm-kit --skill vault-ops -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install kv0906/pm-kit vault-ops --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kv0906/pm-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/vault-ops .cursor/skills/vault-ops && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "vault-ops" agent skill from https://github.com/kv0906/pm-kit/tree/main/.claude/skills/vault-ops into .cursor/skills/vault-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-ops", 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.

gemini skills install

$ gemini skills install https://github.com/kv0906/pm-kit.git --path .claude/skills/vault-ops

--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 kv0906/pm-kit --skill vault-ops -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install kv0906/pm-kit vault-ops --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kv0906/pm-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/vault-ops .gemini/skills/vault-ops && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "vault-ops" agent skill from https://github.com/kv0906/pm-kit/tree/main/.claude/skills/vault-ops into .gemini/skills/vault-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-ops", 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.

GitHub CLI

$ gh skill install kv0906/pm-kit vault-ops

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 kv0906/pm-kit --skill vault-ops -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/kv0906/pm-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/vault-ops .github/skills/vault-ops && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "vault-ops" agent skill from https://github.com/kv0906/pm-kit/tree/main/.claude/skills/vault-ops into .github/skills/vault-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-ops", 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 kv0906/pm-kit --skill vault-ops -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install kv0906/pm-kit vault-ops --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kv0906/pm-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/vault-ops .opencode/skills/vault-ops && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "vault-ops" agent skill from https://github.com/kv0906/pm-kit/tree/main/.claude/skills/vault-ops into .opencode/skills/vault-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-ops", 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-ops
GitHub stars: 138
Token cost: ~844 tokens
SKILL.md length: 185 words
Files: 1
Skills in repo: 26
Repo updated: Jun 29, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions.

Works in 6 steps: Check if note already exists… → Load appropriate template from _templates/ → Replace template variables (Handlebars… → …
SKILL.md covers Vault Structure, Naming Conventions…, File Operations and Template Variables, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vault Ops is an agent skill from kv0906/pm-kit. Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions. Auto-invoked for all file operations.

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AI-augmented PM workspace for Coding Agents — daily standups, decisions, blockers, docs, and sprint reviews as markdown skills. The licence is MIT.

Example prompts

“/vault-ops”

Requirements

Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Check if note already exists (naming-as-API enables fast lookup)
Load appropriate template from _templates/
Replace template variables (Handlebars syntax)
Add YAML frontmatter with type, project, status, date, tags
Insert wiki-links to related notes
Write to correct folder per naming convention

What it can do on your machine

Read from SKILL.md and the folder at commit 2cb5d9f. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Edit
- Glob
- Grep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and yaml).
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 Ops loads about 844 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 185 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~46
When it runs · the whole SKILL.md, loaded when a task matches: ~844

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.

SKILL.md

The full file from kv0906/pm-kit at commit 2cb5d9f, republished under its MIT licence (© kv0906). 185 words, ~844 tokens.

Download SKILL.mdSave it as .claude/skills/vault-ops/SKILL.md (or your agent's skills folder).

name: vault-ops
description: Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions. Auto-invoked for all file operations.
allowed-tools: Read, Write, Edit, Glob, Grep

Vault Operations Skill

Core operations for reading, writing, and managing files in a PM-Kit vault.

Vault Structure

pm-kit/
├── CLAUDE.md           # Vault context (read first)
├── _core/              # config.yaml, MANIFESTO.md, PROCESSING.md
├── _templates/         # Note templates (ALWAYS USE)
├── 00-inbox/           # Unprocessed captures
├── 01-index/           # Project MOCs
├── daily/              # YYYY-MM-DD.md (multi-project)
├── docs/{project}/     # PRDs, specs
├── decisions/{project}/ # Decision records
├── blockers/{project}/  # Active blockers
├── meetings/           # Meeting notes
├── reports/            # Generated reports
│   └── previews/       # HTML previews (/preview, /report --preview)
└── _archive/           # Archived by YYYY-MM/

Naming Conventions (Naming-as-API)

Strict filename patterns enable glob queries without a database:

Type	Pattern	Example
Daily	`daily/YYYY-MM-DD.md`	`daily/2026-01-15.md`
Doc	`docs/{project}/{slug}.md`	`docs/project-a/checkout-flow.md`
Decision	`decisions/{project}/YYYY-MM-DD-{slug}.md`	`decisions/project-a/2026-01-15-auth-approach.md`
Blocker	`blockers/{project}/YYYY-MM-DD-{slug}.md`	`blockers/project-a/2026-01-15-api-rate-limit.md`
Meeting	`meetings/YYYY-MM-DD-{type}-{slug}.md`	`meetings/2026-01-15-sync-sprint-review.md`
Inbox	`00-inbox/YYYY-MM-DD-{slug}.md`	`00-inbox/2026-01-15-quick-thought.md`
Index	`01-index/{project}.md`	`01-index/project-a.md`

File Operations

Creating Notes

Check if note already exists (naming-as-API enables fast lookup)
Load appropriate template from _templates/
Replace template variables (Handlebars syntax)
Add YAML frontmatter with type, project, status, date, tags
Insert wiki-links to related notes
Write to correct folder per naming convention

Editing Notes

Preserve YAML frontmatter structure
Maintain existing wiki-links
Use consistent heading hierarchy
Apply standard tag format

Wiki-Link Format

markdown

[[Note Name]]                    # Simple link
[[Note Name|Display Text]]       # Link with alias
[[Note Name#Section]]            # Link to heading
[[folder/Note Name]]             # Link with path

Template Variables

When processing templates, replace Handlebars syntax:

{{date}} → Today's date (YYYY-MM-DD)
{{project}} → Project ID
{{project_name}} → Project display name
{{title}} → Note title
{{slug}} → URL-safe slug

YAML Frontmatter

All notes require frontmatter:

yaml

---
type: [daily|doc|decision|blocker|meeting|inbox|index]
project: {project-id}
status: {per note_types in config.yaml}
date: YYYY-MM-DD
tags: []
---

Auto-Linking Rules

From	Links To
Daily (blocked item)	`blockers/{project}/`
Meeting	`decisions/{project}/`, `blockers/{project}/`
Decision	`docs/{project}/`
Doc	decisions, blockers

Archive Rules

Move to _archive/YYYY-MM/ when:

Blocker status → resolved
Doc status → shipped
Decision status → superseded

Files

Just SKILL.md in .claude/skills/vault-ops of kv0906/pm-kit.

Open the folder on GitHubat commit 2cb5d9f

Compare with similar skills

Vault Ops 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.

Vault Ops compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Vault Ops this skillkv0906/pm-kit	138	—	~844	Automated safety check: Pass	MIT	3 mo ago
Obsidian Vault Maintaineropenclaw/openclaw	392k	1 repos	~262	Automated safety check: Pass	MIT	today
Knowledge Opsaffaan-m/ECC	276k	2 repos	~1.7k	Automated safety check: Pass	MIT	4 days ago
Research Opsaffaan-m/ECC	276k	2 repos	~902	Automated safety check: Pass	MIT	4 days ago
Terminal Opsaffaan-m/ECC	276k	2 repos	~750	Automated safety check: Pass	MIT	4 days ago
Messages Opsaffaan-m/ECC	276k	1 repos	~724	Automated safety check: Pass	MIT	4 days ago

Similar skills

Obsidian Vault Maintainer
openclaw/openclaw
Maintain an Obsidian-friendly memory wiki vault with wikilinks, frontmatter, and official Obsidian CLI awareness.
392k GitHub starsUsed in 1 repo~262 tokens
Knowledge ManagementAuto-check passed
Knowledge Ops
affaan-m/ECC
Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos).
276k GitHub starsUsed in 2 repos~1.7k tokens
Knowledge ManagementAuto-check passed
Research Ops
affaan-m/ECC
Evidence-first current-state research workflow for ECC. An agent skill from affaan-m/ECC.
276k GitHub starsUsed in 2 repos~902 tokens
Research & ScienceAuto-check passed
Terminal Ops
affaan-m/ECC
Evidence-first repo execution workflow for ECC. An agent skill from affaan-m/ECC.
276k GitHub starsUsed in 2 repos~750 tokens
Testing & QAAuto-check passed
Messages Ops
affaan-m/ECC
Evidence-first live messaging workflow for ECC. An agent skill from affaan-m/ECC.
276k GitHub starsUsed in 1 repo~724 tokens
Productivity & AutomationAuto-check passed
Email Ops
affaan-m/ECC
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.
276k GitHub starsUsed in 1 repo~1.1k tokens
Writing & ContentAuto-check passed

Questions about Vault Ops

What does Vault Ops do?

Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions. Vault Ops is an agent skill from kv0906/pm-kit. Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions.

How do I install Vault Ops in Claude Code?

Run `npx skills add kv0906/pm-kit --skill vault-ops -a claude-code`. Or copy the skill folder (.claude/skills/vault-ops in kv0906/pm-kit) into .claude/skills/vault-ops in your project. Claude Code loads it when a task matches its description.

How do I install Vault Ops in Codex?

Run `npx skills add kv0906/pm-kit --skill vault-ops -a codex`. Or copy the skill folder (.claude/skills/vault-ops in kv0906/pm-kit) into .agents/skills/vault-ops in your project. Codex loads it when a task matches its description.

Can I use Vault Ops 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 kv0906/pm-kit --skill vault-ops -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-ops, .gemini/skills/vault-ops, .github/skills/vault-ops and .opencode/skills/vault-ops in your project.

What does Vault Ops need to run?

SKILL.md names no scripts, command-line tools or credentials: Vault Ops is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep.

Does Vault Ops 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 Ops 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 Ops use?

Vault Ops 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 Ops use?

About 844 tokens (SKILL.md is roughly 3.4k 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 Ops?

Skills that share tags, products or a category with Vault Ops: Obsidian Vault Maintainer (openclaw/openclaw, 392k stars), Knowledge Ops (affaan-m/ECC, 276k stars), Research Ops (affaan-m/ECC, 276k stars) and Terminal Ops (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vault Ops?

kv0906 (a GitHub user) maintains it in kv0906/pm-kit, which has 138 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on June 29, 2026.

Source: kv0906/pm-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Vault Ops

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Vault Operations Skill

Vault Structure

Naming Conventions (Naming-as-API)

File Operations

Creating Notes

Editing Notes

Wiki-Link Format

Template Variables

YAML Frontmatter

Auto-Linking Rules

Archive Rules

Files

Compare with similar skills

Similar skills

More from kv0906/pm-kit

Questions about Vault Ops