@jakkrichm/create-nexus-devflow 2.0.0 → 2.0.1

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

@@ -1,73 +1,73 @@
----
-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: safe
-source: community
-date_added: "2026-02-27"
----
-
-# 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 `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** 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. **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).
-
-## 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.
-
-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",
-  "name": "My Template",
-  ...
-}
-```
-
-## Resources
-
-- [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.
-
-### Official Documentation
-
-- [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.
+---
+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: safe
+source: community
+date_added: "2026-02-27"
+---
+
+# 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 `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** 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. **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).
+
+## 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.
+
+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",
+  "name": "My Template",
+  ...
+}
+```
+
+## Resources
+
+- [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.
+
+### Official Documentation
+
+- [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.

package/template/.agents/skills/obsidian-clipper-template-creator/assets/clipping-template.json

@@ -1,51 +1,51 @@
-{
-	"schemaVersion": "0.1.0",
-	"name": "General Clipping",
-	"behavior": "create",
-	"noteContentFormat": "{{content}}",
-	"properties": [
-		{
-			"name": "categories",
-			"value": "[[Clippings]]",
-			"type": "multitext"
-		},
-		{
-			"name": "author",
-			"value": "[[{{author}}]]",
-			"type": "multitext"
-		},
-		{
-			"name": "source",
-			"value": "{{url}}",
-			"type": "text"
-		},
-		{
-			"name": "via",
-			"value": "",
-			"type": "text"
-		},
-		{
-			"name": "published",
-			"value": "{{published}}",
-			"type": "datetime"
-		},
-		{
-			"name": "created",
-			"value": "{{date}}",
-			"type": "datetime"
-		},
-		{
-			"name": "topics",
-			"value": "",
-			"type": "multitext"
-		},
-		{
-			"name": "description",
-			"value": "{{description}}",
-			"type": "text"
-		}
-	],
-	"triggers": [],
-	"noteNameFormat": "{{title}}",
-	"path": "Clippings/"
-}
+{
+	"schemaVersion": "0.1.0",
+	"name": "General Clipping",
+	"behavior": "create",
+	"noteContentFormat": "{{content}}",
+	"properties": [
+		{
+			"name": "categories",
+			"value": "[[Clippings]]",
+			"type": "multitext"
+		},
+		{
+			"name": "author",
+			"value": "[[{{author}}]]",
+			"type": "multitext"
+		},
+		{
+			"name": "source",
+			"value": "{{url}}",
+			"type": "text"
+		},
+		{
+			"name": "via",
+			"value": "",
+			"type": "text"
+		},
+		{
+			"name": "published",
+			"value": "{{published}}",
+			"type": "datetime"
+		},
+		{
+			"name": "created",
+			"value": "{{date}}",
+			"type": "datetime"
+		},
+		{
+			"name": "topics",
+			"value": "",
+			"type": "multitext"
+		},
+		{
+			"name": "description",
+			"value": "{{description}}",
+			"type": "text"
+		}
+	],
+	"triggers": [],
+	"noteNameFormat": "{{title}}",
+	"path": "Clippings/"
+}

package/template/.agents/skills/obsidian-clipper-template-creator/assets/recipe-template.json

@@ -1,48 +1,48 @@
-{
-	"schemaVersion": "0.1.0",
-	"name": "Recipe",
-	"behavior": "create",
-	"noteContentFormat": "![{{schema:Recipe:image|first}}]\n\n## Description\n{{schema:Recipe:description}}\n\n## Ingredients\n{{schema:Recipe:recipeIngredient|list}}\n\n## Instructions\n{{schema:Recipe:recipeInstructions|map:step =>> step.text|list}}\n\n## Nutrition\n- Calories: {{schema:Recipe:nutrition.calories}}",
-	"properties": [
-		{
-			"name": "categories",
-			"value": "[[Recipes]]",
-			"type": "multitext"
-		},
-		{
-			"name": "author",
-			"value": "[[{{schema:Recipe:author.name}}]]",
-			"type": "text"
-		},
-		{
-			"name": "source",
-			"value": "{{url}}",
-			"type": "text"
-		},
-		{
-			"name": "ingredients",
-			"value": "{{schema:Recipe:recipeIngredient}}",
-			"type": "multitext"
-		},
-		{
-			"name": "cuisine",
-			"value": "{{schema:Recipe:recipeCuisine}}",
-			"type": "text"
-		},
-		{
-			"name": "rating",
-			"value": "",
-			"type": "number"
-		},
-		{
-			"name": "type",
-			"value": "Recipe",
-			"type": "text"
-		}
-	],
-	"triggers": [
-		"schema:Recipe"
-	],
-	"noteNameFormat": "{{schema:Recipe:name}}",
-	"path": "Recipes/"
-}
+{
+	"schemaVersion": "0.1.0",
+	"name": "Recipe",
+	"behavior": "create",
+	"noteContentFormat": "![{{schema:Recipe:image|first}}]\n\n## Description\n{{schema:Recipe:description}}\n\n## Ingredients\n{{schema:Recipe:recipeIngredient|list}}\n\n## Instructions\n{{schema:Recipe:recipeInstructions|map:step =>> step.text|list}}\n\n## Nutrition\n- Calories: {{schema:Recipe:nutrition.calories}}",
+	"properties": [
+		{
+			"name": "categories",
+			"value": "[[Recipes]]",
+			"type": "multitext"
+		},
+		{
+			"name": "author",
+			"value": "[[{{schema:Recipe:author.name}}]]",
+			"type": "text"
+		},
+		{
+			"name": "source",
+			"value": "{{url}}",
+			"type": "text"
+		},
+		{
+			"name": "ingredients",
+			"value": "{{schema:Recipe:recipeIngredient}}",
+			"type": "multitext"
+		},
+		{
+			"name": "cuisine",
+			"value": "{{schema:Recipe:recipeCuisine}}",
+			"type": "text"
+		},
+		{
+			"name": "rating",
+			"value": "",
+			"type": "number"
+		},
+		{
+			"name": "type",
+			"value": "Recipe",
+			"type": "text"
+		}
+	],
+	"triggers": [
+		"schema:Recipe"
+	],
+	"noteNameFormat": "{{schema:Recipe:name}}",
+	"path": "Recipes/"
+}

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

@@ -1,79 +1,79 @@
-# Analysis Workflow: Validating Variables
-
-To ensure your template works correctly, you must validate that the target page actually contains the data you want to extract.
-
-## 1. Fetch the Page
-
-Use the `WebFetch` tool or a browser DOM snapshot to retrieve the content of a representative URL provided by the user.
-
-```text
-WebFetch(url="https://example.com/recipe/chocolate-cake")
-```
-
-## 2. Analyze the Output
-
-### Check for Schema.org (Recommended)
-
-Look for `<script type="application/ld+json">`. This contains structured data which is the most reliable way to extract info.
-
-**Example Found in HTML:**
-
-```html
-<script type="application/ld+json">
-{
-  "@context": "https://schema.org/",
-  "@type": "Recipe",
-  "name": "Chocolate Cake",
-  "author": {
-    "@type": "Person",
-    "name": "John Doe"
-  }
-}
-```
-
-**Conclusion:**
-
-- `{{schema:Recipe:name}}` is valid.
-- `{{schema:Recipe:author.name}}` is valid.
-- **Tip:** You can use `schema:Recipe` in the `triggers` array to automatically select this template for any page with this schema.
-
-### Check for Meta Tags
-
-Look for `<meta>` tags in the `<head>` section.
-
-**Example Found in HTML:**
-
-```html
-<meta property="og:title" content="The Best Chocolate Cake" />
-<meta name="description" content="A rich, moist chocolate cake recipe." />
-```
-
-**Conclusion:**
-
-- `{{meta:og:title}}` is valid.
-- `{{meta:description}}` is valid.
-
-### Check for CSS Selectors (Verified)
-
-If Schema and Meta tags are missing, look for HTML structure (classes and IDs) to use with `{{selector:...}}`.
-Selectors must be verified against the fetched HTML or DOM snapshot. Do not guess selectors.
-
-**Example Found in HTML:**
-
-```html
-<div class="article-body">
-  <h1 id="main-title">Chocolate Cake</h1>
-  <span class="author-name">By John Doe</span>
-</div>
-```
-
-**Conclusion:**
-
-- `{{selector:h1#main-title}}` or `{{selector:h1}}` can extract the title.
-- `{{selector:.author-name}}` can extract the author.
-
-## 3. Verify Against Base
-
-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.
+# Analysis Workflow: Validating Variables
+
+To ensure your template works correctly, you must validate that the target page actually contains the data you want to extract.
+
+## 1. Fetch the Page
+
+Use the `WebFetch` tool or a browser DOM snapshot to retrieve the content of a representative URL provided by the user.
+
+```text
+WebFetch(url="https://example.com/recipe/chocolate-cake")
+```
+
+## 2. Analyze the Output
+
+### Check for Schema.org (Recommended)
+
+Look for `<script type="application/ld+json">`. This contains structured data which is the most reliable way to extract info.
+
+**Example Found in HTML:**
+
+```html
+<script type="application/ld+json">
+{
+  "@context": "https://schema.org/",
+  "@type": "Recipe",
+  "name": "Chocolate Cake",
+  "author": {
+    "@type": "Person",
+    "name": "John Doe"
+  }
+}
+```
+
+**Conclusion:**
+
+- `{{schema:Recipe:name}}` is valid.
+- `{{schema:Recipe:author.name}}` is valid.
+- **Tip:** You can use `schema:Recipe` in the `triggers` array to automatically select this template for any page with this schema.
+
+### Check for Meta Tags
+
+Look for `<meta>` tags in the `<head>` section.
+
+**Example Found in HTML:**
+
+```html
+<meta property="og:title" content="The Best Chocolate Cake" />
+<meta name="description" content="A rich, moist chocolate cake recipe." />
+```
+
+**Conclusion:**
+
+- `{{meta:og:title}}` is valid.
+- `{{meta:description}}` is valid.
+
+### Check for CSS Selectors (Verified)
+
+If Schema and Meta tags are missing, look for HTML structure (classes and IDs) to use with `{{selector:...}}`.
+Selectors must be verified against the fetched HTML or DOM snapshot. Do not guess selectors.
+
+**Example Found in HTML:**
+
+```html
+<div class="article-body">
+  <h1 id="main-title">Chocolate Cake</h1>
+  <span class="author-name">By John Doe</span>
+</div>
+```
+
+**Conclusion:**
+
+- `{{selector:h1#main-title}}` or `{{selector:h1}}` can extract the title.
+- `{{selector:.author-name}}` can extract the author.
+
+## 3. Verify Against Base
+
+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.

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

@@ -1,44 +1,44 @@
-# Working with Obsidian Bases
-
-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 `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
-
-Base files use a YAML-like structure. Look for the `properties` section.
-
-```yaml
-properties:
-  file.name:
-    displayName: name
-  note.author:
-    displayName: author
-  note.type:
-    displayName: type
-  note.ingredients:
-    displayName: ingredients
-```
-
-*   `note.X` corresponds to a property name `X` in the frontmatter.
-*   `displayName` helps understand the intent, but the property key (e.g., `author`, `type`, `ingredients`) is what matters for the template.
-
-## Mapping to Clipper Properties
-
-When creating the JSON for the Web Clipper, map the Base properties to the `properties` array in the JSON.
-
-| Base Property | Clipper JSON Property Name | Value Strategy |
-| :--- | :--- | :--- |
-| `note.author` | `author` | `{{author}}` or `{{schema:author.name}}` |
-| `note.source` | `source` | `{{url}}` |
-| `note.published` | `published` | `{{published}}` |
-| `note.ingredients` | `ingredients` | `{{schema:Recipe:recipeIngredient}}` |
-| `note.type` | `type` | Constant (e.g., `Recipe`) or empty |
-
-**Crucial Step:** Ask the user which properties should be automatically filled, which should be hardcoded (e.g., `type: Recipe`), and which should be left empty for manual entry.
+# Working with Obsidian Bases
+
+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 `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
+
+Base files use a YAML-like structure. Look for the `properties` section.
+
+```yaml
+properties:
+  file.name:
+    displayName: name
+  note.author:
+    displayName: author
+  note.type:
+    displayName: type
+  note.ingredients:
+    displayName: ingredients
+```
+
+*   `note.X` corresponds to a property name `X` in the frontmatter.
+*   `displayName` helps understand the intent, but the property key (e.g., `author`, `type`, `ingredients`) is what matters for the template.
+
+## Mapping to Clipper Properties
+
+When creating the JSON for the Web Clipper, map the Base properties to the `properties` array in the JSON.
+
+| Base Property | Clipper JSON Property Name | Value Strategy |
+| :--- | :--- | :--- |
+| `note.author` | `author` | `{{author}}` or `{{schema:author.name}}` |
+| `note.source` | `source` | `{{url}}` |
+| `note.published` | `published` | `{{published}}` |
+| `note.ingredients` | `ingredients` | `{{schema:Recipe:recipeIngredient}}` |
+| `note.type` | `type` | Constant (e.g., `Recipe`) or empty |
+
+**Crucial Step:** Ask the user which properties should be automatically filled, which should be hardcoded (e.g., `type: Recipe`), and which should be left empty for manual entry.