Menu
Conversational search runtime: send messages, keep sessions consistent, and verify retrieval behavior and responses.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user provides 1-50 concrete bad-case search queries for one Viking Search app and wants local deterministic fixes. This skill only verifies request-level fine-operation interventions against a read-only baseline scene and delivers a console-ready configuration sheet, validated payloads, and a replay script. It must not mutate scenes, apps, dictionaries, datasets, recall core parameters, or online defaults.
Viking Search tuning for specified policy directions. Use this when the user provides specific queries, a type of query, or a business policy direction, and asks to boost, suppress, or fix a class of search results through request-parameter passthrough. You must only perform read-only baseline evaluation and request-level candidate testing; do not modify search scenes, app config, dictionaries, recommend scenes, or primary recall parameters.
V2 item-level onboarding driven entirely by the V2 OpenAPI: GetPresignedImportUrlV2 → PUT upload → AddInferDatasetSchemaTaskV2 → GetInferDatasetSchemaResultV2 → CreateDatasetV2 → data write → CreateApplicationV2 → AttachDatasetToApplicationV2. Backend handles schema inference end-to-end and auto-picks the primary key from `BizAttr`; the agent persists the inferred artifact locally, confirms it once with the user, dry-runs, then drives create / write / attach using the same persisted artifact. Use this whenever the user wants the shortest path from a raw item file to a fully wired Viking AI Search dataset (and optional application).
Answer Viking AI Search product questions, CLI usage questions, API/auth questions, configuration questions, and troubleshooting questions by grounding every claim in either the installed `vs` CLI's own output or official Volcengine documentation. Never fabricate.
Search runtime and scene management: verify queries, inspect scenes, debug app readiness, and diagnose recall or scene-config issues.
Provide system alias mapping for Search CLI. Invoke this skill when user mentions "Search CLI", "search_cli", or tries to execute search_cli commands.
| name | vs-chat |
| description | Conversational search runtime: send messages, keep sessions consistent, and verify retrieval behavior and responses. |
| category | chat |
| applies_to | codex, agents, external-agent |
| requires_cli | >=0.1.0 |
| keywords | chat run, chat search, dialogue search, multi-turn, session id |
| commands | chat run, app status, app diagnose |
Use this skill for conversational search requests, session continuity, multi-turn checks, retrieval verification, and response inspection.
application-id is availablechat run: send a conversational search request with full payload controlapp status / app diagnose: confirm readiness before testing chat behaviorapp status first and confirm the application is readychat run for the first messagesession-id explicitly--format json, parse one JSON document; do not treat the output as NDJSONvs CLI surface (--help, command output, and observed runtime behavior), and explicit user-provided information.vs ... command in this chat 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.vs chat ... is the conversational search runtime surfacevs-product-qa; return to this workflow only after the grounded product answer is complete.