Provide system alias mapping for Search CLI. Invoke this skill when user mentions "Search CLI", "search_cli", or tries to execute search_cli commands.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Invoke this skill when the user refers to the CLI tool as "Search CLI" or "search_cli", to ensure the correct underlying binary (vs) is executed.
Before starting this skill workflow, run vs version check --json. Continue only when status is up-to-date. If status is update-available, stop and tell the user to update the cloned vs repository, then run git pull --ff-only, bash ./scripts/install.sh, and bash ./scripts/install-skills.sh all --target auto --force (PowerShell: scripts/install.ps1 and scripts/install-skills.ps1). If the status is unknown, stop and report that the CLI version could not be verified.
search_cli.vs binary (or its absolute path).vs CLI surface (--help, command output, and observed runtime behavior), and explicit user-provided information.vs ... command, 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.search_cli.vs prefix and VIKING_ environment variables.vs-product-qa; return to this workflow only after the grounded product answer is complete.When user says: "Use search_cli to auth login"
You should execute: vs auth login (or the absolute path like /path/to/vs-macos-arm64 auth login)
When user says: "Check search_cli doctor"
You should execute: vs doctor
Always keep this mapping in mind when interacting with the CLI tool in this workspace.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Volcengine official documentation lookup helper. Supports both document search and full-content fetch across Volcengine products, developer tools, support content, best practices, pricing, deployment, troubleshooting, API, SDK, and policy pages.
The English summary is being prepared. Showing the original description.
Conversational search runtime: send messages, keep sessions consistent, and verify retrieval behavior and responses.
The English summary is being prepared. Showing the original description.
Crawl websites (news, blogs, papers, GitHub, product docs, RSS feeds) into a fixed-schema JSONL file, then create a dataset and a searchable application in Viking AI Search. Supports one-time crawl and scheduled recurring crawl with automatic incremental sync.
The English summary is being prepared. Showing the original description.
onboarding workflow for creating datasets and applications in Viking AI Search. Supports one-time import from local files (JSON, JSONL, CSV) and MySQL databases, plus scheduled incremental sync for append-only JSONL files and MySQL. All sources are first exported to a bootstrap JSONL file; backend-driven schema inference handles detection, and optional background sync keeps the dataset up to date as new data arrives.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Create Viking web projects, start and verify a local preview, or deploy a generated project to Volcengine IGA Pages when explicitly requested. Includes agent-guided feature, eligible application, dataset, scene, and authentication choices. Use only after confirming the installed CLI exposes `vs project`; otherwise stop without taking action.
The English summary is being prepared. Showing the original description.