Your knowledge compounds while you sleep.
12 Claude Code skills that turn your Obsidian vault into an autonomous knowledge OS — capturing what you learn, organizing your vault overnight, reflecting weekly on your patterns. Zero dependencies. Zero code. 26 markdown files. And /minions so you never need to memorize a command.
Not a CLAUDE.md template. Not an Obsidian plugin. Not a prompt collection. An autonomous knowledge operating system that runs inside Claude Code.
See a real vault after 30 days → · Alex Rivera, CEO of an AI SaaS startup · built automatically from 10-second captures
Minions manages your Obsidian vault as a persistent knowledge graph. Capture in 10 seconds. Organize overnight. Reflect weekly. The vault gets smarter the longer you use it — and Claude Code reads it every session, so it always knows where things stand.
No database. No server. No dependencies. Just markdown files and Claude.
- Claude Code (CLI, desktop app, or IDE extension)
- Obsidian (recommended for browsing, optional)
git clone https://github.com/Catafal/minions-skill.git
cd minions-skill
./install.shThis symlinks all 12 skills into ~/.claude/skills/. Claude Code discovers them automatically.
/minionsYour command center — shows every skill, every flag, every example. Run this any time you forget a command.
# In Claude Code:
/minions-init/minions-migrate /path/to/your/vault/minions-remember "Sarah got promoted to senior engineer at Acme Corp"✓ _Inbox/2026-03-27-0914.md — captured in <1s
Sarah will be extracted → People/Sarah.md on next /minions-organize --inbox
./uninstall.shRemoves skill symlinks only. Your vault data is never touched.
┌─────────────────────┐
│ SETUP (once) │
│ │
│ /minions-init │ Fresh vault
│ /minions-migrate │ Existing vault + preferences
└────────┬────────────┘
│
┌──────────────────┼──────────────────┐
│ │ │
▼ ▼ ▼
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ CAPTURE │ │ CAPTURE │ │ MONITOR │
│ (anytime) │ │ (auto) │ │ (on demand) │
│ │ │ │ │ │
│ /remember │ │ /learn │ │ /trends │
│ "save this" │ │ sessions → │ │ digest/recap │
│ → _Inbox/ │ │ patterns │ │ read-only │
└──────┬───────┘ └──────┬───────┘ └──────────────┘
│ │
▼ ▼
┌─────────────────────────────────┐
│ PROCESS (periodic) │
│ │
│ /organize │
│ inbox → extract → wikilinks │
│ → rename → lifecycle → indexes │
│ → READMEs │
└──────────────┬──────────────────┘
│
▼
┌─────────────────────────────────┐
│ CONSOLIDATE (periodic) │
│ │
│ /consolidate │
│ dedup → contradictions │
│ → episodic→semantic │
│ → derive insights │
└──────────────┬──────────────────┘
│
┌───────┴───────┐
▼ ▼
┌──────────────┐ ┌──────────────┐
│ REFLECT │ │ REFLECT │
│ (weekly) │ │ (weekly) │
│ │ │ │
│ /reflect │ │ /dev-reflect │
│ professional │ │ developer │
│ growth │ │ growth │
└──────────────┘ └──────────────┘
│
▼
┌─────────────────────────────────┐
│ EVOLVE (monthly) │
│ │
│ /autoresearch [skill] │
│ test → mutate → improve │
│ the skills themselves │
└─────────────────────────────────┘
The system runs mostly on autopilot. Here's what you actually do vs. what runs automatically.
| When | What | How | Time |
|---|---|---|---|
| Morning | What's happening? | /minions-trends --digest |
1 min (read) |
| Throughout day | Capture ideas/facts | /minions-remember "..." |
2 sec each |
| End of day | Auto-extract from sessions | /minions-learn |
0 min (cron) |
| Overnight | Process inbox captures | /minions-organize --inbox |
0 min (cron) |
| When | What | How | Time |
|---|---|---|---|
| Monday AM | Set goals | Write weekly/YYYY-WXX.md (manual) |
3 min |
| Friday PM | Week recap | /minions-trends --recap --days 7 |
1 min |
| Friday PM | Professional reflection | /minions-reflect --days 7 |
2 min (read) |
| Friday PM | Write review | Fill "End-of-week review" in weekly file | 5 min |
| Weekend | Full maintenance | /minions-organize --full |
0 min (cron) |
| Weekend | Knowledge quality | /minions-consolidate |
0 min (cron) |
| What | How | Time |
|---|---|---|
| Developer growth report | /minions-dev-reflect --days 30 |
5 min |
| Deep professional reflection | /minions-reflect --days 30 --deep |
10 min |
| Review learnings | Browse _Learnings/ in Obsidian |
10 min |
| Improve weakest skill | /minions-autoresearch [skill] |
5 min setup |
| What | How |
|---|---|
| Big picture reflection | /minions-reflect --days 90 --deep |
| Full vault reorganization | /minions-organize --deep |
| Evolve the system | /minions-autoresearch on 2-3 skills |
| # | Skill | Purpose | When |
|---|---|---|---|
| — | /minions |
Your command center. Shows all skills, flags, examples, vault status. Run this any time. | Any time |
| 1 | /minions-init |
Create fresh vault with full structure | Once |
| 2 | /minions-migrate |
Adapt existing Obsidian vault + preferences interview | Once |
| 3 | /minions-remember |
Capture knowledge — quick inbox (default) or direct extraction | Many times daily |
| 4 | /minions-learn |
Extract patterns from Claude Code sessions + reflective content | Daily (cron) |
| 5 | /minions-organize |
Maintain vault structure — 9 phases from inbox processing to folder READMEs | Daily (inbox) + weekly (full) |
| 6 | /minions-consolidate |
Deduplicate, detect contradictions, elevate episodic to semantic knowledge | Weekly |
| 7 | /minions-trends |
Temporal analysis — trends table, vault digest, narrative recap | On demand |
| 8 | /minions-dev-reflect |
Developer growth analysis — coding patterns, gaps, learning resources | Weekly-monthly |
| 9 | /minions-reflect |
Professional growth analysis — strategic focus, decisions, blind spots | Weekly-monthly |
| 10 | /minions-autoresearch |
Iterative skill optimization via binary evals and controlled mutations | Monthly |
| — | /minions-schedule |
Set up automated maintenance — cron, launchd, or OS crontab | Once per vault |
Use /minions-schedule to set up automated maintenance for any vault:
# Set up schedule for your vault (interactive)
/minions-schedule
# Set up for a specific vault
/minions-schedule --vault ~/Documents/Github/skillia-brain
# See all active schedules across vaults
/minions-schedule --list
# Remove a vault's schedule
/minions-schedule --remove --vault ~/brain| Method | Setup | Lifespan | Multi-vault |
|---|---|---|---|
| Claude Code crons | Instant | 7 days (renew with /minions-schedule) |
Yes — vault path in each prompt |
| OS crontab | Copy-paste | Permanent | Yes — separate lines per vault |
| macOS launchd | Auto-generated plists | Permanent + survives reboots | Yes — separate plists per vault |
| Preset | Tasks | Best for |
|---|---|---|
| Standard | Daily: learn + inbox. Weekly: organize + consolidate | Most users |
| Light | Weekly: organize + consolidate | Low-volume vaults |
| Heavy | Standard + weekly reflect + monthly dev-reflect | Active knowledge workers |
| Custom | Pick exactly what runs when | Power users |
| Schedule | Task | Purpose |
|---|---|---|
| Daily 10:57 PM | /minions-learn --recent |
Extract from today's Claude sessions |
| Daily 11:13 PM | /minions-organize --inbox |
Process inbox captures |
| Weekly Sun 2:07 AM | /minions-organize --full |
Full maintenance |
| Weekly Sun 3:37 AM | /minions-consolidate |
Knowledge quality pass |
Times use odd minutes to avoid API load spikes.
brain/ # Your knowledge vault (Obsidian-compatible)
├── People/ # Entity files by type
├── Organizations/
├── Projects/
├── Technologies/
├── Concepts/
├── Places/
├── Events/
├── _Inbox/ # Quick capture drawer (zero friction)
├── _Learnings/ # Insights that change behavior
│ ├── system/ # Skill corrections (auto-captured)
│ ├── domain/ # Domain insights from reflections
│ └── process/ # How you work best
├── Journal/ # Timestamped fact logs
│ ├── Sessions/ # Claude Code session extractions
│ ├── dev-reflections/ # Developer growth reports
│ └── reflections/ # Professional growth reports
├── _Index/ # Machine-readable indexes
│ ├── catalog.yaml # All entities
│ ├── graph.yaml # All relationships
│ └── timeline.yaml # Activity log
├── _Meta/ # System state
│ ├── state.json # Skill run state
│ ├── preferences.json # Vault organization rules (source of truth)
│ └── run-log.md # Audit trail
├── _Conventions/ # Self-documenting rules
│ ├── vault-rules.md
│ └── entity-template.md
└── CLAUDE.md # Claude Code reads this every session
Capture is separated from organization. /minions-remember dumps to _Inbox/ in ~2 seconds (no LLM, no classification). /minions-organize processes the inbox later — extracting entities, deduplicating, and placing files in proper folders.
"remember X" → _Inbox/ (2 sec) → /organize processes → entity files in proper folders
_Learnings/ stores insights that change behavior, not just facts. Three sources:
- system/ — auto-captured when user rejects a skill suggestion (the system learns from corrections)
- domain/ — extracted from weekly reviews and decisions
- process/ — behavioral patterns from sessions
All skills read _Learnings/system/ at startup to avoid repeating mistakes.
_Meta/preferences.json stores vault organization rules (naming convention, protected folders, wikilink style, README generation). Set once during /minions-migrate or /minions-init. Respected by every skill on every run.
Heavy skills (/organize, /learn, /migrate) spawn parallel sub-agents for large vaults:
- Sub-agents READ and COMPUTE (return JSON)
- Only the main agent WRITES (prevents conflicts)
- Small vaults (<50 files) skip sub-agents entirely
/minions-autoresearch [skill-name] treats skill improvement as a controlled experiment:
- Binary evals only (yes/no, no rating scales)
- One mutation per experiment (isolates causality)
- Keep improvement, discard regression
- Autonomous loop until 95%+ pass rate
/minions-init
Creates the full vault structure. Interactive — asks for location and domains.
/minions-migrate /path/to/your/vault
Analyzes your vault, detects its organization pattern, runs a preferences interview, then overlays the Minions layer without moving any files.
/minions-remember "Sarah got promoted to senior engineer at Acme Corp"
Dumps to inbox. Run /minions-organize --inbox to process into entity files.
minions-skill/
├── _shared/ # Shared references for all skills
│ ├── vault-conventions.md # Structure, formats, indexes, learnings, CLAUDE.md template
│ └── vault-patterns.md # 8 vault org patterns + migration principles
│
├── minions/ (173 lines) ← help + command center
├── minions-init/ (250 lines)
├── minions-migrate/ (511 lines)
├── minions-remember/ (379 lines)
├── minions-learn/ (292 lines)
├── minions-organize/ (485 lines)
├── minions-consolidate/ (189 lines)
├── minions-trends/ (200 lines)
├── minions-dev-reflect/ (335 lines)
├── minions-reflect/ (322 lines)
├── minions-autoresearch/ (443 lines)
└── minions-schedule/ (188 lines)
Each skill follows the same pattern:
SKILL.md— Main skill definition (YAML frontmatter + step-based workflow)references/— Detailed rules loaded on-demand (keeps SKILL.md lean)scripts/— Optional executable assets (dashboard.html for autoresearch)
5000+ lines of Python replaced by 26 markdown files and 0 lines of code.
The insight: Claude Code already has file reading, writing, searching, and LLM intelligence built in. Building a separate application to call an LLM, store results, and search them is building middleware between Claude and Claude.
Skills are process-as-prompt: detailed SOPs that Claude follows step-by-step. Change the behavior by editing a markdown file. No tests, no deployments, no dependencies.
The vault is the database. Obsidian is the UI. Claude is the engine. Markdown is the API.