菜单
Process web clippings into Second Brain. Use when user mentions clippings, asks to process articles, or wants to integrate saved content. Not for newsletters (use newsletter-digest) or email bookmarks (use process-email-bookmarks).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execution 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).
| name | process-clippings |
| description | Process web clippings into Second Brain. Use when user mentions clippings, asks to process articles, or wants to integrate saved content. Not for newsletters (use newsletter-digest) or email bookmarks (use process-email-bookmarks). |
| compatibility | Requires Obsidian CLI (obsidian MCP commands). |
| allowed-tools | ["Bash","Read","WebFetch"] |
Process web clippings from the Clippings folder and integrate them into the Second Brain.
Obsidian CLI: See ../_OBSIDIAN.md | Integration: See ../_SECOND_BRAIN.md
Documents/ (vault)
├── Clippings/ ← Inbox (unprocessed)
│ └── Processed/ ← Archive
├── Second Brain/ ← Destination for actionable knowledge
│ ├── Second Brain - AI Agents and Tools.md
│ ├── Second Brain - Claude Code.md
│ ├── Second Brain - Development.md
│ ├── Second Brain - DevOps and Cloud.md
│ └── Second Brain - Engineering Management.md
└── Bookmarks/ ← Reference links only
obsidian files folder=Clippings ext=md
obsidian read path="Clippings/<file>.md"
../_SECOND_BRAIN.md routing table../_SECOND_BRAIN.md content template:# Append to destination
obsidian append file="Second Brain - <Topic>" content="<extracted>"
# Update timeline
obsidian append file="Second Brain - Timeline" content="- **YYYY-MM-DD** | [Topic] | Source: Clipping | -> Second Brain - <File>.md"
After successful integration:
obsidian move path="Clippings/<file>.md" to="Clippings/Processed/<file>.md"
Or if user prefers, delete:
obsidian delete path="Clippings/<file>.md"
After processing each clipping, report:
Processed: [Clipping Title]
-> Added to: Second Brain - [File].md
-> Type: [Actionable/Reference]
-> Key insight: [1-line summary]
See ../_SECOND_BRAIN.md for shared rules. Additional: