content-processing

What problem does it solve? It standardizes the create-inject-commit pipeline for turning enriched content (articles, transcripts, meetings) into properly formatted Obsidian notes, eliminating inconsistent frontmatter, null-value pollution, and redundant tool calls. ## Core Features & Use Cases - Single-call note creation: Uses the content parameter on para_create to create a note, inject body sections, and auto-commit in one invocation for resources and meetings. - Null-safety and field validation: Enforces omitting null args and filters invalid fields against validArgs from para_template_fields to keep frontmatter clean. - Post-creation verification: Reads back frontmatter with para_fm_get, detects mismatches, self-repairs via para_fm_set, and reports a verification status. - Use Case: During inbox triage, a worker agent classifies a YouTube link as a resource, creates the note with Layer 1 transcript excerpts injected, and commits it to the vault in one call. ## Quick Start Create a resource note from this enriched article content, inject the Layer 1 summary into the captured notes section, and commit it to my vault.