BC qwen-orchestrator
Qwen Chat (chat.qwen.ai) access via Puppeteer browser automation with CDP interceptor. Persistent daemon (~35ms startup), health checks, graceful shutdown, PM2 management. Configurable via `.qwen.json`. Use when: (1) need Qwen responses without API key, (2) code analysis, review, or generation, (3) text analysis, summarization, translation, (4) web search via Qwen's built-in search, (5) "consult Qwen" or ask-qwen.sh.
As a process C 64/100 · Has gaps — weak spots: result and completion, when it triggers, progress reporting
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
How to improve
- 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 · 8
✓ No critical or high findings
Medium and low: 8
-
medium Obfuscation
uni-mixed-script-wordauth-check.js:138Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (1 occurrence)logFn(`\x1b[31mТребуется авторизация в Qwen Chat. Запусти ask-qwen.sh --visible --wait --dry-run, войди вручную, затем повтори запрос.\x1b[0m`);
-
low Dangerous commands
cmd-privilegeask-puppeteer.js:1941Privilege escalation / world-writable permissions (detector / deny-list definition; string literal in code, not executed)'--no-sandbox', '--disable-setuid-sandbox',
detectorcode literal -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:80High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…bKX+KS9G…yMA/NhKJ…RGz/Q==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:141High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Wwy+ghLE…vfU/YnxW…fdg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:169High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…sGd+f4+f7C+Nik/MCk2…MPT/yRKvg++FZhQ…GqA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:211High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…bgK+BO66q+ZpKq…RhN+7lnv…m9g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:246High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…2BV+FY5ZFezP/ypmwayk68+NzzA…NFD/uUmBJuGoXw==",
detector -
low Dangerous commands
cmd-privilegeqwen-daemon.js:149Privilege escalation / world-writable permissions (string literal in code, not executed)'--disable-setuid-sandbox',
code literal
Files scanned: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 38 steps
- 100Failures and branches. 10 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2881 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 420: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.