BF volcengine
Configure and use Volcano Engine (Volcengine) models including Doubao (Seed 2.0), GLM, DeepSeek, and Qwen. Use when: (1) Setting up Volcengine API access in OpenClaw, (2) Choosing between LLM and VLM (multimodal) models, (3) Configuring model aliases for easy access, (4) Troubleshooting authentication or connection issues with Volcengine providers.
As a process F 38/100 · Will not run — References files that are not bundled: configuration.md, configuration.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 55. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Configure and use Volcano Engine (Volcengine) models including Dou… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: configuration.md - warning
missing-refreference to a missing file: configuration.md
Process rating: all ten parameters 38/100
- 0Tools and files. 2 referenced file(s) missing: configuration.md, configuration.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (volcengine) differs from the folder (volcano-engine)
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 92 steps
- 100Execution cost. Instruction body is 3458 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 350: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 92 items
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (2 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.