菜单
Use when the user asks to create an Obsidian note with an agent team, deep research, strict verification, multiple angles, or phrases like "팀으로 조사해서 노트", "깊게 조사해서 옵시디언 노트", "/agentic-notes", "--team", "--verify strict", or "--deep". Do NOT use for a simple one-shot Obsidian note; use obsidian-note instead.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/sskim91/dotfiles --skill agentic-notes命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | agentic-notes |
| description | Use when the user asks to create an Obsidian note with an agent team, deep research, strict verification, multiple angles, or phrases like "팀으로 조사해서 노트", "깊게 조사해서 옵시디언 노트", "/agentic-notes", "--team", "--verify strict", or "--deep". Do NOT use for a simple one-shot Obsidian note; use obsidian-note instead. |
Obsidian 노트를 만들기 전에 여러 서브에이전트가 수집·검증·합성을 맡고, 마지막에는 obsidian-note의 leaf writer 규칙으로 노트 1장을 저장하는 상위 orchestration skill.
다음 신호가 있을 때 사용한다.
/agentic-notes--team [N]--verify strict 또는 --deep단순한 "노트로 저장해줘"는 obsidian-note로 처리한다.
--team 크기, strict 여부를 정한다. 기본 팀 크기는 4다.source-hunter: 공식 문서, 웹 출처, 최신 자료 수집vault-researcher: 기존 Obsidian vault에서 관련 노트와 연결 후보 조사skeptic: 주장 검증, 반례, outdated 정보, 과장 표현 탐지synthesizer: 팀 결과를 claim ledger와 노트 구조로 합성note-writer: 최종 결과를 obsidian-note 규칙으로 저장TASK, DELIVERABLE, SCOPE, VERIFY를 포함한다. 자세한 템플릿은 references/subagent-prompts.md를 읽는다.references/strict-verification.md를 읽고 claim ledger를 작성한다.note-writer 또는 lead가 obsidian-note를 사용해 _Inbox/{Title}.md 한 장으로 저장한다.| Intent | Claude Code | Codex |
|---|---|---|
| Spawn role worker | Agent with subagent_type: general-purpose | spawn_agent with fork_turns: "none" |
| Wait for results | wait for all Agent results | wait_agent, then integrate substantive final output |
| Follow up on silent worker | send targeted prompt | send_message or followup_task |
| Close worker | not usually explicit | close_agent after integrating result |
Every subagent assignment starts with:
TASK: <imperative assignment>
DELIVERABLE: <required artifact>
SCOPE: <allowed paths, sources, and boundaries>
VERIFY: <checks the subagent must run or report>
The final synthesis must include:
obsidian-noteSubagent output must follow references/subagent-prompts.md.
note-writer writes to the vault.Before reporting completion:
obsidian-note frontmatter and body structurerelated_notes links exist in the vaultReview Codex CLI changelog updates against the user's Codex and dotfiles configuration, then recommend which new features are worth adopting. Use when the user mentions "codex 변경사항", "codex changelog", "codex 업데이트 검토", "codex release notes", "codex 버전", "최근 codex 릴리스", gives a Codex CLI version range like 0.136.0..0.137.0, or asks what is worth adopting from Codex updates. Do NOT use for Claude Code changelogs, OpenAI SDK/API model changelogs, or general release-note reading without a dotfiles cross-reference.
Create detailed Korean GenOS patch notes by reconciling a target release with its predecessor across curated release metadata, Git tags and diffs, migrations, configuration changes, and available Notion content, then save the note to the user's Obsidian vault and maintain MOC discoverability. Use when the user asks for a GenOS version patch note, release note, upgrade summary, changes since a version, or customer-update release material such as "v1.8.7 패치노트", "1.8.6부터 변경사항", or "고객사 업데이트용 릴리스 노트". Do NOT use for generic GenOS knowledge capture, session logs, or customer-specific branch notes unless the user explicitly includes them.
Use when user mentions "Obsidian", "옵시디언", "write as note", "save to notes", "노트로 저장", or /obsidian-note command. Do NOT use for TIL (use til), YouTube notes (use youtube-summarizer), GenOS 작업 지식 캡처 (use genos-knowledge-capture), GenOS 패치노트·릴리스 노트 (use write-genos-patch-notes), or deep/team/multi-angle note research (use agentic-notes).