clippings-process

Convert Obsidian web clippings into summarized notes in 2_Areas subfolders.

Updated Aug 14, 2012
One-click install
npx skills add https://github.com/dakotahp/dotfiles --skill clippings-process
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clippings-process
Source: https://github.com/dakotahp/dotfiles/tree/main/dot_config/claude/skills/clippings-process
Command: npx skills add https://github.com/dakotahp/dotfiles --skill clippings-process

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow processes web clippings from an Obsidian vault's Clippings/ folder, summarizes each clipping, and files it into the appropriate 2_Areas/ subfolder in the personal vault, then removes the original clipping.

Core Features & Use Cases

  • Clipping intake & summarization: reads clippings, extracts metadata (title, source, author, created, tags) and the body, and generates a concise summary note.
  • Routing by tags: matches clipping tags to a best-fit 2_Areas subfolder in ObsidianPersonal based on semantic similarity of tags.
  • Metadata-rich notes: creates a new markdown file with frontmatter including source, author, clipped date, and tags.
  • Safe disposal: deletes the original clipping after successful processing to avoid duplication.

Quick Start

Run the clippings-process command to organize clippings from Obsidian Work into your personal 2_Areas structure.

Frequently Asked Questions about clippings-process

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically organize and summarize web clippings in an Obsidian vault?

To summarize Obsidian clippings, the workflow parses YAML frontmatter for tags and matches them to the best-fitting 2_Areas subfolder. It then creates a metadata-rich note with a concise summary and removes the original clipping.

How does routing by tags work when filing Obsidian notes?

Tag-based routing matches clipping tags to a 2_Areas subfolder using semantic similarity. The workflow reads tags from the YAML frontmatter and files the summarized note into the best-fitting folder.

Do I need the Obsidian CLI to process clippings across multiple vaults?

Yes, the Obsidian CLI is required. The workflow operates across ObsidianWork and ObsidianPersonal vaults, using the CLI to read clippings and write summarized notes to the personal vault.

What happens to the original web clipping after it is processed into a summary note?

The original clipping is deleted after successful processing to prevent duplication. This safe disposal mechanism ensures your vault remains clean and free of redundant content.

Can I use this workflow to file clippings into subfolders other than the 2_Areas structure?

No, this workflow specifically targets the 2_Areas subfolder structure within ObsidianPersonal. It routes clippings based on semantic tag matching and does not support alternative folder hierarchies.

What metadata is included when converting an Obsidian clipping into a summarized note?

The workflow creates a markdown file with YAML frontmatter containing source, author, clipped date, and tags. This metadata is extracted from the original clipping alongside the body content.