
Vs Chat
- 3 installs
- 1.2k repo stars
- Updated July 31, 2026
- volcengine/searchcli
Runs conversational search against a Viking application, keeping session continuity across turns and verifying retrieval behavior and responses.
About
Sends multi-turn conversational search requests to a Viking AI Search application and keeps sessions consistent. A developer uses it to run dialogue search, maintain session continuity, and inspect retrieval and responses.
- chat run sends conversational search with full payload control
- Checks app status and diagnose to confirm readiness before testing
Vs Chat by the numbers
- 3 all-time installs (skills.sh)
- +1 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #435 of 550 CLI & Terminal skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/volcengine/searchcli --skill vs-chatAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 3 |
|---|---|
| repo stars | ★ 1.2k |
| Last updated | July 31, 2026 |
| Repository | volcengine/searchcli ↗ |
What it does
Runs conversational search against a Viking application, keeping session continuity across turns and verifying retrieval behavior and responses.
Files
Viking Chat
When to Use
Use this skill for conversational search requests, session continuity, multi-turn checks, retrieval verification, and response inspection.
Preconditions
- an
application-idis available - the application is preferably already ready
Commands
chat run: send a conversational search request with full payload controlapp status/app diagnose: confirm readiness before testing chat behavior
Workflow
1. Check app status first and confirm the application is ready 2. Use chat run for the first message 3. If you need multi-turn behavior, pass session-id explicitly 4. Use the full request payload when you need tighter control over the request 5. If you request --format json, parse one JSON document; do not treat the output as NDJSON 6. Summarize whether retrieval was triggered, whether relevant items were returned, and whether session continuity is preserved
Customer Environment Principle
- In customer environments, assume repository source code is unavailable.
- Execute tasks using only the installed skills, the packaged
vsCLI surface (--help, command output, and observed runtime behavior), and explicit user-provided information. - Do not rely on reading local repository source files, generated repo snapshots, or implementation details to decide runtime actions.
- If the installed CLI behavior conflicts with a skill, trust the installed CLI behavior first.
- If the skills and the packaged CLI still do not provide enough information to proceed safely, stop and ask the user instead of searching source code.
Constraints
vs chat ...is the conversational search runtime surface- When debugging parsing issues, inspect the raw JSON response first instead of adding an extra line-oriented parser
- If a command failure or user follow-up turns into a product concept, capability, API field, console UI path, purchase, billing, or general troubleshooting question outside this chat workflow, temporarily hand off to
vs-product-qa; return to this workflow only after the grounded product answer is complete.