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

by scott-fryxell in scott-fryxell/brayness

Read, search, and maintain the user's Obsidian vault at work/vault, a PARA-structured knowledge base of projects, interests, and reference material.

MITAuto-check passedKnowledge Management

Install Vault

skills CLI
$ npx skills add scott-fryxell/brayness --skill vault -a claude-code

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

GitHub CLI
$ gh skill install scott-fryxell/brayness vault --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/scott-fryxell/brayness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vault .claude/skills/vault && 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
GitHub stars
125
Token cost
~1.3k tokens
SKILL.md length
414 words
Files
5
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Read, search, and maintain the user's Obsidian vault at work/vault, a PARA-structured knowledge base of projects, interests, and reference material.

  • Works in 3 steps: Ask once: "Do you have an Obsidian… → If they have one elsewhere, link it: ln… → If not, create it
  • The user asks about their notes
  • SKILL.md covers Location, If there is no vault, Structure and Reading the vault, plus 4 more sections
  • Runs Shell scripts from its folder; calls rg and bash

What it does

Vault is an agent skill from scott-fryxell/brayness. Read, search, and maintain the user's Obsidian vault at work/vault, a PARA-structured knowledge base of projects, interests, and reference material. Creates one if none exists. Use when the user asks about their notes or interests, or wants links categorized or feeds rebuilt.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `add-frontmatter.sh`, `add-stars.sh` and `github-stars-map.yaml`).

It sits in Knowledge Management, covering Knowledge bases. It works with Obsidian and GitHub. The repository describes itself as: A harness for the anxious digital mind. A safe place for creatives to keep their creative soul while exploring digital skills. The licence is MIT.

When your agent uses it

  • The user asks about their notes
  • Wants links categorized

Example prompts

  • “/vault”

Requirements

  • A Bash shell

Workflow steps

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

  1. Ask once: "Do you have an Obsidian vault? Where is it?"
  2. If they have one elsewhere, link it: ln -s "" work/vault.
  3. If not, create it

What it can do on your machine

