What problem does it solve? Web clippings captured in an Obsidian inbox arrive as raw stubs that need enrichment, categorization, and note creation without flooding the coordinating agent's context with full article content. This Skill processes a single clipping end-to-end and returns only a compact proposal. ## Core Features & Use Cases - Domain-aware content fetching: Routes YouTube URLs to transcript tools, X/Twitter links to the X-API, and other articles to Firecrawl scraping. - Atomic note creation: Creates the resource note and injects Layer 1 captured notes in a single para_create call, keeping full content out of the coordinator context. - Structured proposals: Returns a ~500-byte JSON proposal with title, summary, area/project wikilinks, resource type, and verification status. - Use Case: During inbox triage, a clipped Twitter thread is fetched via X-API, classified as a thread resource, linked to the relevant area and project, and filed under 03 Resources/ with formatted Layer 1 notes. ## Quick Start Analyze the clipping at '00 Inbox/✂️ Article Title.md' and return a triage proposal with the created resource note.