The Obsidian Web Clipper imports templates via JSON files. The properties array defines the YAML frontmatter of the note. The Clipper template editor checks tem
Json Schema defines the structure and validation rules for templates used by the Obsidian Web Clipper. It specifies how metadata (YAML frontmatter) and note content are formatted and saved, enabling consistent and automated capture of web content as Markdown notes. The schema controls note creation behavior, naming conventions, content formatting, and auto-triggering conditions based on URL patterns or Schema.org types.
This skill ensures that templates are syntactically correct and logically valid before use, reducing errors in large-scale clipping workflows. It supports variables, conditional logic, and loops within content and metadata fields, allowing marketers to tailor notes precisely to data they want to extract and organize.
This skill is designed for growth leads and content strategists who manage large content repositories and need structured, automated content capture workflows. SEO specialists who curate research or competitor data from the web will find it valuable for creating standardized note templates with metadata to streamline analysis. Agency strategists handling multiple client URLs can use triggers to automate content capture for diverse campaigns, ensuring consistent data collection across platforms.
First, a practitioner defines the root JSON structure of the template, specifying the note creation behavior, folder path, and naming pattern, aligning with their content organization strategy. Next, they configure the properties array to establish YAML frontmatter fields, selecting appropriate types like text, datetime, or checkbox, and embedding dynamic variables or logic as needed.
Then, they add triggers to automate template selection based on URL patterns or schema types detected on target pages, enabling hands-free clipping for prioritized content sources. Finally, they validate the template syntax using the Clipper’s built-in editor to catch logic or formatting errors before deployment, ensuring smooth integration into daily clipping routines.
How do I control where clipped notes are saved? Set the `path` property in the root schema to a folder for new notes or a full file path to append to an existing note. Can I use dynamic variables in metadata fields? Yes, property `value` fields accept variables and template logic for dynamic content generation. What triggers automation of templates? Triggers can be URL patterns or Schema.org types present on the page, which the Clipper uses to select the template automatically.
Attach the Json Schema skill to any Metaflow agent tasked with managing content capture or note generation workflows. When running, the agent will validate and apply the specified template schema to incoming web content, producing structured Markdown notes with metadata. This ensures consistent formatting and reliable automation for your clipping processes. You can configure triggers and properties directly in your Metaflow setup to align with campaign goals and data requirements.
For broader context, see our roundup of marketing skills claude, and read Claude skills for SEO for related setup guidance.