From obsidian
Creates structured Korean Obsidian notes documenting non-code decisions—research, investigations, planning, design choices—via user interview. Logs problem, options considered, decision reached. No git context needed.
npx claudepluginhub orange-brother/obsidian-skills --plugin obsidianThis skill uses the workspace's default tool permissions.
Turn a non-code decision or investigation into a structured Obsidian note. No git context — entirely driven by interview. Designed for research, design choices, planning, and any work where thinking and judgment matter more than code changes.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
Turn a non-code decision or investigation into a structured Obsidian note. No git context — entirely driven by interview. Designed for research, design choices, planning, and any work where thinking and judgment matter more than code changes.
VAULT_PATH = /path/to/your/vault/Dev Logs
Replace with the actual folder path in your Obsidian vault.
Check if VAULT_PATH is still set to the placeholder value /path/to/your/vault/Dev Logs.
If it is:
If VAULT_PATH is already configured, skip this step silently.
The user provides:
If missing, ask for it before proceeding.
Use the obsidian-cli skill to search for existing notes related to this topic:
obsidian search query="{topic-name}" limit=10
obsidian search query="decision-log" limit=10
If Obsidian is not running, skip silently and proceed without wikilinks.
Ask the following 5 questions all at once:
Use the obsidian-markdown skill for structure — frontmatter, headings, callouts, and wikilinks.
Use the human-writer skill for all prose content within each section. Apply its vocabulary, structural, and voice rules to every sentence written. The text should sound like the user wrote it, not like an AI summarized it.
Save the file to:
{VAULT_PATH}/{YYYY-MM-DD}-{topic-name}.md
Where {topic-name} is the topic name lowercased with spaces replaced by hyphens.
frontmatter → title, date, tags: [decision-log], status: done
# {Topic Name}
## 배경 / 문제 → 왜 이 결정이 필요했는지
## 검토한 것들 → 조사하거나 참고한 것들, [[wikilinks]] where relevant
## 고려한 옵션 → 선택지와 각각의 장단점
→ use > [!warning] for tradeoffs
## 결정 및 근거 → 최종 결정, 1인칭으로
→ use > [!insight] for the key reasoning
## 다음 액션 → use > [!question] for unresolved items, omit if nothing
You MUST write the entire log in Korean, regardless of the language the user used. Keep each section concise — this is a log, not documentation.