AC openrouter-models
拉取并分析 OpenRouter 模型目录——涵盖 8 项定价（prompt / completion / cache_read / cache_write / web_search / reasoning / image / audio）、上下文长度及输入输出模态（text、image、file、audio、video）。适用于用户询问 OpenRouter 模型对比、"最便宜的支持 X 能力的模型"、"所有 Claude/GPT/Gemini 变体"、免费模型、模型价格对比、模型定价分析等场景。不适用于非 OpenRouter 聚合的通用 LLM 定价问题，也不用于生成或对话任务。
拉取并分析 OpenRouter 模型目录——涵盖 8 项定价（prompt / completion / cacheread / cachewrite / websearch / reasoning / image /…
As a process C 52/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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 contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
medium Dangerous commands
cmd-autorun-instructionSKILL.md:29Instructs the agent to auto-run a script on every session**Tip:** Always run `fetch_models.py` first to ensure the data is current.
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")
Process rating: all ten parameters 52/100
- 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
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 15 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1046 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 296: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 15 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.