BC api-toolkit-free
API工具箱免费版是一套面向独立开发者与一人公司的轻量级API测试与调试工具集。围绕"请求构造—认证管理—错误诊断—文档速查"四件事，提供可复制即用的curl/HTTPie模板、常见认证流程速查表、HTTP状态码与错误体诊断决策树，以及一份覆盖15类共80+主流第三方服务的端点索引。Use
API工具箱免费版是一套面向独立开发者与一人公司的轻量级API测试与调试工具集。围绕"请求构造—认证管理—错误诊断—文档速查"四件事，提供可复制即用的curl/HTTPie模板、常见认证流程速查表、HTTP状态码与错误体诊断决策树，以及一份覆盖15类共80+主流第三方服务的端点索引。Use
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useSKILL.md:112Credential used in a network call (verify the destination is the intended service) (security demo / example)curl -H "Authorization: Bearer $TOKEN" https://api.example.com/v1/data
demo
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Map keys must be unique at line 21, column 1: suggested_price: "9.9 CNY/per_use" tools: ["read", "write", "exec"] ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "pricing_tier" - note
frontmatter-keyunknown frontmatter key "pricing_model" - note
frontmatter-keyunknown frontmatter key "suggested_price"
Process rating: all ten parameters 51/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
- 30Running it twice. 3 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2345 tokens
- low 10 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
- +2Single-language instructions
- +3Description length 145: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.