BC alltoken
Bootstrap a modular AllToken agent — chat, async image+video, model routing, OpenAI-compatible SDK. Works inside Hermes, OpenClaw, Claude Code, Codex CLI, OpenCode, or any runtime that loads SKILL.md.
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, execution cost
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useUSAGE.md:68Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -H "Authorization: Bearer $ALLTOKEN_API_KEY" https://api.alltoken.ai/v1/models | jq '.data[].id'
vendor-host
Files scanned: 2. 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") - warning
body-longSKILL.md body ≈ 10360 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 55/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
- 30Running it twice. 17 mutating operations with no state check
- 40Execution cost. Instruction body is 10360 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 57 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- low 20 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
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (28 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.
External checks
ClawHub: clean
The visible artifacts look like a normal AllToken bootstrap recipe, but using it will create project files, install packages, use an AllToken API key, and send requests to AllToken.
LLM: benign (medium) · VirusTotal: · 29 May 2026