SKILLEMALL.ai

BF qa-quickcheck

AI 驱动的日常测试助手,覆盖 PR 静态审计、动态功能测试、回归策略,2 分钟上手

ClawHub Agent Skills author: HouYang995 v1.0.3 MIT-0 18 files body ≈ 650 tokens Open the sourceclawhub.ai analyzed 2 d ago

AI 驱动的日常测试助手,覆盖 PR 静态审计、动态功能测试、回归策略,2 分钟上手

As a process F 35/100 · Will not run — References files that are not bundled: scripts/http-test-runner.js, scripts/security-headers-check.js, scripts/data-factory.js

ProcedureAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: scripts/http-test-runner.js, scripts/security-headers-check.js, scripts/data-factory.js
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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 · 0

✓ No critical or high findings

Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: scripts/http-test-runner.js
  • warning missing-ref reference to a missing file: scripts/security-headers-check.js
  • warning missing-ref reference to a missing file: scripts/data-factory.js
  • note frontmatter-key unknown frontmatter key "categories"

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: scripts/http-test-runner.js, scripts/security-headers-check.js, scripts/data-factory.js
  • 0Tools and files. 3 referenced file(s) missing: scripts/http-test-runner.js, scripts/security-headers-check.js, scripts/data-factory.js
  • 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
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 650 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)
  • +3Description length 42: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (9 of 9)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.

External checks

ClawHub: suspicious
This QA testing skill is broadly aligned with testing, but it includes under-disclosed active execution, network requests, file writes, and unsafe template code execution that users should review before installing.
LLM: suspicious (high) · 3 Jul 2026