obsidian-clipper-template-creator

Generate importable Obsidian Web Clipper JSON templates from a target page and Base definition.

Updated Nov 29, 2025
One-click install
npx skills add https://github.com/thimslugga/agent-skills --skill obsidian-clipper-template-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-clipper-template-creator
Source: https://github.com/thimslugga/agent-skills/tree/main/skills/obsidian/obsidian-clipper-template-creator
Command: npx skills add https://github.com/thimslugga/agent-skills --skill obsidian-clipper-template-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Obsidian users often need consistent, structured templates for clipping web content. This Skill automates the creation of JSON templates for the Obsidian Web Clipper by leveraging a defined Base to map page data to the note frontmatter.

Core Features & Use Cases

  • Generate importable Obsidian Web Clipper JSON templates by analyzing a target page and a selected Base.
  • Map data from Schema.org, meta tags, or CSS selectors to frontmatter fields per the Base definition, enabling uniform note structure.
  • Reuse examples from Templates/Bases and assets to illustrate expected output or plug into existing workflows.

Quick Start

Provide a sample URL and the target Base to generate a ready-to-import template.

Frequently Asked Questions about obsidian-clipper-template-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Obsidian Web Clipper templates from web pages?

To create Obsidian Web Clipper templates, provide a target page URL and a Base definition to automatically extract schema.org data, meta tags, or CSS selectors and map them to structured note frontmatter. This generates a ready-to-import JSON template for consistent clipping.

How does mapping web page data to Obsidian note frontmatter work?

Mapping web page data to Obsidian note frontmatter works by applying a defined Base schema to extract target page elements like schema.org metadata or CSS selectors. The extracted data is then automatically validated and mapped to corresponding frontmatter properties in the output JSON template.

Can I use a single Obsidian Web Clipper template for different types of content like recipes and articles?

Yes, you can use the template generation process for diverse clipping scenarios like recipes, articles, or notes. By analyzing the target page and applying your selected Base definition, the output adapts to extract the relevant schema.org data or meta tags for each specific content type.

What is the best way to ensure consistent frontmatter structure when clipping web content to Obsidian?

The best way to ensure consistent frontmatter structure is to enforce a defined JSON schema and Base mapping validation workflow during template creation. This guarantees that data extracted from meta tags or CSS selectors uniformly populates the exact frontmatter properties required by your Obsidian vault.

Do I need a Base definition to generate an Obsidian Web Clipper JSON template?

Yes, a Base definition is required to generate a Web Clipper JSON template. The Base provides the necessary schema and frontmatter mapping rules that dictate how extracted page data from schema.org, meta tags, or CSS selectors is structured and validated for your Obsidian notes.

Why are my extracted web page properties not mapping correctly to Obsidian frontmatter?

Incorrect frontmatter mapping often occurs when the target page lacks standard schema.org data or when CSS selectors fail to match the content structure. Generating a template from a valid Base definition enforces the proper JSON schema and validation workflow to prevent these mapping errors.