一键在 Manus 中运行任何 Skill

obsidian-capture

星标4

分支0

更新时间2026年5月14日 19:38

Save a note, decision, or thought to the Obsidian vault right now. Use when someone says "capture this", "save this to Obsidian", "note this down", "log this decision", "obsidian note", "save this for later", "capture that idea". Requires OBSIDIAN_VAULT_PATH to be set.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

chuckplayer

chuckplayer/claude-agent-pack

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Obsidian Capture

Save an ad-hoc note, decision, or thought to the vault immediately. Captures always land in Claude/captures/ (global, not project-specific) and are linked into the project's daily note automatically.

Step 1 — Check configuration

Read OBSIDIAN_VAULT_PATH from the environment:

Bash: bash -c 'echo $OBSIDIAN_VAULT_PATH'
PowerShell: $env:OBSIDIAN_VAULT_PATH

If empty, stop and tell the user:

"OBSIDIAN_VAULT_PATH is not set. Re-run install.sh and provide your vault path when prompted, or add it manually to ~/.claude/settings.json under the env key."

Step 2 — Collect content

Ask the user: "What do you want to capture?"

Accept a title and body, or just body text (title will default to the first line of the body if not provided separately).

Step 3 — Write capture file (REST API if key present, filesystem fallback)

3a. REST API attempt (skip if `OBSIDIAN_REST_API_KEY` is empty)

If the key is set, attempt to write the capture file via PowerShell.

Vault-relative capture path (always): Claude/captures/<YYYY-MM-DD>-<HHmm>.md

Build the capture markdown (same format obsidian-writer would produce):

---
type: claude/capture
project: <project>
date: <YYYY-MM-DD>
captured_at: <YYYY-MM-DDThh:mm>
tags: [claude, capture]
---

## <title>

<body>

Attempt the PUT — try PowerShell first, curl fallback:

PowerShell (Windows PS5.1 or PS7, or macOS/Linux with pwsh installed):

$key    = $env:OBSIDIAN_REST_API_KEY
$port   = if ($env:OBSIDIAN_REST_API_PORT) { $env:OBSIDIAN_REST_API_PORT } else { "27124" }
$scheme = if ($env:OBSIDIAN_REST_API_HTTPS -eq 'false') { 'http' } else { 'https' }
$vaultRel = "Claude/captures/<YYYY-MM-DD>-<HHmm>.md"
$url    = "${scheme}://127.0.0.1:${port}/vault/${vaultRel}"
$body   = @"<capture markdown content>"@
$irm = @{ Method='Put'; Uri=$url; Body=$body; ContentType='text/markdown'; TimeoutSec=5
          Headers=@{"Authorization"="Bearer $key";"Content-Type"="text/markdown"} }
