Skip to content
Development
Skill

/algo-ecom-search

\"Optimize e-commerce search relevance across the full pipeline from query understanding to result presentation. Use this skill when the user needs to improve search quality, implement query processing features, or diagnose search relevance issues — even if they say 'search

From plugin
awesome-agent-skill
27200 skills4 commands

Claude Code

$ npx -y skills add charlieviettq/awesome-agent-skill --skill algo-ecom-search --agent claude-code

SKILL.md

algo-ecom-search.SKILL.md
name: "\"algo-ecom-search\""
description: "\"Optimize e-commerce search relevance across the full pipeline from query understanding to result presentation. Use this skill when the user needs to improve search quality, implement query processing features, or diagnose search relevance issues — even if they say 'search results are bad', 'improve product search', or 'search relevance optimization'.\"."
allowed-tools: Read, Glob, Grep

E-Commerce Search Relevance

Overview

E-commerce search is a pipeline: query understanding → retrieval → ranking → presentation. Each stage affects relevance. Optimization requires diagnosing WHICH stage fails, not just tuning one component. Zero-result rate, click-through rate, and add-to-cart rate are key metrics.

When to Use

**Trigger conditions:**

  • Diagnosing why search results don't meet user expectations
  • Implementing query processing features (spell check, synonyms, intent detection)
  • Reducing zero-result searches and improving conversion

**When NOT to use:**

  • For ranking algorithm design only (use e-commerce ranking skill)
  • For text relevance scoring only (use BM25)

Algorithm

IRON LAW: Search Quality Is Determined by the WEAKEST Pipeline Stage
Query understanding, retrieval, ranking, and presentation are sequential.
Perfect ranking cannot fix bad retrieval (missing products). Perfect
retrieval cannot fix bad query understanding (wrong intent). Diagnose
which stage fails FIRST before optimizing.

Phase 1: Input Validation

Audit current search: sample 100 queries by volume. For each, evaluate: query understanding (correct intent?), retrieval (relevant products in candidate set?), ranking (best products at top?), presentation (useful display?). **Gate:** Weakness localized to specific pipeline stage(s).

Phase 2: Core Algorithm

**Query understanding:** 1. Spell correction (edit distance, n-gram). 2. Synonym expansion (earbuds↔earphones). 3. Intent classification (product search vs brand search vs category browse). 4. Query rewriting (attribute extraction: "red shoes size 10" → color:red, category:shoes, size:10).

**Retrieval optimization:** 1. Multi-field search (title, description, brand, category, SKU). 2. Boosting strategies (title match > description match). 3. Filter vs boost (hard constraints: category, availability vs soft signals: popularity).

**Result quality:** 1. Zero-result fallback (relax query, suggest alternatives). 2. Faceted navigation (filters by price, brand, rating). 3. Did-you-mean suggestions.

Phase 3: Verification

Measure: zero-result rate (<5% target), CTR on first page (>30% target), NDCG on judged queries. **Gate:** Key metrics improve over baseline.

Phase 4: Output

Return search audit with prioritized improvements.

Output Format

{
  "audit": {"zero_result_rate": 0.08, "avg_ctr": 0.25, "top_failing_queries": ["earbuds wireless", "gift ideas"]},
  "recommendations": [{"stage": "query_understanding", "issue": "no_synonym_expansion", "impact": "high", "fix": "Add earbuds↔earphones synonym"}],
  "metadata": {"queries_sampled": 100, "period": "2025-Q1"}
}

Examples

Sample I/O

**Input:** "wireles earbud" (misspelled) returns 0 results **Expected:** Spell correction → "wireless earbuds" → relevant products displayed. Recommendation: implement spell correction.

Edge Cases

| Input | Expected | Why | |-------|----------|-----| | Category-only query ("shoes") | Browse intent, show popular | Not a specific product search | | Brand misspelling | Fuzzy brand matching | "Nikee" → "Nike" | | Long-tail query ("blue cotton v-neck t-shirt men XL") | Attribute parsing needed | Multiple structured attributes in free text |

Gotchas

  • **Synonym maintenance**: Synonym lists need ongoing curation. "AirPods" is a brand, not a synonym for "earbuds." Wrong synonyms hurt precision.
  • **Over-recall**: Aggressive synonym expansion and fuzzy matching return too many irrelevant results. Balance recall (find everything) with precision (only relevant).
  • **Language-specific challenges**: Chinese search needs word segmentation. "皮鞋" (leather shoes) should not match "拖鞋" (slippers) despite shared "鞋".
  • **Search analytics are essential**: Without tracking query-level CTR, zero-result queries, and conversion rates, you're optimizing blind.
  • **A/B testing search is hard**: Search changes affect all queries. Some improve, some regress. Measure aggregate metrics AND stratify by query type.

References

  • For query understanding pipeline architecture, see `references/query-pipeline.md`
  • For search relevance evaluation methodology, see `references/relevance-evaluation.md`
Read more
@charlieviettq
Ships withawesome-agent-skill

Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).

Stars on GitHub

Momentum

stars in total
27
Star history of charlieviettq/awesome-agent-skill on GitHub, a chart by star-history.com

Other skills on awesome-agent-skill.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills10d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc11d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react1d252k
@facebook@facebookInstall Skill

Questions about algo-ecom-search.

Which coding agents can use algo-ecom-search?
algo-ecom-search installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.