Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
volcengine avatar

Vs Alias Mapping

  • 2 installs
  • 1.2k repo stars
  • Updated July 31, 2026
  • volcengine/searchcli

Maps the user's 'Search CLI' or 'search_cli' intent to the correct underlying vs binary so agents execute the right command.

About

Provides a conceptual alias mapping so that references to Search CLI or search_cli are translated to the vs binary. A developer uses it so an agent runs the correct CLI when the user names the tool differently.

  • Intercepts search_cli intent and maps it to the vs binary
  • Assumes customer environments without source code, relying only on the packaged CLI surface

Vs Alias Mapping by the numbers

  • 2 all-time installs (skills.sh)
  • +1 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #445 of 550 CLI & Terminal skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/volcengine/searchcli --skill vs-alias-mapping

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2
repo stars1.2k
Last updatedJuly 31, 2026
Repositoryvolcengine/searchcli

What it does

Maps the user's 'Search CLI' or 'search_cli' intent to the correct underlying vs binary so agents execute the right command.

Files

SKILL.mdMarkdownGitHub ↗

Search CLI Alias Mapping

When to Use

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.

Preconditions

  • The agent is about to execute a CLI command based on the user's "Search CLI" intent.

Commands

  • No specific commands are required; this is a conceptual mapping.

Workflow

  • Intercept the intent to run search_cli.
  • Translate the intent to use the vs binary (or its absolute path).
  • Execute the mapped command.

Customer Environment Principle

  • In customer environments, assume repository source code is unavailable.
  • Execute tasks using only the installed skills, the packaged vs CLI 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

  • Never execute a command literally named search_cli.
  • Always use the vs prefix and VIKING_ environment variables.

<system-rule> IMPORTANT ALIAS MAPPING: 1. The user refers to this tool system as "Search CLI" or "search_cli". 2. However, the actual underlying executable binary is named "vs" (or variations like vs-macos-arm64, vs-linux-x64, vs-win-x64.exe). 3. Whenever you plan to use "Search CLI" capabilities, you MUST translate that intent into executing the vs binary (or the absolute path provided by the user). </system-rule>

Examples

  • 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.

Related skills

CLI & Terminalintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.