Obsidian Web Clipper Template Creator

Workflow

1. Identify User Intent: specific site (YouTube), specific type (Recipe), or general clipping?
2. Check Existing Bases: The user likely has a "Base" schema defined in

   Templates/Bases/

   .
   • Action: Read

     Templates/Bases/*.base

     to find a matching category (e.g.,

     Recipes.base

     ).
   • Action: Use the properties defined in the Base to structure the Clipper template properties.
   • See references/bases-workflow.md for details.
3. Fetch & Analyze Reference URL: Validate variables against a real page.
   • Action: Ask the user for a sample URL of the content they want to clip (if not provided).
   • Action: Use

     WebFetch

     to retrieve the page HTML.
   • Action: Analyze the HTML for Schema.org JSON, Meta tags, and CSS selectors.
   • See references/analysis-workflow.md for analysis techniques.
4. Draft the JSON: Create a valid JSON object following the schema.
   • See references/json-schema.md.
5. Verify Variables: Ensure the chosen variables (Preset, Schema, Selector) exist in your analysis.
   • See references/variables.md.

Output Format

{
  "schemaVersion": "0.1.0",
  "name": "My Template",
  ...
}

Resources

• references/variables.md - Available data variables.
• references/filters.md - Formatting filters.
• references/json-schema.md - JSON structure documentation.
• references/bases-workflow.md - How to map Bases to Templates.
• references/analysis-workflow.md - How to validate page data.

Official Documentation

• Variables
• Filters
• Templates

Examples