← ClaudeAtlas

clippingslisted

Process a Web Clippings inbox (e.g. Obsidian Web Clipper output) one item at a time. Analyze each, recommend an action (act, save, backlog, ignore), execute on confirmation, then delete the clipping. GTD-style triage for captured articles and YouTube transcripts.
ozlar34/claude-code-skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill ozlar34/claude-code-skills
# Clippings — Web Clippings Inbox Processor Process a folder of captured articles / YouTube transcripts using GTD methodology: one item at a time, analyze, decide, execute, delete. ## Configuration Edit this default at the top of this file before first use: ``` CLIPPINGS_DIR : <ABSOLUTE_PATH_TO_INBOX> ``` This is wherever your web-clipper writes new captures. For Obsidian Web Clipper that's typically a folder inside your vault, e.g.: ``` ~/Library/Mobile Documents/iCloud~md~obsidian/Documents/<VaultName>/Web Clippings/ ``` Everything in `CLIPPINGS_DIR` is unprocessed. Once processed, it gets deleted. ## Workflow ### Step 0: Count clippings Count how many `.md` files are in `CLIPPINGS_DIR` and report: "You have N clippings to process." If zero, say so and stop. ### Step 1: Present a clipping For each clipping file in the folder: 1. Read the full file 2. Determine the type from frontmatter `type` field: - `type: youtube` → YouTube transcript - `type: article` (or missing) → Article 3. Present: ``` ### [N/total] Title **Type:** YouTube / Article **Source:** [link] **Published:** date | **Clipped:** date **TL;DR:** 2-3 sentence summary of the content. **Why this matters to you:** 1-2 sentences connecting (or not connecting) this to the user's active projects, goals, or interests. Be honest — if it's not relevant, say so. **Recommended action:** [one of the actions below] — because [reason] ``` ### Step 2: User decides Present the action options. The user