feat: Update obsidian-clipper-template-creator skill (#226)

* chore: sync generated registry files [ci skip]

* Update skill to support clipper 1.0.0 features

* chore: sync generated registry files [ci skip]

* Update skill frontmatter

* chore: sync generated registry files [ci skip]

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

README.md

@@ -1,4 +1,4 @@
-<!-- registry-sync: version=7.0.1; skills=1206; stars=20847; updated_at=2026-03-06T15:02:32+00:00 -->
+<!-- registry-sync: version=7.0.1; skills=1206; stars=21178; updated_at=2026-03-07T08:34:18+00:00 -->
 # 🌌 Antigravity Awesome Skills: 1,206+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
 
 > **The Ultimate Collection of 1,206+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode, AdaL**

skills/obsidian-clipper-template-creator/SKILL.md

@@ -1,7 +1,7 @@
 ---
 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."
-risk: unknown
+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.
+risk: safe
 source: community
 date_added: "2026-02-27"
 ---
@@ -13,19 +13,20 @@ This skill helps you create importable JSON templates for the Obsidian Web Clipp
 ## 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`).
+2. **Check Existing Bases:** The user likely has a "Base" schema defined in `Bases/`.
+    - **Action:** Read `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](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 (REQUIRED):** Use **WebFetch** to retrieve page content; if WebFetch is not available, use a browser DOM snapshot. See [references/analysis-workflow.md](references/analysis-workflow.md).
     - **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](references/analysis-workflow.md) for analysis techniques.
 4. **Draft the JSON:** Create a valid JSON object following the schema.
     - See [references/json-schema.md](references/json-schema.md).
-5. **Verify Variables:** Ensure the chosen variables (Preset, Schema, Selector) exist in your analysis.
+5. **Consider template logic:** Use conditionals for optional blocks (e.g. show nutrition only if present), loops for list data, variable assignment to avoid repeating expressions, and fallbacks for missing variables. Use logic only when it improves the template; keep simple templates simple. See [references/logic.md](references/logic.md).
+6. **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](references/variables.md).
 
@@ -40,6 +41,9 @@ This skill helps you create importable JSON templates for the Obsidian Web Clipp
 
 **ALWAYS** output the final result as a JSON code block that the user can copy and import.
 
+The Clipper template editor validates template syntax.
+If you use template logic (conditionals, loops, variable assignment), ensure it follows the syntax in [references/logic.md](references/logic.md) and the official [Logic](https://help.obsidian.md/web-clipper/logic) docs so the template passes validation.
+
 ```json
 {
   "schemaVersion": "0.1.0",
@@ -53,6 +57,7 @@ This skill helps you create importable JSON templates for the Obsidian Web Clipp
 - [references/variables.md](references/variables.md) - Available data variables.
 - [references/filters.md](references/filters.md) - Formatting filters.
 - [references/json-schema.md](references/json-schema.md) - JSON structure documentation.
+- [references/logic.md](references/logic.md) - Template logic.
 - [references/bases-workflow.md](references/bases-workflow.md) - How to map Bases to Templates.
 - [references/analysis-workflow.md](references/analysis-workflow.md) - How to validate page data.
 
@@ -60,11 +65,9 @@ This skill helps you create importable JSON templates for the Obsidian Web Clipp
 
 - [Variables](https://help.obsidian.md/web-clipper/variables)
 - [Filters](https://help.obsidian.md/web-clipper/filters)
+- [Logic](https://help.obsidian.md/web-clipper/logic)
 - [Templates](https://help.obsidian.md/web-clipper/templates)
 
 ## Examples
 
 See [assets/](assets/) for JSON examples.
-
-## When to Use
-This skill is applicable to execute the workflow or actions described in the overview.

skills/obsidian-clipper-template-creator/references/analysis-workflow.md

@@ -74,6 +74,6 @@ Selectors must be verified against the fetched HTML or DOM snapshot. Do not gues
 
 ## 3. Verify Against Base
 
-Compare the available data from your analysis with the properties required by the user's Base (see `references/bases-workflow.md`).
+Compare the available data from your analysis with the properties required by the user's Base (see [bases-workflow.md](bases-workflow.md)).
 
 - If the Base requires `ingredients` but the page has no Schema or clear list structure, warn the user that this field might need manual entry or a prompt variable.

skills/obsidian-clipper-template-creator/references/bases-workflow.md

@@ -1,13 +1,13 @@
 # Working with Obsidian Bases
 
-The user maintains "Bases" in `Templates/Bases/*.base` which define the schema and properties for different types of notes (e.g., Recipes, Clippings, People).
+The user maintains "Bases" in `Bases/*.base` which define the schema and properties for different types of notes (e.g., Recipes, Clippings, People).
 
 ## Workflow
 
 1.  **Identify the Category:** Determine the type of content the user wants to clip (e.g., a Recipe, a News Article, a YouTube video).
-2.  **Find the Base:** Search `Templates/Bases/` for a matching `.base` file.
-    *   Example: For a recipe, look for `Templates/Bases/Recipes.base`.
-    *   Example: For a generic article, look for `Templates/Bases/Clippings.base`.
+2.  **Find the Base:** Search `Bases/` for a matching `.base` file.
+    *   Example: For a recipe, look for `Bases/Recipes.base`.
+    *   Example: For a generic article, look for `Bases/Clippings.base`.
 3.  **Read the Base:** Read the content of the `.base` file to understand the required properties.
 
 ## Interpreting .base Files

skills/obsidian-clipper-template-creator/references/json-schema.md

@@ -28,6 +28,7 @@ The Obsidian Web Clipper imports templates via JSON files.
 *   **`noteContentFormat`**: The body of the note.
     *   Use `\n` for newlines.
     *   Can use all variables (e.g., `{{content}}`, `{{selection}}`).
+    *   Supports **template logic** (conditionals, loops, variable assignment) as documented in [logic.md](logic.md).
 *   **`noteNameFormat`**: The filename pattern (e.g., `{{date}} - {{title}}`).
 *   **`path`**: The location to save the note.
     *   For `create` behavior: The *folder* to save the note in (e.g., `Clippings/` or `Recipes/`).
@@ -67,5 +68,10 @@ The `properties` array defines the YAML frontmatter of the note.
 ### Property Object Structure
 
 *   **`name`**: The key in the YAML frontmatter.
-*   **`value`**: The value to populate. Can contain variables.
+*   **`value`**: The value to populate. Can contain variables and the same **template logic** (conditionals, loops, variable assignment) as `noteContentFormat`; see [logic.md](logic.md).
 *   **`type`**: One of the types listed above.
+
+## Template validation
+
+The Clipper template editor checks template syntax. 
+Invalid logic in `noteContentFormat` or property `value` fields will be reported in the editor; use valid syntax as described in the [Logic](https://help.obsidian.md/web-clipper/logic) documentation.

skills/obsidian-clipper-template-creator/references/logic.md

@@ -0,0 +1,67 @@
+# Obsidian Web Clipper Template Logic
+
+**Official docs:** [Logic - Obsidian Help](https://help.obsidian.md/web-clipper/logic)
+
+As of **Obsidian Web Clipper 1.0.0**, templates support logic in `noteContentFormat` and in property `value` fields: conditionals, loops, variable assignment, and fallbacks. This page describes how each works. For authoritative syntax and delimiters, use the official documentation link above.
+
+---
+
+## When to use logic
+
+- **Conditionals:** Show optional sections only when data exists (e.g. nutrition block only if `{{schema:Recipe:nutrition}}` is present).
+- **Variable assignment:** Assign a value once and reuse it in the template to avoid repeating long expressions.
+- **Fallbacks:** Provide a default when a variable is empty so the note still looks correct.
+- **Loops:** Iterate over arrays (ingredients, steps, tags) to format each item; combine with filters for list/table output.
+
+Keep simple templates simple; add logic only when it improves the result or avoids broken output for missing data.
+
+---
+
+## Conditionals
+
+Conditionals include or exclude blocks based on whether a value exists or meets a condition.
+
+- **Comparison operators:** Compare two values (e.g. equals, not equals, greater than, less than). Exact operators are defined in the official Logic page.
+- **Logical operators:** Combine or negate conditions (e.g. and, or, not; or symbol forms like `&&`, `||`, `!`). Use these to build compound conditions.
+- **Truthiness:** Values are evaluated in a JavaScript-like way for conditions. Empty strings, empty arrays, and missing variables are typically falsy; non-empty values are truthy. See the official docs for the full rules.
+- **Typical use:** Wrap optional sections (e.g. author, nutrition, image) in a conditional so they only render when the variable has a value.
+
+---
+
+## Assign a variable
+
+You can assign a variable once and reuse it in the same template. Use this to avoid repeating long variable or filter chains (e.g. the same schema path or selector used in multiple places). The assigned variable is available for the rest of the template in that scope. Exact syntax (e.g. assignment block format and scope) is in the official Logic documentation.
+
+---
+
+## Fallbacks
+
+Fallbacks supply a default when a variable is empty.
+
+- **Default when missing:** Provide a fallback value so the template still produces readable output when the primary variable is empty.
+- **Chaining fallbacks:** You can chain multiple fallbacks (e.g. try variable A, then B, then a literal default). The first non-empty value is used.
+- **With filters:** Fallbacks can be used together with filters. The evaluation order (variable → fallback → filter, or other) is defined in the official docs under "With filters" and "Evaluation order."
+
+---
+
+## Loops
+
+Loops iterate over array values (e.g. ingredients, instructions, tags).
+
+- **Loop sources:** The array to iterate over—typically a variable that returns a list (e.g. `{{schema:Recipe:recipeIngredient}}`, `{{schema:Recipe:recipeInstructions}}`).
+- **Loop variables:** Inside the loop you get a variable for the current item; you may also get an index or other loop metadata. Names and behavior are described in the official "Loop variables" and "Accessing array items by index" sections.
+- **Accessing array items by index:** When you need the nth item of an array outside a loop, or need the current index inside a loop, the syntax is defined in the official documentation.
+- **Nested loops:** Loops can be nested when you have arrays of structured data (e.g. steps each with sub-steps).
+- **Combine logic:** Loops and conditionals can be combined (e.g. loop over items and show a subsection only when a field exists, or conditionally include a loop).
+
+---
+
+## Evaluation order and combining logic
+
+The order in which variables, filters, fallbacks, conditionals, and loops are evaluated is defined in the official documentation. When you combine logic (e.g. conditionals inside loops, or variables used in both conditionals and output), follow the official "Evaluation order" and "Combine logic" sections so behavior matches expectations.
+
+---
+
+## Template validation
+
+The Obsidian Web Clipper template editor **validates template syntax**. Invalid logic (e.g. malformed conditionals or loops) will be reported in the editor. When generating templates, use only logic constructs and syntax described on the official Logic page so that the template passes validation.

skills/obsidian-clipper-template-creator/references/variables.md

@@ -57,3 +57,8 @@ Examples:
 - `{{schema:Recipe:recipeIngredient}}`
 - `{{schema:author.name}}`
 - `{{schema:Article:headline}}`
+
+## Fallbacks
+When a variable is empty, you can supply a default value (fallback). 
+Fallbacks can be chained (try variable A, then B, then a literal default) and used with filters. 
+For syntax and evaluation order, see [logic.md](logic.md).

skills_index.json

@@ -7925,7 +7925,7 @@
     "category": "uncategorized",
     "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.",
-    "risk": "unknown",
+    "risk": "safe",
     "source": "community",
     "date_added": "2026-02-27"
   },