Search teams need reliable guidance across indexing, ranking, semantic retrieval, and evaluation. This skill provides practical workflows and examples for building and improving search systems.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "search-engineer" from https://skillstore.io/skills/zl2023github-search-engineer.md and its manifest at https://skillstore.io/api/skills/zl2023github-search-engineer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "search-engineer". Recommend a search architecture for two million Chinese product records with filters and semantic queries.
Expected outcome:
Use Elasticsearch for structured filters and lexical recall, plus a vector field for semantic retrieval. Evaluate hybrid ranking with NDCG and conversion metrics.
Using "search-engineer". Our zero-result rate increased after changing the analyzer.
Expected outcome:
Compare token output before and after the analyzer change.
Segment affected queries by language, category, and frequency.
Restore recall with synonyms or analyzer adjustments, then run an A/B test.
Using "search-engineer". Plan evaluation for a new RAG retriever.
Expected outcome:
Build a judged query set, measure recall at several depths, evaluate reranking with NDCG, and track answer faithfulness against retrieved evidence.
The 25 external-command findings are false positives caused by Markdown code fences; the document does not use Ruby or shell backtick execution. The pinned third-party plugin installation is a genuine low-severity network and supply-chain risk because no checksum or signature verification is provided.
1
Files scanned
310
Lines analyzed
1
Review items
0
False positives ignored
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Line 88 directs the plugin installer to download a third-party release archive from GitHub. The version is pinned, but the example provides no checksum or signature verification.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
zl2023github. (2026). search-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-search-engineer/audits/4
BibTeX citation
@techreport{zl2023github-zl2023github-search-engineer-2026,
author = {zl2023github},
title = {search-engineer security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-search-engineer/audits/4},
note = {Author version unspecified}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "search-engineer security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "zl2023github"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/zl2023github-search-engineer/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-search-engineer:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance
What You Can Build
Plan a Search Platform
Compare keyword, vector, and hybrid designs, then define mappings, shards, analyzers, and evaluation criteria.
Build a RAG Retriever
Select embeddings, chunk documents, configure vector retrieval, and define relevance measurements for a RAG pipeline.
Diagnose Search Quality
Review zero-result queries, clicks, latency, and A/B metrics to identify practical ranking improvements.
Try These Prompts
Choose a Search Engine
Compare Elasticsearch, Solr, and Milvus for my dataset, query patterns, scale, latency target, and language requirements. Recommend one architecture with reasons.
Design an Index
Design an Elasticsearch index for these fields: [fields]. Include mappings, analyzers, shard assumptions, filters, sorting, and a relevance evaluation plan.
Investigate Relevance Problems
Analyze these search metrics and bad cases: [data]. Classify recall, ranking, tokenization, and latency issues. Propose prioritized experiments with success metrics.
Architect Hybrid RAG Retrieval
Create a production design for hybrid RAG retrieval using [data source]. Specify chunking, embeddings, lexical recall, vector recall, reranking, caching, and evaluation.
Best Practices
Define representative queries and relevance judgments before tuning retrieval.
Validate changes offline, then use controlled experiments with business and quality metrics.
Pin dependencies, secure production services, and verify third-party artifacts before installation.
Avoid
Do not select an engine before documenting data, query, scale, and latency requirements.
Do not optimize only click-through rate without relevance and conversion safeguards.
Do not copy example commands into production without authentication, backups, and environment review.
Frequently Asked Questions
Does this skill install or run a search engine?
No. It provides guidance and examples. Users must review and execute commands in their own environment.
Which search technologies are covered?
The examples cover Elasticsearch, Milvus, Redis, sentence transformers, Chroma, and related Python analysis libraries.
Can it help with Chinese search?
Yes. It discusses Chinese analyzers, custom dictionaries, query normalization, synonyms, and Chinese embedding models.
Does it support semantic search and RAG?
Yes. It outlines embeddings, vector indexes, chunking, retrieval, reranking considerations, and evaluation.
How does it evaluate search quality?
It covers NDCG, MAP, click metrics, zero-result rate, latency, and statistical A/B comparison.
Is the example code production ready?
No. Add error handling, security, observability, dependency pinning, tests, and environment-specific configuration before production use.