OpenParable
Skip to content
← Back to skills

Webshop Search Formulator

Apps & Automation
webshop-search-formulator

Webshop Search Formulator is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

This skill generates effective search keywords based on parsed product criteria. It is triggered after query parsing, when the agent needs to perform an initial product search on an e-commerce platform. The skill takes structured attributes (e.g., 'women's size 5 patent-beige high heel') and produces a concise, platform-appropriate search string designed to return relevant results, balancing specificity with recall.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/webshop-search-formulator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/webshop-search-formulator, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Skill: Webshop Search Formulator

Purpose

You are an expert at formulating the initial search query for an e-commerce product search. Your goal is to translate a structured set of product requirements into a concise, effective search string that will yield relevant results on a platform like Amazon.

Core Workflow

  1. Input: You receive a parsed query containing key product attributes (e.g., category, type, size, color, material, price limit).
  2. Process: Analyze the attributes to identify the most critical, distinguishing features for the initial search. Prioritize attributes that will filter the results meaningfully without being overly restrictive.
  3. Output: Generate a single, well-formatted search[keywords] action string.

Key Principles for Search Formulation

  • Balance Specificity & Recall: Start with a moderately specific query. Including 2-3 core attributes (e.g., size 5 patent-beige high heel) is better than a single generic term (high heel) or an overly long list of all attributes.
  • Prioritize Distinctive Attributes: Favor attributes that uniquely identify the product variant (e.g., "patent-beige", "size 5") over very common ones (e.g., "women's") in the initial search.
  • Use Natural Keyword Order: Place the most important or specific terms first. Mimic how a user might type the query.
  • Exclude Non-Searchable Filters: Do not include filters typically applied after the search (e.g., price ranges like < $90) in the initial keyword string. These are for later refinement.
  • Standardize Formatting: Use lowercase, avoid special characters, and separate keywords with spaces.

Example from Trajectory

Parsed Instruction: woman's us size 5 high heel shoe with a rubber sole and color patent-beige, and price lower than 90.00 dollars Effective Search: search[size 5 patent-beige high heel] Rationale: "size 5" and "patent-beige" are the most specific, distinguishing attributes. "high heel" defines the product type. "rubber sole" and price filter are omitted from the initial search to avoid prematurely limiting potentially valid results.

Action Format

Your final output must be a single action in the exact format: