메뉴
Obsidian vault operations via CLI. Use for note management, search, daily notes, knowledge graph analysis, tasks, properties. Not for Notion sync (use notion-sync).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | obsidian |
| description | Obsidian vault operations via CLI. Use for note management, search, daily notes, knowledge graph analysis, tasks, properties. Not for Notion sync (use notion-sync). |
| compatibility | Requires Obsidian 1.12+ with CLI support and app running. macOS: /Applications/Obsidian.app/Contents/MacOS/obsidian |
CLI reference: See ../_OBSIDIAN.md for full command reference.
Integration: See ../_SECOND_BRAIN.md for category routing when adding knowledge.
obsidian daily:append content="- [ ] <task or note>" silent
obsidian backlinks file=<name> counts
obsidian links file=<name>
obsidian orphans total
obsidian deadends total
obsidian unresolved verbose
obsidian search query="<term>" matches limit=10
obsidian read file=<result>
# 1. Read existing content to check for duplicates
obsidian read file="Second Brain - <Topic>"
# 2. Append extracted content (follow _SECOND_BRAIN.md template)
obsidian append file="Second Brain - <Topic>" content="<extracted>"
# 3. Update timeline
obsidian append file="Second Brain - Timeline" content="- **YYYY-MM-DD** | [Topic] | Source: ..."
# Run the project onboarding protocol from _VAULT_CONTEXT.md
# Detects project info from CLAUDE.md, creates Overview/Log/Solutions, registers in MOC
# See _VAULT_CONTEXT.md "Project Onboarding" for full steps
When the Obsidian CLI is unavailable (app not running, CLI errors, tool not found), access vault markdown files directly.
Vault path: '/Users/maroffo/Library/Mobile Documents/iCloud~md~obsidian/Documents'
.md files in the vault path<vault>/<note name>.md (subfolders for organized notes)--- delimiters<vault>/Daily Notes/YYYY-MM-DD.mdobsidian searchsilent flag for create/append when user doesn't need the note openedfile=<name> (wikilink resolution) over path= for convenience../_SECOND_BRAIN.md routing\n for newlines in content stringsExecution trace capture and token baselining. Use when user says trace, extract trace, count tokens, token baseline, or /harness-trace. Not for harness optimization (use harness-mechanic).
Release prep and tagging with pre-flight verification. Use when user says release, tag, ship it, push to production, create release, or bump version. Not for editing a version string outside a release, a lockfile or a changelog entry by hand, and not for reading what changed in a past release: those are ordinary edits, just do them.
Mine LEARNING.md retrospectives across all repos for recurring failure-modes, then propose harness changes (hooks, rules, skills, checklist items) with falsifiable change-contracts. Also runs the doc-gardening pass over the governance docs (stale rules, dead cross-references, skill-table drift). Use when user says learning loop, mine learnings, recurring failures, what should I fix in my process, cross-repo retrospective, doc gardening, stale docs, or run learning-loop. Runs on human schedule, never autonomously. Not for single-project retrospectives (use learning-docs) or trace/token analysis (use harness-mechanic).
Full contractor-mode loop: sub-protocols (LOCALIZE, BENCH-BASELINE, REPRODUCE, DRIFT), review routing by file pattern, blast radius, UAT, parallelism and effort caps, escalation, just-do-it, goal-backed runs. Load it to RUN that loop, once you have an approved plan and are entering step 1, or when a step needs its detail. It is a protocol, not a way to do the work: it never replaces the language, review or planning skill the task itself calls for, and a task small enough to just edit (SKIP_SET) needs none of it. The always-on spine lives in rules/orchestrator-protocol.md. Not for trace capture (harness-trace) or harness optimization (harness-mechanic).
Ruby on Rails with service-oriented architecture, Dry-validation, Sidekiq/Solid Queue, Hotwire. Use for Rails API, Rails services, Rails forms, RSpec, ActiveRecord, Rails migrations. Not for standalone Ruby gems (use ruby skill), and not for judging whether a migration is safe to run in production (that is the database-reviewer agent).
Get three independent second opinions (isolated Claude + isolated Gemini + isolated DeepSeek) on a problem Claude is analyzing. Use when user says second opinion, another perspective, challenge this approach, or asks gemini/deepseek about a decision, approach, or diagnosis. Also invoke on your own initiative, without being asked: on a complex task before planning, after 2 failed root-cause attempts, on a 🔴 decision (rewrite, core logic, security), or when the review loop is stuck below 80 after 2 fix rounds. Gathers context, writes a focused prompt, calls all reviewers in isolated Docker containers, and synthesizes all viewpoints. Not for reviewing code or changes, even phrased as 'ask gemini to review' (use gemini-review).