obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
Documentation
Obsidian Web Clipper Template Creator
This skill helps you create importable JSON templates for the Obsidian Web Clipper.
Workflow
- Identify User Intent: specific site (YouTube), specific type (Recipe), or general clipping?
- Check Existing Bases: The user likely has a "Base" schema defined in
Templates/Bases/.- Action: Read
Templates/Bases/*.baseto 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.
- Action: Read
- 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 (REQUIRED): Use
WebFetchor a browser DOM snapshot to retrieve page content before choosing any selector. - Action: Analyze the HTML for Schema.org JSON, Meta tags, and CSS selectors.
- Action (REQUIRED): Verify each selector against the fetched content. Do not guess selectors.
- See references/analysis-workflow.md for analysis techniques.
- Draft the JSON: Create a valid JSON object following the schema.
- Verify Variables: Ensure the chosen variables (Preset, Schema, Selector) exist in your analysis.
- Action (REQUIRED): If a selector cannot be verified from the fetched content, state that explicitly and ask for another URL.
- See references/variables.md.
Selector Verification Rules
- Always verify selectors against live page content before responding.
- Never guess selectors. If the DOM cannot be accessed or the element is missing, ask for another URL or a screenshot.
- Prefer stable selectors (data attributes, semantic roles, unique IDs) over fragile class chains.
- Document the target element in your reasoning (e.g., "About sidebar paragraph") to reduce mismatch.
Output Format
ALWAYS output the final result as a JSON code block that the user can copy and import.
{
"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
Examples
See assets/ for JSON examples.
Quick Info
- Source
- antigravity
- Category
- Document Processing
- Repository
- View Repo
- Scraped At
- Jan 26, 2026
Tags
Related Skills
ab-test-setup
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
algorithmic-art
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.