Obsidian Clipper Template Creator

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 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.
   • 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.
   • See 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.
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.

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 and the official Logic docs so the template passes validation.

{
  "schemaVersion": "0.1.0",
  "name": "My Template",
  ...
}

Resources

• references/variables.md - Available data variables.
• references/filters.md - Formatting filters.
• references/json-schema.md - JSON structure documentation.
• references/logic.md - Template logic.
• references/bases-workflow.md - How to map Bases to Templates.
• references/analysis-workflow.md - How to validate page data.

Official Documentation

• Variables
• Filters
• Logic
• Templates

Examples

See assets/ for JSON examples.

AGI Framework Integration

Adapted for @techwavedev/agi-agent-kit Original source: antigravity-awesome-skills

Memory-First Protocol

Retrieve prior documentation structure and content to maintain consistency. Cache generated docs to avoid regenerating unchanged sections.

# Check for prior documentation context before starting
python3 execution/memory_manager.py auto --query "documentation patterns and prior content for Obsidian Clipper Template Creator"

Storing Results

After completing work, store documentation decisions for future sessions:

python3 execution/memory_manager.py store \
  --content "Documentation: API reference generated from OpenAPI spec, deployment guide updated with new env vars" \
  --type technical --project <project> \
  --tags obsidian-clipper-template-creator documentation

Multi-Agent Collaboration

Share documentation changes with all agents so they reference the latest guides and APIs.

python3 execution/cross_agent_context.py store \
  --agent "<your-agent>" \
  --action "Documentation updated — API reference, deployment guide, and CHANGELOG all current" \
  --project <project>

Agent Team: Documentation

This skill pairs with documentation_team — dispatched automatically after any code change to keep docs in sync.