菜单
Unified entry point for Obsidian daily-note captures and long-form notes. Triggers on "記一下 / log / 紀錄 / capture this / 寫到 journal" (→ cap mode) and "建立筆記 / new note / 寫一份筆記 / create a note on" (→ note mode). Also via `/obw:jot`. Requires `.obsidian.yaml`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | jot |
| description | Unified entry point for Obsidian daily-note captures and long-form notes. Triggers on "記一下 / log / 紀錄 / capture this / 寫到 journal" (→ cap mode) and "建立筆記 / new note / 寫一份筆記 / create a note on" (→ note mode). Also via `/obw:jot`. Requires `.obsidian.yaml`. |
Single triage skill. Decide the mode, then run the obsidian CLI directly — no sub-agent. For CLI syntax defer to the obsidian:obsidian-cli skill. If .obsidian.yaml is missing, tell the user to run /obw:init and stop.
Inspect the user's input:
#tag tokens, no explicit title, journaling/log verbs. Goes to today's daily note..obsidian.yaml note config).AskUserQuestion with two options: "Quick capture (daily note)" and "New long-form note".Append a timestamped bullet to today's daily note. Nothing more. Daily note folder / filename / template are owned by Obsidian's Daily Notes core plugin.
- HH:MM — <body> (any #tag tokens stay inline — Obsidian indexes them automatically).daily:append (creates the note if missing).[[<daily-note-basename>]].Example: 記一下 #worklog 完成了 API-first 架構 draft → - 14:32 — 完成了 API-first 架構 draft #worklog
Config (.obsidian.yaml):
vault: <VAULT_NAME>
note:
default_folder: Inbox
filename_strategy: title # title | slug | timestamp-title
Parse input:
title — required, first non-flag text.--folder <path> — override default folder (vault-relative, reject leading / or ..).--tag <tag> — repeatable, adds to frontmatter.Compute filename by kebab-casing the title (lowercase, whitespace/punctuation → -, collapse repeats). Keep Unicode characters intact.
title → <kebab>.mdslug → <kebab>-YYYYMMDD.mdtimestamp-title → YYYYMMDD-<kebab>.mdResolve path = <folder>/<filename>. Check for conflict (read) — if it exists, ask the user (overwrite / rename / cancel via AskUserQuestion).
Create the note at that path (create) with content:
---
created: YYYY-MM-DD
tags: [<tag1>, <tag2>]
---
# <original title, un-kebabbed>
<initial body, if provided>
Empty tag list → tags: []. Missing body → just frontmatter + H1.
Confirm — show vault-relative path and wikilink [[<basename>]].
Example: new note: API Redesign Proposal --folder Architecture --tag design --tag api — with filename_strategy: title → creates Architecture/api-redesign-proposal.md, returns [[api-redesign-proposal]].
Interactively create `.obsidian.yaml` and install starter templates (task / doc / adr) for this project. Triggers via `/obw:init` or when another obw skill reports missing config.
Obsidian Workspace PM — tasks, documents, and ADRs in your Obsidian vault. Triggers on task/doc/ADR lifecycle requests ("add a task", "create an ADR", "archive X", "list in-progress tasks", "refresh dashboard") and via `/obw:pm`. Requires `.obsidian.yaml` with a `pm.project` section.
Render markdown or Mermaid content as formatted HTML in the browser. Triggers when the user asks to view, render, or preview a document as HTML; when the user asks to visualize, diagram, chart, or draw architecture, flows, sequence/class/state/ER diagrams; when resolving plan files from ~/.claude/plans/; or proactively when about to output a table with 4+ rows or 3+ columns, a structured comparison, an audit, a feature matrix, or any formatted content exceeding ~50 lines in the terminal.
Offload dispatch to cheap/fast omp models via pi-agent.sh — name-addressed sub-agent verbs (start/send/poll/peek/ls/stop/watch) over background omp workers with idempotent poll, worktree isolation, and distilled reports. Main loads this to write the offload usage it embeds in a builder brief.
Use for live browser automation via the agent-browser CLI — open URLs, snapshot pages, click/fill/screenshot, inspect elements, scrape or read web pages. Ref-based workflow for AI agents. Not for writing Playwright test files (use playwright or web-test).
Use to write or set up Playwright / @playwright/test E2E tests — test specs, locators, assertions, fixtures, config. Focuses on structuring tests with high-precision locator strategies. Not for live page exploration or debugging (use agent-browser or web-test).