New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vault Sync

by bybren-llc in bybren-llc/safe-agentic-workflow

Detect and repair drift between an OKF knowledge vault and the code it describes.

MITAuto-check passedKnowledge Management

Install Vault Sync

skills CLI
$ npx skills add bybren-llc/safe-agentic-workflow --skill vault-sync -a claude-code

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

GitHub CLI
$ gh skill install bybren-llc/safe-agentic-workflow vault-sync --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/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vault-sync .claude/skills/vault-sync && 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/

Facts

Skill name
vault-sync
GitHub stars
421
Token cost
~1.4k tokens
SKILL.md length
605 words
Files
4 (incl. scripts, references, assets)
Skills in repo
42
Repo updated
First seen
Licence
MIT

At a glance

Detect and repair drift between an OKF knowledge vault and the code it describes.

  • Works in 5 steps: Detect drift → Detect inventory changes → Regenerate → …
  • Update the knowledge vault
  • SKILL.md covers Purpose, When This Skill Applies, Key Files and Procedure, plus 4 more sections
  • Calls node and git

What it does

Vault Sync is an agent skill from bybren-llc/safe-agentic-workflow. Detect and repair drift between an OKF knowledge vault and the code it describes. Use after merging significant changes (schema, interfaces, workflows, agent config), when a staleness review is due, or when the user asks to sync, refresh, or update the knowledge vault.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts, reference files and assets.

It sits in Knowledge Management, covering Second brain. The repository describes itself as: SAW — SAFe Agentic Workflow AI Agent Harness for Multi-Agent Team Workflows Built on SAFe methodology (Scaled Agile Framework), adapted for AI agent teams (Now With AI-DLC!)… The licence is MIT.

When your agent uses it

  • Update the knowledge vault
  • Tasks that involve Second brain

Example prompts

  • “/vault-sync”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Detect drift
  2. Detect inventory changes
  3. Regenerate
  4. Validate
  5. Record

What it can do on your machine

Read from SKILL.md and the folder at commit 26ca58b. 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

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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 Sync loads about 1.4k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 605 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from bybren-llc/safe-agentic-workflow at commit 26ca58b, republished under its MIT licence (© bybren-llc). 605 words, ~1,368 tokens.

Download SKILL.mdSave it as .claude/skills/vault-sync/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
vault-sync
description
Detect and repair drift between an OKF knowledge vault and the code it describes. Use after merging significant changes (schema, interfaces, workflows, agent config), when a staleness review is due, or when the user asks to sync, refresh, or update the knowledge vault.

Vault Sync Skill

TEMPLATE: This skill uses {{PLACEHOLDER}} tokens. Replace with your project values before use.

Purpose

Keep an OKF knowledge vault honest as the code evolves. The vault is a map of the system; this skill detects drift between map and territory, regenerates only the affected concepts, and records the sync.

When This Skill Applies

Invoke this skill when:

  • A significant change merged — schema, public interfaces, CI workflows, agent or skill config
  • A staleness review is due (the stale-concepts Base is the queue)
  • The user asks to sync, refresh, or update the knowledge vault
  • A concept is suspected of being wrong

Key Files

PathRole
<vault>/_meta/vault-config.jsonMachine-readable constitution — types, tags, frontmatter contract
<vault>/_meta/CONVENTIONS.mdThe human-readable rules
<vault>/_meta/manifest.jsonID registry, reverse index, and baseline_sha drift watermark
<vault>/_meta/templates/Per-type skeletons
<vault>/log.mdDated changelog
knowledge-vault/scripts/validate-vault.mjsThe gate

Procedure

1. Detect drift

Read the baseline and diff it to HEAD across the watch-list — the source paths your concepts claim to describe. Configure this list for your project; the example below is illustrative.

bash
BASELINE=$(node -e "console.log(require('./<vault>/_meta/manifest.json').baseline_sha)")
git diff --name-only "$BASELINE"..HEAD -- \
  'src/**' 'lib/**' 'config/**' '.github/workflows/**' 'docs/**'

A concept is stale if and only if a changed path matches its resource or an entry in its sources. Check the manifest first (it is the reverse index); grep concept frontmatter as backup.

This is file-level truth. Do not substitute a time-based heuristic — "older than N days" flags everything and teaches people to ignore the flag.

2. Detect inventory changes

Re-enumerate your source globs and diff against the manifest.

  • New source, no concept → create one. Add the manifest entry first, so the ID exists in the registry before anything links to it.
  • Deleted source → set the concept's status: deprecated. Do not delete the file. Inbound links must be cleaned first, in a follow-up change; the backlinks pane or the validator's orphan report shows them.
