webclipper-templates

Manages a single Obsidian Web Clipper template for zero-decision capture and automatic classification.

6|1|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/nathanvale/side-quest-marketplace-old --skill webclipper-templates-nathanvale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webclipper-templates
Source: https://github.com/nathanvale/side-quest-marketplace-old/tree/main/plugins/para-obsidian/skills/webclipper-templates
Command: npx skills add https://github.com/nathanvale/side-quest-marketplace-old --skill webclipper-templates-nathanvale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Traditional web clippers force decisions at capture time—choosing templates, tags, and folders—which creates friction that fights against ADHD-friendly workflows. This Skill replaces that with a single universal capture template that sends everything to an inbox, deferring classification and organization to an automated review pipeline. ## Core Features & Use Cases - Single Capture Template: One capture.json template captures all web content to 00 Inbox/ with minimal metadata (type, source, date, domain) and zero decisions required. - Automatic Classification Pipeline: Clips are classified by URL patterns and content (YouTube, GitHub, recipes, articles, etc.), then enriched with transcripts and moved to final locations via para scan, para enrich, and para execute. - Troubleshooting & Filter Reference: Detailed references cover Web Clipper filter syntax, JSON import errors, regex escaping for URLs, and filename formatting pitfalls. - Use Case: You clip a YouTube video, a recipe, and a GitHub repo in one session without choosing anything; later, the pipeline classifies each clip, fetches the video transcript, and files each note into the right vault folder. ## Quick Start Import the capture.json template into Obsidian Web Clipper settings and set it as the default template so all clips land in the 00 Inbox folder.

Frequently Asked Questions about webclipper-templates

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

FAQPage Schema
How do I set up Obsidian Web Clipper with a single capture template?

Import the capture.json file through Obsidian Web Clipper's Templates settings and set it as the default template. All clips then go to the 00 Inbox folder with minimal frontmatter (type, source, clipped date, domain), requiring no decisions at capture time.

How does automatic classification of web clippings work?

Classification runs during review via the para scan command, which detects content type from URL patterns and page content. YouTube, GitHub, Twitter, Reddit, recipes, products, podcasts, and books each map to a type, with a generic fallback for unmatched pages.

Why does my Web Clipper template fail to import with a JSON error?

The most common cause is a plain URL inside a replace filter, where the :// breaks the filter parser. Use regex syntax like replace:"/https:\/\/schema\.org\//" instead, and validate the JSON with jq before importing.

Why do clipped notes have wrong filenames with trailing spaces?

The noteNameFormat is missing the trim filter after safe_name. Page titles often contain trailing whitespace, so use {{title|safe_name|trim}} to produce clean filenames.

Can Web Clipper templates use Dataview syntax from Obsidian notes?

No. Web Clipper uses {{variable}} syntax, not Dataview's `= this.field` inline queries. Convert fields to Web Clipper variables like {{title}} or {{schema:@Article:author.name}} before using note content as a template.