Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

process-clippings

Sterne15

Forks2

Aktualisiert4. Juli 2026 um 20:46

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).

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

maroffo

maroffo/claude-forge

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Allgemeine BürokräfteBüro- und Verwaltungsberufe·SOC 43-9061

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

harness-trace

maroffo/claude-forge

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).

2026-07-2515

releasing-software

maroffo/claude-forge

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.

2026-07-2515

learning-loop

maroffo/claude-forge

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).

2026-07-2515

orchestrator

maroffo/claude-forge

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).

2026-07-2515

rails

maroffo/claude-forge

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).

2026-07-2515

second-opinion

maroffo/claude-forge

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).

2026-07-2515

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"]

ABOUTME: Process web clippings from Obsidian vault into Second Brain via CLI

ABOUTME: Reads clippings, categorizes, extracts knowledge, integrates, archives

Process Clippings Skill

Process web clippings from the Clippings folder and integrate them into the Second Brain.

Obsidian CLI: See ../_OBSIDIAN.md | Integration: See ../_SECOND_BRAIN.md

Vault Structure

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

Processing Workflow

Step 1: Find Clippings

obsidian files folder=Clippings ext=md

Step 2: For Each Clipping

Read the clipping:

obsidian read path="Clippings/<file>.md"

Categorize per ../_SECOND_BRAIN.md routing table
Decide: Actionable (tutorials, patterns, code) -> Second Brain | Reference only -> Bookmarks
Extract & integrate per ../_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"

Step 3: Archive Clipping

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"

Output Format

After processing each clipping, report:

Processed: [Clipping Title]
  -> Added to: Second Brain - [File].md
  -> Type: [Actionable/Reference]
  -> Key insight: [1-line summary]

Rules

See ../_SECOND_BRAIN.md for shared rules. Additional:

Code examples: only if genuinely useful, keep minimal