volcengine-find-skills — Claude Code skill: browse and install
The volcengine-find-skills Claude Code skill searches the Volcengine catalog and installs selected skills. It activates when a task needs a matching capability or the current Volcengine setup falls short.
MIT 292 installs ★ 37 updated 2026-11-16
npx skills add volcengine/volcengine-agent-toolkit --skill volcengine-find-skills -a claude-codeWhat volcengine-find-skills does
The skill browses Volcengine’s skill catalog, helps select the required entries, installs them for an agent, and checks their installation status. It can also search for a missing capability during an active Volcengine task.
The bundled scripts/find_skills.py script provides list, info, install, and status operations through the skills CLI. Installation needs python3, npx, and access to the npm registry. If GitHub and the CDN are unreachable and no local toolkit copy exists, installation fails.
What it helps with
- find a Volcengine skill for a specific task
- browse the full skill catalog
- install selected skills for an agent
- check whether a skill is installed
- find a missing capability during Volcengine work
Example prompts for the agent
- Find a Volcengine skill for infrastructure work.
- List the available Volcengine skills and pick one for this task.
- Install
volcengine-iacfor Codex and check its status.
How to install volcengine-find-skills
1Skills CLI (Vercel)
npx skills add volcengine/volcengine-agent-toolkit --skill volcengine-find-skills -a claude-code2Manually: put the files in place
~/.claude/skills/volcengine-find-skills/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/volcengine-find-skills/
1Skills CLI (Vercel)
npx skills add volcengine/volcengine-agent-toolkit --skill volcengine-find-skills -a codex2Manually: put the files in place
.agents/skills/volcengine-find-skills/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add volcengine/volcengine-agent-toolkit --skill volcengine-find-skills -a cursor2Manually: put the files in place
.cursor/skills/volcengine-find-skills/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install volcengine/volcengine-agent-toolkit skills/core/volcengine-find-skills2Manually: put the files in place
.github/skills/volcengine-find-skills/SKILL.md1Skills CLI (Vercel)
npx skills add volcengine/volcengine-agent-toolkit --skill volcengine-find-skills -a gemini-cli2Platform CLI
gemini skills install https://github.com/volcengine/volcengine-agent-toolkit --path skills/core/volcengine-find-skillsManually: put the files in place
.devin/skills/volcengine-find-skills/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add volcengine/volcengine-agent-toolkit --skill volcengine-find-skills -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about volcengine-find-skills
How do I install volcengine-find-skills in Claude Code?
Run npx skills add volcengine/volcengine-agent-toolkit --skill volcengine-find-skills -a claude-code. The skill file is placed at ~/.claude/skills/volcengine-find-skills/SKILL.md.
What does volcengine-find-skills do?
It browses the Volcengine skill catalog, helps select and install skills, then checks their installation status. It can search for missing capabilities during an active Volcengine task.
What does volcengine-find-skills require?
It needs python3, npx, and npm registry access for the skills CLI. If GitHub cannot be reached, the script can use the CDN or a local toolkit copy.
Source text
SKILL.md · MIT
---
name: volcengine-find-skills
description: >-
List, select, and install Volcengine skills from the volcengine-skills marketplace. Use when a
user asks which Volcengine skill or plugin handles a task, wants to browse every available skill,
needs an optional skill that is not currently installed, or asks to install or check the
installation status of a Volcengine skill. Also use to discover any core skill,
including this finder. Use as a fallback during a Volcengine operation when the currently loaded
or installed skills cannot cover the required product, tool, or workflow; inspect the full
catalog, select the missing capability, and install it.
license: MIT
metadata:
openclaw:
requires:
bins:
- python3
- npx
envVars:
- name: VOLCENGINE_TOOLKIT_BASE_URL
required: false
description: Base URL of the toolkit package used when GitHub is unreachable; defaults to https://cloudcache.volccdn.com/ve/skills
- name: VOLCENGINE_TOOLKIT_DIR
required: false
description: Local directory that holds the downloaded toolkit package; defaults to ~/.volcengine/agent-toolkit
---
# Volcengine Skills Finder
Use the bundled catalog to inspect every available skill and select the minimum skill set that
covers the request. Treat plugin ownership as catalog classification only; install exact skills.
## Decision flow
1. Detect whether the request starts with skill discovery or whether an active Volcengine task has
reached a capability gap in the currently loaded or installed skills.
2. Preserve completed work and pause only the unsupported part of the active task.
3. List the complete catalog without changing installation state.
4. Inspect every name, product domain, summary, and keyword, then select the minimum exact skill set
that covers the user's request. Make the selection directly when the catalog provides enough
information.
5. Pass only exact skill names to the installer. Use plugin ownership to explain classification,
never as the installation target.
6. Install through the `skills` CLI and verify the resulting installed state. Never report success
from process exit alone.
7. If the host cannot load a newly installed skill into the current thread, tell the user to start
a new thread and restate the original task plus completed context.
## List and select skills
Run the script relative to this skill directory:
```bash
python3 scripts/find_skills.py list
python3 scripts/find_skills.py list --json
python3 scripts/find_skills.py info <skill-or-plugin>
```
Always read the complete `list` output before selecting a skill. Use `--json` when keywords or the
English summaries help distinguish related skills. Choose by responsibility rather than name alone;
install multiple skills only when the request crosses distinct responsibilities.
The catalog includes all skills in `skills/core/` and every optional skill owned directly by a
product-domain plugin. `skills/specialized/<domain>/<skill>/` contains generated copies of those
optional skills, grouped by the plugin name without `volcengine-`; each skill is listed only once
in the catalog. If none of the listed responsibilities covers the request, report that the
repository does not currently provide a matching skill.
For an uncovered capability, continue the supported work and optionally include the
[feedback form](https://github.com/volcengine/volcengine-agent-toolkit/issues/new?template=feedback.yml)
at a natural summary so the user can describe the scenario they need. Invite at most once per
conversation across skills, without waiting for a reply. Feedback itself is optional, not a
capability gap that requires installation: use `volcengine-feedback` when already available and
requested by the user, otherwise offer the form or a redacted draft in the current conversation.
Do not install, log in, collect extra diagnostics, or restart the main conversation for feedback.
## Recover from a capability gap
Invoke this finder when a Volcengine task is already in progress and the available skills lack the
required product coverage, tool integration, or workflow. Treat that gap as a discovery request:
list the complete catalog, select and install the matching skill, then continue when the host can
load it. Carry forward the original goal, relevant evidence, and completed work so discovery does
not restart the task from scratch.
## Install selected skills
Install one or more exact skills for the current host:
```bash
python3 scripts/find_skills.py install <skill> [<skill> ...] --agent <agent-name>
python3 scripts/find_skills.py install volcengine-iac --agent codex
```
The script uses `npx skills add --skill` with `--full-depth` to discover skills nested under product
categories and plugin directories. It accepts only exact skill names, installs those skills directly, and verifies
every selected name with `skills list`. Omit `--agent` only when host auto-detection is intended.
Passing a plugin name is an error, even when every skill in that plugin is needed.
Use `--scope global` for user-level installation or `--scope project` for the current project. The
default is global. `--source` may point at a reviewed local checkout or another repository source;
otherwise the catalog's official repository is used.
When GitHub does not answer within a short probe, the script installs from the Volcengine CDN
instead: it downloads the toolkit package, verifies its SHA-256 against the release manifest,
unpacks it to `~/.volcengine/agent-toolkit` (or `VOLCENGINE_TOOLKIT_DIR`), and passes that directory
to the skills CLI. The fallback needs no flag and reports on stderr which source it used. If the
CDN is also unreachable, an existing local copy is used and its version is reported; with no local
copy the install fails and says so. The skills CLI itself still comes from the npm registry.
Use `--dry-run` when the user asks to inspect the command first. Installation is local, but any
later cloud-resource operation remains governed by the installed skill's own confirmation and
safety rules.
## Check status
Inspect catalogued skill installation state for the current host:
```bash
python3 scripts/find_skills.py status --agent codex
```
Do not equate "skill installed" with "skill loaded in this thread". Use the status only to verify
installation; start a new thread when the host cannot dynamically load the newly installed skill.
© volcengine · MIT · volcengine/volcengine-agent-toolkit