OpenParable
Skip to content
← Back to skills

Vs Alias Mapping

Apps & Automation
vs-alias-mapping

Vs Alias Mapping is an Agent Skill for apps & automation published in the volcengine/SearchCLI repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Provide system alias mapping for Search CLI. Invoke this skill when user mentions "Search CLI", "search_cli", or tries to execute search_cli commands.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/volcengine/SearchCLI/blob/HEAD/skills/vs-alias-mapping/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/vs-alias-mapping, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

  • Before executing any mapped concrete 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.
  • Never execute a command literally named search_cli.
  • Always use the vs prefix and VIKING_ environment variables.
  • If alias resolution or mapped CLI execution fails and the user asks a product concept, capability, API field, console UI path, purchase, billing, or general troubleshooting question outside alias mapping, temporarily hand off to vs-product-qa; return to this workflow only after the grounded product answer is complete.

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.