try {
    if ($PSVersionTable.PSVersion.Major -ge 7) {
        Invoke-RestMethod @irm -SkipCertificateCheck
    } else {
        [Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}
        [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
        Invoke-RestMethod @irm
    }
    $apiWritten = $true
} catch {
    $apiWritten = $false
}

If PowerShell tool is unavailable (macOS/Linux without pwsh), use curl via Bash:

KEY="$OBSIDIAN_REST_API_KEY"
PORT="${OBSIDIAN_REST_API_PORT:-27124}"
SCHEME=$([ "$OBSIDIAN_REST_API_HTTPS" = "false" ] && echo "http" || echo "https")
VAULT_REL="Claude/captures/<YYYY-MM-DD>-<HHmm>.md"
BODY='<capture markdown content>'
STATUS=$(curl -sk -X PUT \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: text/markdown" \
  --data-binary "$BODY" \
  -w "%{http_code}" -o /dev/null \
  "${SCHEME}://127.0.0.1:${PORT}/vault/${VAULT_REL}")
[ "${STATUS:-0}" -ge 200 ] && [ "${STATUS:-0}" -lt 300 ] && apiWritten=true || apiWritten=false

If $apiWritten is $true: dispatch obsidian-writer with session_api_written: true (obsidian-writer will skip capture file creation and only append the daily note)
If $apiWritten is $false: dispatch obsidian-writer normally

3b. Dispatch obsidian-writer

Invoke the obsidian-writer agent with:

write_mode: capture
vault_path: value of OBSIDIAN_VAULT_PATH
projects_folder: value of OBSIDIAN_PROJECTS_FOLDER (empty string if unset)
title: user's title
body: user's body text
project: basename of current working directory
timestamp: current datetime in YYYY-MM-DDThh:mm format
session_api_written: true if 3a succeeded, false otherwise

Step 4 — Confirm

Report the file path and write method. Example:

"Captured to Claude/captures/2026-05-14-1430.md (via REST API)"

or:

"Captured to Claude/captures/2026-05-14-1430.md (filesystem)"

Gotchas

Capture files always go to Claude/captures/ — they are not project-scoped.
If OBSIDIAN_REST_API_KEY is missing: skip step 3a entirely and dispatch obsidian-writer with session_api_written: false.
The daily note append is always handled by obsidian-writer (filesystem).
If obsidian-writer reports the vault directory doesn't exist, tell the user to verify the path in ~/.claude/settings.json.

同仓库更多 Skills

同仓库

implement

chuckplayer/claude-agent-pack

Orchestrates the full agent-pack pipeline for a task: git-engineer → [tech-lead] → engineer(s) → code-reviewer → [security-reviewer] → [performance-reviewer] → smell-reviewer → test-engineer → merge-reviewer → git-engineer (push/PR). Use when implementing a feature, fix, or change end-to-end. Trigger this when someone says: implement this, build this feature, make this change, add this functionality, code this up, I need this feature built, ship this. Do NOT use for targeted bug fixes with a known root cause — use /hotfix or /debug instead. Do NOT use for pure restructuring with no behavior change — use /refactor instead.

2026-07-164

review-pr

chuckplayer/claude-agent-pack

Review changed files or an open PR with code-reviewer, smell-reviewer, security-reviewer, and performance-reviewer. Use when the user wants a quality check on a diff, a PR number, or the current working-tree changes without running the full implement pipeline. Trigger this when someone says: review my PR, check my code, look at this diff, quality check, code review, does this look good, review PR #123, give me feedback on these changes, smell check, structural review. Do NOT use when the user wants to implement new changes — use /implement instead.

2026-07-164

plan

chuckplayer/claude-agent-pack

Decompose a complex task using tech-lead and optionally pressure-test the plan using devils-advocate before implementation begins. Use when the task is ambiguous, spans multiple concerns, or when the user wants to stress-test an existing proposal before committing. Trigger this when someone says: how should I approach this, plan this out, I am not sure how to do this, think through this with me, is this a good approach, pressure-test my plan, help me design this. Do NOT use when the task is already well-scoped — go straight to /implement instead.

2026-07-154

refactor

chuckplayer/claude-agent-pack

Refactor existing code with impact analysis first. Routes to tech-lead for blast-radius assessment, then engineers, with heavy emphasis on test coverage. Use when restructuring code with no intended behavior change. Trigger this when someone says: refactor this, clean up this code, extract this pattern, restructure this, this code is messy, improve the code structure, rename this across the codebase, remove duplication. Do NOT use when the change modifies behavior — use /implement instead. Do NOT use for single-file cleanup — just edit the file directly.

2026-07-154

scaffold

chuckplayer/claude-agent-pack

Scaffold a new feature end-to-end: API contract → database schema → backend service/controller → frontend. Use when building something new from scratch across multiple layers. More opinionated than /implement — always runs the full vertical slice in the correct dependency order. Trigger this when someone says: build this feature from scratch, scaffold a new endpoint, I need a full-stack feature, new feature end-to-end, build the whole thing. Do NOT use when the task is already partially built or only one layer needs changes — use /implement instead.

2026-07-154

devops-azure

chuckplayer/claude-agent-pack

Read and create Azure DevOps work items and PRs via the az CLI (devops extension) for the org/projects configured in AZURE_DEVOPS_ORG/AZURE_DEVOPS_PROJECTS. Use for one-off Azure Boards/Repos operations outside the code pipeline: viewing or creating work items, viewing PRs, commenting, updating state, linking work items to PRs/commits. Trigger this when someone says: check my work items, list open PRs in Azure DevOps, create a work item, comment on PR #N, close this work item, link this commit to a work item, connect to azure devops, smoke test the az cli. Do NOT use for GitHub PRs/issues -- that's skills/devops-github. Do NOT use for a full code review or implementation pipeline -- use /review-pr or /implement instead.

2026-07-104

name	obsidian-capture
description	Save a note, decision, or thought to the Obsidian vault right now. Use when someone says "capture this", "save this to Obsidian", "note this down", "log this decision", "obsidian note", "save this for later", "capture that idea". Requires OBSIDIAN_VAULT_PATH to be set.

Obsidian Capture

Step 1 — Check configuration

Read OBSIDIAN_VAULT_PATH from the environment:

Bash: bash -c 'echo $OBSIDIAN_VAULT_PATH'
PowerShell: $env:OBSIDIAN_VAULT_PATH

If empty, stop and tell the user:

"OBSIDIAN_VAULT_PATH is not set. Re-run install.sh and provide your vault path when prompted, or add it manually to ~/.claude/settings.json under the env key."

Step 2 — Collect content

Ask the user: "What do you want to capture?"

Accept a title and body, or just body text (title will default to the first line of the body if not provided separately).

Step 3 — Write capture file (REST API if key present, filesystem fallback)

3a. REST API attempt (skip if `OBSIDIAN_REST_API_KEY` is empty)

If the key is set, attempt to write the capture file via PowerShell.

Vault-relative capture path (always): Claude/captures/<YYYY-MM-DD>-<HHmm>.md

Build the capture markdown (same format obsidian-writer would produce):

---
type: claude/capture
project: <project>
date: <YYYY-MM-DD>
captured_at: <YYYY-MM-DDThh:mm>
tags: [claude, capture]
---

## <title>

<body>

Attempt the PUT — try PowerShell first, curl fallback:

PowerShell (Windows PS5.1 or PS7, or macOS/Linux with pwsh installed):

$key    = $env:OBSIDIAN_REST_API_KEY
$port   = if ($env:OBSIDIAN_REST_API_PORT) { $env:OBSIDIAN_REST_API_PORT } else { "27124" }
$scheme = if ($env:OBSIDIAN_REST_API_HTTPS -eq 'false') { 'http' } else { 'https' }
$vaultRel = "Claude/captures/<YYYY-MM-DD>-<HHmm>.md"
$url    = "${scheme}://127.0.0.1:${port}/vault/${vaultRel}"
$body   = @"<capture markdown content>"@
$irm = @{ Method='Put'; Uri=$url; Body=$body; ContentType='text/markdown'; TimeoutSec=5
          Headers=@{"Authorization"="Bearer $key";"Content-Type"="text/markdown"} }
try {
    if ($PSVersionTable.PSVersion.Major -ge 7) {
        Invoke-RestMethod @irm -SkipCertificateCheck
    } else {
        [Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}
        [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
        Invoke-RestMethod @irm
    }
    $apiWritten = $true
} catch {
    $apiWritten = $false
}

If PowerShell tool is unavailable (macOS/Linux without pwsh), use curl via Bash:

KEY="$OBSIDIAN_REST_API_KEY"
PORT="${OBSIDIAN_REST_API_PORT:-27124}"
SCHEME=$([ "$OBSIDIAN_REST_API_HTTPS" = "false" ] && echo "http" || echo "https")
VAULT_REL="Claude/captures/<YYYY-MM-DD>-<HHmm>.md"
BODY='<capture markdown content>'
STATUS=$(curl -sk -X PUT \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: text/markdown" \
  --data-binary "$BODY" \
  -w "%{http_code}" -o /dev/null \
  "${SCHEME}://127.0.0.1:${PORT}/vault/${VAULT_REL}")
[ "${STATUS:-0}" -ge 200 ] && [ "${STATUS:-0}" -lt 300 ] && apiWritten=true || apiWritten=false

If $apiWritten is $true: dispatch obsidian-writer with session_api_written: true (obsidian-writer will skip capture file creation and only append the daily note)
If $apiWritten is $false: dispatch obsidian-writer normally

3b. Dispatch obsidian-writer

Invoke the obsidian-writer agent with:

write_mode: capture
vault_path: value of OBSIDIAN_VAULT_PATH
projects_folder: value of OBSIDIAN_PROJECTS_FOLDER (empty string if unset)
title: user's title
body: user's body text
project: basename of current working directory
timestamp: current datetime in YYYY-MM-DDThh:mm format
session_api_written: true if 3a succeeded, false otherwise

Step 4 — Confirm

Report the file path and write method. Example:

"Captured to Claude/captures/2026-05-14-1430.md (via REST API)"

or:

"Captured to Claude/captures/2026-05-14-1430.md (filesystem)"

Gotchas

Capture files always go to Claude/captures/ — they are not project-scoped.
If OBSIDIAN_REST_API_KEY is missing: skip step 3a entirely and dispatch obsidian-writer with session_api_written: false.
The daily note append is always handled by obsidian-writer (filesystem).
If obsidian-writer reports the vault directory doesn't exist, tell the user to verify the path in ~/.claude/settings.json.

obsidian-capture

Obsidian Capture

Step 1 — Check configuration

Step 2 — Collect content

Step 3 — Write capture file (REST API if key present, filesystem fallback)

3a. REST API attempt (skip if OBSIDIAN_REST_API_KEY is empty)

3b. Dispatch obsidian-writer

Step 4 — Confirm

Gotchas

同仓库更多 Skills

同仓库更多 Skills

Obsidian Capture

Step 1 — Check configuration

Step 2 — Collect content

Step 3 — Write capture file (REST API if key present, filesystem fallback)

3a. REST API attempt (skip if OBSIDIAN_REST_API_KEY is empty)

3b. Dispatch obsidian-writer

Step 4 — Confirm

Gotchas

3a. REST API attempt (skip if `OBSIDIAN_REST_API_KEY` is empty)

3a. REST API attempt (skip if `OBSIDIAN_REST_API_KEY` is empty)