obsidian-clipper-template-creator

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.

3.5KStar
806Fork
更新于 1/26/2026
SKILL.md
readonly只读
name
obsidian-clipper-template-creator
description

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.

Obsidian Web Clipper Template Creator

This skill helps you create importable JSON templates for the Obsidian Web Clipper.

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 (REQUIRED): Use WebFetch or 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.
  4. Draft the JSON: Create a valid JSON object following the schema.
  5. 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

Official Documentation

Examples

See assets/ for JSON examples.

You Might Also Like

Related Skills

verify

verify

243K

Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

facebook avatarfacebook
获取
test

test

243K

Use when you need to run tests for React core. Supports source, www, stable, and experimental channels.

facebook avatarfacebook
获取

Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.

facebook avatarfacebook
获取

Use when adding new error messages to React, or seeing "unknown error code" warnings.

facebook avatarfacebook
获取
flow

flow

243K

Use when you need to run Flow type checking, or when seeing Flow type errors in React code.

facebook avatarfacebook
获取
flags

flags

243K

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

facebook avatarfacebook
获取