obsidian-vault-ops
Operate Obsidian vaults for SCBE workflows, including discovery, inspection, and controlled note export.
Best use case
obsidian-vault-ops is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Operate Obsidian vaults for SCBE workflows, including discovery, inspection, and controlled note export.
Teams using obsidian-vault-ops should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/obsidian-vault-ops/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How obsidian-vault-ops Compares
| Feature / Agent | obsidian-vault-ops | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Operate Obsidian vaults for SCBE workflows, including discovery, inspection, and controlled note export.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Obsidian Vault Ops ## Quick Workflow 1. Discover vaults first. - Run `python scripts/list_obsidian_vaults.py`. - Confirm the target vault path before touching notes. 2. Default to read-only inspection. - List notes with `rg --files <vault_path> -g "*.md"`. - Inspect structure with `rg -n "^# |^---$|^tags:|^source:" <vault_path> -g "*.md"`. 3. Normalize metadata only when requested. - Preserve existing content. - Add only missing frontmatter keys needed for SCBE ingestion. 4. Export for SCBE training workflows. - Copy selected markdown notes into a staging folder in the active repo. - Keep filenames stable and deterministic. - Record source vault path and export timestamp in the manifest. 5. Validate before commit or upload. - Ensure UTF-8 text. - Ensure each exported markdown file has a clear title and source context. - Re-run grep checks for required metadata fields. ## Safety Rules - Never modify Obsidian vault content unless explicitly requested. - Avoid bulk rewrites across a vault without a backup. - Keep exports separate from source vaults to prevent accidental corruption. ## SCBE Notes Ingestion Pattern - Prefer markdown as source of truth. - Keep lore/story files in a dedicated export folder. - Include provenance fields in frontmatter when available: - `title` - `source` - `tags` - `updated_at` - When preparing training artifacts, preserve chapter boundaries and glossary sections as distinct blocks. ## Resources - `scripts/list_obsidian_vaults.py`: detect Obsidian vaults from `%APPDATA%\\Obsidian\\obsidian.json`. - `references/local_vaults.md`: current known local vault paths discovered on this machine.
Related Skills
obsidian
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
multi-agent-cloud-offload
Deterministically sort, bundle, verify, and offshore local files through multiple AI/model lanes while capturing training rows and method evidence. Use when Codex needs to inventory folders, batch-process files, upload them to cloud targets such as rclone-backed Google Drive, Hugging Face, or GitHub, and only delete sources after the configured number of verified targets succeed.
long-form-work-orchestrator
Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.
scbe-code-scanning-ops
Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.
cloud-storage-local-storage-management
Audit, sort, route, and back up large Windows workspaces across local disks and cloud-sync folders without recursive mirror failures. Use when the user wants the filesystem cleaned up, cloud storage organized, backup targets chosen by free space and route quality, or hardware/storage bottlenecks identified before moving data.