Skill

Create Obsidian Web Clipper Templates

Creates importable Obsidian Web Clipper JSON templates by verifying real page selectors and Schema.org data.

Works with obsidian

81
Spark score
out of 100
Updated yesterday
Version 15.7.0

Add to Favorites

Why it matters

Automate the creation of custom Obsidian Web Clipper templates by analyzing website structures and generating valid JSON configurations.

Outcomes

What it gets done

01

Analyze website DOM and schema data to identify relevant content.

02

Verify CSS selectors against live page content to ensure accuracy.

03

Generate importable JSON templates for the Obsidian Web Clipper.

04

Incorporate template logic for conditional content and data looping.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-obsidian-clipper-template-creator | bash

Overview

Obsidian Web Clipper Template Creator

Creates importable Obsidian Web Clipper JSON templates by mapping real DOM, Schema.org data, and CSS selectors, with mandatory live-page selector verification. Use when creating or refining an Obsidian Web Clipper template for a specific site or content type.

What it does

Creates importable JSON templates for the Obsidian Web Clipper by mapping a site's real DOM, Schema.org data, and CSS selectors into a valid clipping template, with mandatory live-page selector verification before any template is finalized.

When to use - and when NOT to

Use this skill when creating or refining an importable Obsidian Web Clipper template, mapping a site's real DOM/schema data/selectors into a valid clipping template, or needing selector verification and template logic guidance before handing off the JSON. Not a fit for Obsidian plugin development unrelated to the Web Clipper, or for templates where selectors cannot be verified against real page content.

Inputs and outputs

Follows a six-step workflow: identify user intent (specific site like YouTube, specific content type like Recipe, or general clipping); check for an existing "Base" schema in Bases/*.base and use its defined properties to structure the Clipper template; fetch and analyze a reference URL using WebFetch (or a browser DOM snapshot if WebFetch is unavailable) to find Schema.org JSON, meta tags, and CSS selectors, verifying every selector against the fetched content rather than guessing; draft the JSON template following the documented schema; add template logic only where it improves the template - conditionals for optional blocks (e.g. show nutrition data only if present), loops for list data, variable assignment to avoid repeated expressions, and fallbacks for missing variables; and verify that every chosen variable (Preset, Schema, Selector) actually exists in the analysis, explicitly flagging and requesting another URL if a selector cannot be verified.

Selector verification rules require always verifying against live page content, never guessing, preferring stable selectors (data attributes, semantic roles, unique IDs) over fragile class chains, and documenting the target element in reasoning to reduce mismatch. Output is always a JSON code block starting with schemaVersion and name fields, ready to copy and import, with any template logic following the Clipper's validated logic syntax so the template passes the editor's validation.

Integrations

Targets the Obsidian Web Clipper's JSON template format and its variables, filters, and logic systems, cross-referencing user-defined Obsidian "Base" schemas, and requiring WebFetch or a browser DOM snapshot tool to validate selectors against live pages.

Who it's for

Obsidian users building custom Web Clipper templates for specific sites or content types who need selectors and variables verified against real page content rather than a template built on assumptions that may not match the live DOM.

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

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.