3. Regenerate

For a handful of concepts, update inline. For larger sets, fan out generation agents batched by area. Every generation prompt must carry exactly four things:

  1. The type template from _meta/templates/
  2. A golden example — a real, already-accepted concept of the same type
  3. The hard rules from _meta/CONVENTIONS.md, inline
  4. The manifest ID registry — links may target only IDs listed there

Every touched concept gets timestamp: = today and verified_against: = the current short SHA.

Re-derive facts from the source files. Never patch prose without re-reading the code it describes. Editing a concept to match a changed interface without opening the file is how a vault becomes fiction.

Show full SKILL.md (202 more words)Show less
4. Validate
bash
node knowledge-vault/scripts/validate-vault.mjs --vault <vault>

Must exit 0. Markdown lint must pass. Neither is optional.

5. Record

Prepend a dated entry to log.md: what changed, why (ticket), and the source SHA. Then bump baseline_sha and generated in the manifest.

Ship on a {{TICKET_PREFIX}}-XXX-vault-sync-<topic> branch with a docs(vault): … commit to {{MAIN_BRANCH}}. The pull request should name the code changes that triggered the sync.

Invariants (do not relax)

  • Concept-to-concept links never leave the bundle; out-of-bundle links only under ## Citations
  • Relative markdown links only — no wikilinks, no leading-slash paths, no repo-host URLs for repo files
  • Link only to IDs in the manifest. If a concept does not exist, name it in prose and report it as a suggestion — never invent a link
  • One concept per file; H2 sections exactly match the type template, in order
  • Stub types cite their source-of-truth doc; they never restate it
  • A citation is not re-verification. Only re-deriving a concept from source bumps its timestamp and verified_against

Anti-Patterns (Do NOT use)

text
Bumping timestamps on a docs-only pass   (that is laundering, not verification)
Deleting a concept when its source dies  (deprecate; clean inbound links first)
Regenerating the whole vault on drift    (regenerate only what the diff implicates)
Patching prose without reading the code  (the one habit that makes a vault untrustworthy)
Skipping the validator because "it is just docs"  (drift is invisible without the gate)

Authoritative References

  • knowledge-vault/docs/GUIDE.md -- the method and why each rule exists
  • knowledge-vault/docs/ADOPTION-PLAYBOOK.md -- running your first build
  • knowledge-vault/docs/BUILD-PROMPT.md -- the multi-agent build prompt

Routes To

  • safe-workflow — branch, commit, and PR conventions
  • linear-sop — recording the sync against a ticket
  • pattern-discovery — find existing concepts before writing new ones

© bybren-llc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references, assets) in .agents/skills/vault-sync of bybren-llc/safe-agentic-workflow.

  • SKILL.md
  • assets/.gitkeep
  • references/.gitkeep
  • scripts/.gitkeep

Open the folder on GitHubat commit 26ca58b

Compare with similar skills

Vault Sync 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 Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vault Sync this skillbybren-llc/safe-agentic-workflow421—~1.4kAutomated safety check: PassMIT
Second BrainNicholasSpisak/second-brain7361 repos~1.5kAutomated safety check: NotesNone
3D Brainnateherkai/AIS-OS1.6k—~2.1kAutomated safety check: PassCustom licence
Obsidian Canvas BoardsAgriciDaniel/claude-obsidian15k—~1.4kAutomated safety check: PassMIT
Icm ArchitectRinDig/icm-architect1.8k—~3.2kAutomated safety check: PassMIT
Obsidian CLI Read TransportAgriciDaniel/claude-obsidian15k1 repos~762Automated safety check: PassMIT

