BC qwen-code
Run Alibaba Cloud Qwen Code CLI via background process for task execution, code review, and automation.
As a process C 62/100 · Has gaps — weak spots: result and completion, consistency, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenassets/examples/headless-mode.example.js:102High-entropy token-like string (may be an id, hash or a credential) (placeholder value)function exam…ion() {placeholder -
low Secrets in code
secret-high-entropy-tokenassets/examples/headless-mode.example.js:116High-entropy token-like string (may be an id, hash or a credential) (placeholder value)function exam…ons() {placeholder -
low Secrets in code
secret-high-entropy-tokenassets/examples/headless-mode.example.js:135High-entropy token-like string (may be an id, hash or a credential) (placeholder value)// exam…ion();
placeholder -
low Secrets in code
secret-high-entropy-tokenassets/examples/headless-mode.example.js:136High-entropy token-like string (may be an id, hash or a credential) (placeholder value)// exam…ons();
placeholder
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (qwen-code) differs from the folder (qwen-code-skill)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 29 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1531 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +3Description length 103: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 26 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.
External checks
ClawHub: suspicious
This looks like a legitimate Qwen Code wrapper, but it gives broad coding-agent authority that users should review before installing.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026