القائمة
Search runtime and scene management: verify queries, inspect scenes, debug app readiness, and diagnose recall or scene-config issues.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/volcengine/SearchCLI --skill vs-searchيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | vs-search |
| description | Search runtime and scene management: verify queries, inspect scenes, debug app readiness, and diagnose recall or scene-config issues. |
| category | search |
| applies_to | codex, agents, external-agent |
| requires_cli | >=0.1.0 |
| keywords | search debug, search run, query run, search scene, search diagnosis, recall issue, online strategy, boost bury, rerank, synonym, diversity, serving controls, fine-grained operations, query-specific rules |
| commands | search run, search scene create, search scene list, search scene get, search scene update, app status, app diagnose |
Use this skill for:
If the user wants automated batch evaluation or similarity tuning across many queries and strategies, use vs-search-tuning instead.
application-id is availablescene-idBefore changing anything, decide whether the user wants:
This skill stays at the search workflow level. Do not embed low-level API field mappings, payload design, or enum interpretation here. When a concrete command needs exact parameters, first consult vs-product-qa.
search run: send a production-style search requestsearch scene create / search scene list / search scene get: manage search scenessearch scene update: update scene configurationapp status / app diagnose: inspect readiness before blaming the querysearch scene list/get first and inspect the current scene before mutating it.vs-product-qa to confirm the current command behavior and the exact parameter requirements.search run for verification requests and search scene update for persistent scene changes.search scene get and verify that the intended change is visible online.app status and then app diagnose.--help, trust the installed CLI behavior first, and only then inspect repository code when needed to explain or fix the gap.references/search-scene-natural-language-routing.md: workflow-oriented mapping from natural-language search-scene requests to the first config area or workflow you should inspectvs CLI surface (--help, command output, and observed runtime behavior), and explicit user-provided information.vs ... command in this search workflow, first consult vs-product-qa to verify the current command surface, required flags, payload fields, input format, and allowed values. Only after that check may you finalize parameters and run the command.ShuffleConfig.Rules[].FieldName, ShuffleExpr.field, BoostBuryCondConfig.Rules[].Config.field, FilterConfig.Config.field, AuxiliaryPools[].Filter.field, etc.) are case-sensitive. Never infer or normalize field name casing from the user's natural-language description. Before writing any field name into a config, first look up the exact field name from the dataset schema or data-config via dataset get --id <dataset-id> --full or app dataset-config get --application-id <id> --dataset-id <id> --full, and copy the field name exactly as it appears there (case-for-case). If the field name you have doesn't match any field in the schema, stop and ask the user to confirm which field they mean instead of guessing.dataset-idvs search ... commands over bypassing the CLI and calling lower-level APIs directlysearch scene update for persistent search behavior and do not invent low-level API mappings inside this skillreferences/search-scene-natural-language-routing.md as the routing layer; if the target is a rule-resource workflow such as filter-item-scope, do not reduce it to a single inline scene field edit--help, skill text, and the installed command implementation are perfectly aligned; verify the actual command behavior before making high-risk scene changesvs-product-qa; return to this workflow only after the grounded product answer is complete.