Similar skills

  • Second Brain

    NicholasSpisak/second-brain

    Set up a new Obsidian knowledge base with the LLM Wiki pattern.

    736 GitHub starsUsed in 1 repo~1.5k tokens
    Knowledge ManagementAuto-check: notes

  • 3D Brain

    nateherkai/AIS-OS

    A skill your agent uses when someone asks to build a 3D brain, visualize their AIOS or second brain, turn their knowledge into an interactive graph, or run /3d-brain or /3D brain.

    1.6k GitHub stars~2.1k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

  • Obsidian Canvas Boards

    AgriciDaniel/claude-obsidian

    Creates, inspects and updates Obsidian JSON Canvas boards in a vault, with text, file, link, group and edge nodes, using safe recoverable edits.

    15k GitHub stars~1.4k tokensUpdated 28 days ago
    Knowledge ManagementAuto-check passed

  • Icm Architect

    RinDig/icm-architect

    Design any process, idea, problem, or body of knowledge into an ICM (Interpretable Context Methodology) workspace — folder structure as agent architecture — or restructure an existing folder, repo…

    1.8k GitHub stars~3.2k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

  • Obsidian CLI Read Transport

    AgriciDaniel/claude-obsidian

    Detects and uses the official Obsidian command-line interface for read-only vault access, falling back to direct file reads, while all mutations stay on a separate transaction core.

    15k GitHub starsUsed in 1 repo~762 tokens
    Knowledge ManagementAuto-check passed

  • Cascading Goal Tracker

    ballred/obsidian-claude-pkm

    Tracks three-year, yearly, monthly, and weekly goals in linked Markdown files, calculating completion percentages and flagging stalled goals.

    1.9k GitHub stars~1.5k tokensUpdated 7 mo ago
    Knowledge ManagementAuto-check passed

More from bybren-llc/safe-agentic-workflow

All 42 skills in this repo

  • Multi-Agent Coordination Template

    bybren-llc/safe-agentic-workflow

    Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialist agents, managing blockers across agents…

    421 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed

  • API Route Patterns

    bybren-llc/safe-agentic-workflow

    API route implementation patterns with RLS, validation, and error handling. Use when creating API routes, implementing CRUD endpoints, adding server-side…

    421 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed

  • Technical Documentation Templates

    bybren-llc/safe-agentic-workflow

    Documentation templates for ADRs, runbooks, architecture docs, and knowledge transfer documents. Use when creating Architecture Decision Records, writing…

    421 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed

  • Deployment SOP Checklist

    bybren-llc/safe-agentic-workflow

    Deployment workflows, pre-deploy validation, smoke testing, and rollback procedures. Use when deploying to staging or production, running smoke tests…

    421 GitHub stars~950 tokensUpdated 2 mo ago
    Auto-check passed

  • Frontend Patterns Template

    bybren-llc/safe-agentic-workflow

    Frontend patterns for modern web frameworks, component libraries, auth flows, and analytics. Use when building UI components, creating pages, implementing…

    421 GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed

  • Advanced Git Operations

    bybren-llc/safe-agentic-workflow

    Advanced git operations including rebase, bisect, cherry-pick, and conflict resolution. Use when rebasing feature branches, debugging with bisect…

    421 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Vault Sync

What does Vault Sync do?

Detect and repair drift between an OKF knowledge vault and the code it describes. Vault Sync is an agent skill from bybren-llc/safe-agentic-workflow. Detect and repair drift between an OKF knowledge vault and the code it describes.

When should I use Vault Sync?

Vault Sync fits situations like: update the knowledge vault; tasks that involve Second brain.

How do I install Vault Sync in Claude Code?

Run `npx skills add bybren-llc/safe-agentic-workflow --skill vault-sync -a claude-code`. Or copy the skill folder (.agents/skills/vault-sync in bybren-llc/safe-agentic-workflow) into .claude/skills/vault-sync in your project. Claude Code loads it when a task matches its description.

How do I install Vault Sync in Codex?

Run `npx skills add bybren-llc/safe-agentic-workflow --skill vault-sync -a codex`. Or copy the skill folder (.agents/skills/vault-sync in bybren-llc/safe-agentic-workflow) into .agents/skills/vault-sync in your project. Codex loads it when a task matches its description.

Can I use Vault Sync 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 bybren-llc/safe-agentic-workflow --skill vault-sync -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-sync, .gemini/skills/vault-sync, .github/skills/vault-sync and .opencode/skills/vault-sync in your project.

What does Vault Sync need to run?

Going by SKILL.md and its folder, Vault Sync needs the command-line tools its instructions call (node and git).

Does Vault Sync access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Vault Sync 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Vault Sync use?

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

About 1.4k tokens (SKILL.md is roughly 5.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 Sync?

Skills that share tags, products or a category with Vault Sync: Second Brain (NicholasSpisak/second-brain, 736 stars), 3D Brain (nateherkai/AIS-OS, 1.6k stars), Obsidian Canvas Boards (AgriciDaniel/claude-obsidian, 15k stars) and Icm Architect (RinDig/icm-architect, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vault Sync?

bybren-llc (a GitHub organization) maintains it in bybren-llc/safe-agentic-workflow, which has 421 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on July 20, 2026.

Source: bybren-llc/safe-agentic-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.