SKILLEMALL.ai

AC qa-ai-blindspot-compensation

AI在生成测试用例时存在六大系统性盲区:时序依赖、并发冲突、资源竞争、状态累积、数据一致性、第三方集成差异。评审完AI生成的用例之后,必须用此技能做盲区补盲——因为AI几乎一定会漏掉这些。如果你心里觉得"好像还差点什么但说不上来",这就是答案。每个盲区维度至少补2-3个场景,总补盲数12-18个。 触发场景:还有什么没测到、AI漏了什么、补盲、全面覆盖、是不是不够、哪还没测、盲区分析、遗漏场景、时。 Use when the user asks about: compensating for known blind spots in AI-generated test cases — timing dependencies, concurrency conflicts, resource contention, state accumulation, data consistency, and third-party integration differences.

ClawHub Agent Skills author: kokxi v1.8.0 MIT-0 3 files body ≈ 741 tokens Open the sourceclawhub.ai↗ analyzed 15 d ago

AI在生成测试用例时存在六大系统性盲区:时序依赖、并发冲突、资源竞争、状态累积、数据一致性、第三方集成差异。评审完AI生成的用例之后,必须用此技能做盲区补盲——因为AI几乎一定会漏掉这些。如果你心里觉得"好像还差点什么但说不上来",这就是答案。每个盲区维度至少补2-3个场景,总补盲数12-18个。…

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

Integrationtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    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: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 59/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
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 31 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 741 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 439: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 31 items
    • +4Has examples (4 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +1License stated

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

    External checks

    ClawHub: clean
    This is a Markdown-only QA helper that guides test blind-spot review and does not show hidden execution, persistence, or data exfiltration behavior.
    LLM: benign (high) · VirusTotal: · 29 Sept 2026