Read from SKILL.md and the folder at commit 71f10e2. 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 script files (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • rg
    • bash

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

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

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 scott-fryxell/brayness at commit 71f10e2, republished under its MIT licence (© scott-fryxell). 414 words, ~1,335 tokens.

Download SKILL.mdSave it as .claude/skills/vault/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
vault
description
Read, search, and maintain the user's Obsidian vault at work/vault, a PARA-structured knowledge base of projects, interests, and reference material. Creates one if none exists. Use when the user asks about their notes or interests, or wants links categorized or feeds rebuilt.

Vault

The vault is a PARA-structured Obsidian brain. Other skills read and write it.

Location

bash
VAULT=./work/vault   # from the harness root

If there is no vault

Don't ask at session start. The first time a task needs the vault:

  1. Ask once: "Do you have an Obsidian vault? Where is it?"
  2. If they have one elsewhere, link it: ln -s "<their vault>" work/vault.
  3. If not, create it:
bash
mkdir -p "work/vault/"{"01 Projects","02 Areas","03 Resources","04 Archive",Clippings}

Then carry on with the original task.

Structure

  • 01 Projects/ -- active work with an end
  • 02 Areas/ -- ongoing interests
  • 03 Resources/ -- reference material
  • 04 Archive/ -- inactive items
  • 05 journal/ -- yearly journals
  • Clippings/ -- saved articles and links inbox (categorize into PARA sections)
  • Unsorted/ -- secondary inbox for uncategorized links

Each subfolder has a :feed.md with a dataview query listing its contents by date added. :feed.md is the convention for "show me what's in this section."

Reading the vault

Use read, rg, or find directly against $VAULT. Examples:

bash
# list a section
ls "$VAULT/02 Areas/Music/"

# literal search across the vault
rg -l "cowpunk" "$VAULT"

# show a section's feed
cat "$VAULT/02 Areas/Music/:feed.md"

For semantic search ("what notes feel related to X"), no tool exists yet - fall back to rg with synonyms.

Recent activity

When asked "what's been happening recently in my vault" or "what's new":

bash
# 1. Current journal -- newest entries at the bottom
read "$VAULT/05 journal/Journal.md"
read "$VAULT/05 journal/Journal $(date +%Y).md"

# 2. Most recently modified files across the vault (excludes dot dirs)
find "$VAULT" -name "*.md" \
  -not -path "*/.obsidian/*" -not -path "*/.git/*" \
  -exec stat -f "%m %Sm %N" {} + 2>/dev/null \
  | sort -rn | head -30

# 3. Recently added files per section (by ctime = when file was created)
for section in "01 Projects" "02 Areas" "03 Resources"; do
  find "$VAULT/$section" -name "*.md" -not -name ":feed.md" \
    -exec stat -f "%m %Sm %N" {} + 2>/dev/null \
    | sort -rn | head -10
  echo "---"
done

# 4. Check inboxes
find "$VAULT/Clippings" -name "*.md" -mtime -30 2>/dev/null | sort
find "$VAULT/Unsorted" -name "*.md" -mtime -30 2>/dev/null | sort

Note: All files in the vault may share the same ctime/mtime (common after a git clone or bulk operation). In that case, rely on the journal content and created date in YAML frontmatter instead of filesystem timestamps.

Also check specific project notes for structured updates (release notes, TODOs, design briefs):

bash
for project in "$VAULT/01 Projects"/*/; do
  echo "=== $(basename "$project") ==="
  ls "$project" | grep -i -E "(todo|release|log|status|notes|update)" | head -5
done

How feeds work

Each :feed.md contains a Dataview query that reads created (YAML frontmatter) to list items chronologically. Starred repos appear alongside regular notes by their repo creation date. The github column shows owner/repo for stars, blank for regular notes:

dataview
TABLE created AS "Date", github AS "Source"
FROM "02 Areas/Music"
WHERE file.name != ":feed"
SORT created DESC

Regenerate all feeds from skills/vault/:

bash
bash rebuild-feeds.sh
Show full SKILL.md (166 more words)Show less

Maintenance

bash
./add-frontmatter.sh       # batch add YAML frontmatter to files missing it (extracts source URL, author from domain)
./add-stars.sh             # sync GitHub starred repos into vault (idempotent, skips existing via github: frontmatter key)
./rebuild-feeds.sh         # regenerate all :feed.md files (runs after add-stars.sh to surface new entries)
GitHub stars sync

add-stars.sh fetches your starred repos (GITHUB_USER, or the gh login), categorizes each into the right PARA section using skills/vault/github-stars-map.yaml rules (topic matching with language/description fallbacks), and creates a note with github: owner/repo frontmatter. Re-runs are safe -- existing notes are skipped.

See skills/vault/github-stars-map.yaml for the categorization mapping. Override any misclassification by moving the note to the right directory and the feed will pick it up.

Filing conventions

  • Filename is the title -- do not duplicate it as a heading inside the note.
  • Bare URLs trigger the auto-card-link plugin; do not wrap them.
  • Unsorted is the inbox; anything there should be categorized into a PARA section and removed from Unsorted.
  • Add created date in frontmatter when organizing -- use the file's original timestamp. Preserves capture date if files are ever copied/moved (filesystem ctime changes, frontmatter survives).
  • Frontmatter format:
    yaml
    ---
title: "Filename as Title"
source: "https://example.com/article" # extracted from first URL in file
author:
  - "[[Domain]]" # derived from source URL
published:
created: YYYY-MM-DD # from filesystem ctime
description: ""
tags:
  - "reference"
---

© scott-fryxell, 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 4 other files in skills/vault of scott-fryxell/brayness.

  • SKILL.md
  • add-frontmatter.sh
  • add-stars.sh
  • github-stars-map.yaml
  • rebuild-feeds.sh

Open the folder on GitHubat commit 71f10e2

Compare with similar skills

Vault 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 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vault this skillscott-fryxell/brayness125—~1.3kAutomated safety check: PassMIT
LLM Wikilewislulu/llm-wiki-skill655—~3.7kAutomated safety check: PassNone
LLM Wikipraneybehl/llm-wiki-plugin118—~5.7kAutomated safety check: PassMIT
Obsidian Vault Ingest Pipelinejason-effi-lab/karpathy-llm-wiki-vault721—~669Automated safety check: PassNone
My WikiNimaChu/my-wiki124—~674Automated safety check: PassMIT
Knowledge Base Health Lintjason-effi-lab/karpathy-llm-wiki-vault721—~336Automated safety check: PassNone

Similar skills

  • LLM Wiki

    lewislulu/llm-wiki-skill

    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…

    655 GitHub stars~3.7k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

  • LLM Wiki

    praneybehl/llm-wiki-plugin

    Build and maintain an LLM-curated knowledge base from papers, articles, transcripts, notes and project findings.

    118 GitHub stars~5.7k tokensUpdated 28 days ago
    Knowledge ManagementAuto-check passed

  • Obsidian Vault Ingest Pipeline

    jason-effi-lab/karpathy-llm-wiki-vault

    Compiles raw articles, papers and transcripts sitting in an inbox folder into linked Obsidian source, entity and concept pages, then archives the originals.

    721 GitHub stars~669 tokensUpdated 6 mo ago
    Knowledge ManagementAuto-check passed

  • My Wiki

    NimaChu/my-wiki

    Work with a local My Wiki knowledge base, Dashboard, and knowledge graph.

    124 GitHub stars~674 tokensUpdated 3 days ago
    Knowledge ManagementAuto-check passed

  • Knowledge Base Health Lint

    jason-effi-lab/karpathy-llm-wiki-vault

    Scans an Obsidian-style wiki for broken double-link references, orphan pages, files missing from the index and unresolved knowledge conflicts, then reports the findings.

    721 GitHub stars~336 tokensUpdated 6 mo ago
    Knowledge ManagementAuto-check passed

  • Wiki Vault Query

    jason-effi-lab/karpathy-llm-wiki-vault

    Answers questions from a local Obsidian-style wiki by reading its index first, then the relevant pages, and replying with wiki-link citations instead of model memory.

    721 GitHub stars~383 tokensUpdated 6 mo ago
    Knowledge ManagementAuto-check passed

More from scott-fryxell/brayness

All 27 skills in this repo

  • Logo Finder

    scott-fryxell/brayness

    Find and install brand SVG logos via SVGL (https://svgl.app/) and Wikimedia Commons fallbacks into any project's static asset folder.

    125 GitHub stars~1.1k tokensUpdated 13 days ago
    Auto-check passed

  • Test Coverage

    scott-fryxell/brayness

    Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors.

    125 GitHub stars~1.6k tokensUpdated 13 days ago
    Auto-check passed

  • Flexible Visual System

    scott-fryxell/brayness

    Derive a project's visual rules from its existing tokens, palette, type scale, logo, and icons (Intake), then generate raw SVG vector graphics from those rules as a small composable set (module…

    125 GitHub stars~1.9k tokensUpdated 13 days ago
    Auto-check passed

  • Hyperframes

    scott-fryxell/brayness

    Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML.

    125 GitHub stars~3.2k tokensUpdated 13 days ago
    Auto-check passed

  • Motion Systems

    scott-fryxell/brayness

    A skill your agent uses when designing or implementing motion for web interfaces, including CSS transitions and keyframes, linear() easing design, transform strategy (translate/rotate vs…

    125 GitHub stars~1.7k tokensUpdated 13 days ago
    Auto-check passed

  • Vue Inspect

    scott-fryxell/brayness

    Inspect live Vue 3 component state via agent-browser eval - no Devtools extension, no console.log.

    125 GitHub stars~779 tokensUpdated 13 days ago
    Auto-check passed

Works with

Categories

Questions about Vault

What does Vault do?

Read, search, and maintain the user's Obsidian vault at work/vault, a PARA-structured knowledge base of projects, interests, and reference material. Vault is an agent skill from scott-fryxell/brayness. Read, search, and maintain the user's Obsidian vault at work/vault, a PARA-structured knowledge base of projects, interests, and reference material.

When should I use Vault?

Vault fits situations like: the user asks about their notes; wants links categorized.

How do I install Vault in Claude Code?

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

How do I install Vault in Codex?

Run `npx skills add scott-fryxell/brayness --skill vault -a codex`. Or copy the skill folder (skills/vault in scott-fryxell/brayness) into .agents/skills/vault in your project. Codex loads it when a task matches its description.

Can I use Vault 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 scott-fryxell/brayness --skill vault -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, .gemini/skills/vault, .github/skills/vault and .opencode/skills/vault in your project.

What does Vault need to run?

Going by SKILL.md and its folder, Vault needs a shell for the scripts in its folder and the command-line tools its instructions call (rg and bash). Our summary lists: A Bash shell.

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

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

About 1.3k tokens (SKILL.md is roughly 5.3k 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?

Skills that share tags, products or a category with Vault: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), LLM Wiki (praneybehl/llm-wiki-plugin, 118 stars), Obsidian Vault Ingest Pipeline (jason-effi-lab/karpathy-llm-wiki-vault, 721 stars) and My Wiki (NimaChu/my-wiki, 124 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vault?

scott-fryxell (a GitHub user) maintains it in scott-fryxell/brayness, which has 125 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 28, 2026.

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