AC zero-token
零成本。不掉线。13个免费模型接管。主模型挂了？无感切换，用户根本不知道。 Zero token cost. Opus-level personality. 13+ free LLMs take over when your main model dies. No one notices. 無料。切断なし。Opus級の人格。13の無料モデルが自動で引き継ぎます。 $0. Sin caídas. 13+ modelos gratis toman el control cuando tu modelo principal falla. Zéro coût. Zéro coupure. 13 modèles gratuits prennent le relais automatiquement.
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Broad scope
meta-agent-memory-dumpSOUL.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokensSOUL.md
-
low Dangerous commands
cmd-background-processscripts/setup.sh:56Starts a background / autostarted processnohup npm start > "$FREE_WAY_DIR/free-way.log" 2>&1 &
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "repository"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 639 tokens
- 100Running it twice. No mutating operations
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
- +2Single-language instructions
- +3Description length 349: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (3 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.