obsidian-web-clipper

Obsidian Web Clipper templates use precise JSON, variables, and triggers to reliably capture pages into your Obsidian vault. You can generate valid template JSON, import it into the Web Clipper, and customize properties and triggers for your target sites.

Web clipper template extraction fails when selectors and schema variables do not align with target site structures. Debugging involves adjusting schema-driven selectors and interpreter variables to match the specific domain's content layout and your vault conventions.

The best way to manage Web Clipper settings across sites is importing and exporting template JSON files. This allows you to reuse customized templates, adjust schema-driven selectors, and align clips to various domains while enforcing the template JSON schema.

Yes, schema-driven and selector-based extraction covers a wide range of web content. By defining schema and selector variables in your template JSON, you can reliably capture targeted page metadata and align it to your specific vault conventions.

Yes, understanding JSON structure is necessary because Obsidian Web Clipper templates require precise JSON syntax. The Skill validates your template against the JSON schema and helps generate or debug schema, selector, and interpreter variables.

Auto-matching triggers require precise configuration to safely target intended sites without mismatching. Limitations include ensuring triggers accurately match target domains and adhering to documented safety cautions to prevent incorrect page captures into your vault.