obsidian-extract-inbox

Extract structured document proposals from Obsidian inbox markdown notes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BreakerOfStems/claude-skills --skill obsidian-extract-inbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-extract-inbox
Source: https://github.com/BreakerOfStems/claude-skills/tree/main/skills/obsidian-extract-inbox
Command: npx skills add https://github.com/BreakerOfStems/claude-skills --skill obsidian-extract-inbox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms disorganized notes from an Obsidian inbox into structured, actionable document proposals, reducing the manual effort of organizing raw information.

Core Features & Use Cases

  • Inbox Processing: Analyzes raw notes from specified inbox directories.
  • Proposal Generation: Creates structured document proposals with titles, summaries, and suggested sections.
  • Uncertainty Flagging: Identifies and flags ambiguous content for human review.
  • Use Case: You've captured many quick thoughts and fragments in your Obsidian inbox over a week. Use this Skill to automatically group related fragments, suggest titles and structures for new documents, and highlight anything that needs your direct attention before formalizing.

Quick Start

Process all markdown files in the '_inbox/' directory and generate structured document proposals.

Frequently Asked Questions about obsidian-extract-inbox

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

FAQPage Schema
How do I structure messy Obsidian inbox notes into organized documentation?

To structure messy Obsidian inbox notes, this Skill parses raw markdown files, identifies content boundaries, and classifies document types to generate structured proposals with titles, summaries, and suggested sections.

What is the best way to extract document proposals from raw markdown capture data?

Extracting document proposals from raw markdown capture data involves analyzing textual fragments in inbox directories, grouping related content, and flagging uncertainties for human review before formatting into canonical documentation.

How do I process an Obsidian inbox directory to group related note fragments automatically?

Processing an Obsidian inbox directory requires parsing markdown files to identify source fragments, classifying textual content boundaries, and automatically grouping related fragments into actionable document structures.

Does this Skill flag ambiguous content when organizing raw notes into proposals?

Yes, organizing raw notes into proposals includes uncertainty flagging, which identifies and highlights ambiguous content fragments within the Obsidian inbox notes for direct human review before formalizing documentation.

Can I use this to classify document types from unstructured markdown files?

Yes, you can classify document types from unstructured markdown files by applying textual analysis to parse content boundaries, allowing the Skill to suggest canonical documentation formats for your inbox notes.