BD skill-composer
L2 编排层 - 智能技能编排引擎。自动编排多技能协作流程,分析技能依赖关系,优化执行策略(并行/串行决策)。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:275High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…ywo+qwL+oL8H…C1U+vRfLQDvw==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:291High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-Yqfm+XDx0+Prh3…1yC+JWZ2…IL7+vK+Clp7…D7g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:304High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…xZl+RoGR…fbT/ZgrF…0EA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:317High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…3bJ+V0If…IXN+CL65…a4w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:333High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…H47+FFon…OsV/4+RRsz…0ig==",
quoted
Files scanned: 6. 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") - note
frontmatter-keyunknown frontmatter key "origin" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (skill-composer) differs from the folder (skill-composer-pro)
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 23 steps
- 100Execution cost. Instruction body is 1040 tokens
- 100Running it twice. No mutating operations
- low 14 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)
- +3Description length 55: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -218 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 32 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: suspicious
This looks like a legitimate workflow-planning skill, but it asks for broad write and command-execution authority while describing automatic retries and fallback behavior without clear user approval boundaries.
LLM: suspicious (high) · VirusTotal: · 29 May 2026