vendor-recipe-ingestor

Parse vendor recipe sites lacking LD+JSON markup with custom DOM parsers.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill vendor-recipe-ingestor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vendor-recipe-ingestor
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/vendor-recipe-ingestor
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill vendor-recipe-ingestor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard LD+JSON recipe parsing fails for vendor sites that require custom DOM parsing, branded ingredient enforcement, or bespoke data migration configuration, creating gaps in recipe data ingestion for the Pear Commerce platform.

Core Features & Use Cases

  • Custom DOM Parser Implementation: Build site-specific recipe parsers using stable selectors for recipe headers, hero images, and ingredient sections instead of relying on generic theme wrappers.
  • Branded Ingredient Handling: Preserve vendor branding in ingredient text by appending vendor names to product-linked ingredients that lack explicit branding.
  • Idempotent Migration & Test Coverage: Add non-duplicate VendorRecipeIngestor database configurations and targeted test coverage for custom parser logic to ensure reliable integration.
  • Use Case: For a grocery vendor's recipe site that uses custom HTML markup instead of LD+JSON, use this skill to build a dedicated parser, enforce branded ingredient labels, and add migration and test coverage to integrate it into the Pear recipe ingestion pipeline.

Quick Start

Use the vendor-recipe-ingestor skill to implement a custom DOM parser, branded ingredient customizer, idempotent data migration, and targeted tests for a vendor recipe site that requires bespoke ingestion beyond standard LD+JSON support.

Frequently Asked Questions about vendor-recipe-ingestor

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

FAQPage Schema
How do I parse recipe data from vendor sites that lack standard LD+JSON markup?

To parse recipe data without LD+JSON markup, you can build a custom DOM parser using stable CSS selectors for recipe headers, hero images, and ingredient sections instead of relying on generic theme wrappers.

How do I preserve branded ingredient names when ingesting vendor recipes?

To preserve branded ingredients during recipe ingestion, you can append vendor names to product-linked ingredients that lack explicit branding, ensuring vendor brand preservation within the ingredient text.

How do I add a new vendor recipe ingestor without creating duplicate database configurations?

To add a vendor recipe ingestor without duplicates, you can use idempotent data migration configuration that adds non-duplicate VendorRecipeIngestor database entries for reliable integration.

What is the best way to test custom recipe parsers for grocery vendor sites?

The best way to test custom recipe parsers is to implement focused test validation that targets the custom parser logic, ensuring reliable ingestion and integration for specific grocery vendor sites.

Do I need custom DOM parsing if a vendor site uses standard recipe markup?

If a vendor site uses standard recipe markup, you do not need custom DOM parsing; this approach is specifically for vendor sites that lack standard LD+JSON recipe markup and require bespoke ingestion.

Can I use this recipe ingestion logic outside the Pear Commerce API codebase?

This recipe ingestion logic is scoped to Pear Commerce's api.pearcommerce.com codebase for adding or updating vendor-specific recipe ingestion logic, branded ingredient handling, and data migrations.