SKILLEMALL.ai

CD testany-debug

分析 Testany 测试失败原因 - 排查问题、查看日志、定位根因;处理签名日志前先单独加载本 skill,勿回显原始请求。

TestAny-io/testany-agent-skills Agent Skills author: TestAny-io MIT 6 files · 3 scripts body ≈ 1 288 tokens Open the sourcegithub.com↗ analyzed 3 d ago

分析 Testany 测试失败原因 - 排查问题、查看日志、定位根因;处理签名日志前先单独加载本 skill,勿回显原始请求。

As a process D 37/100 · Unfinished process — References files that are not bundled: ../testany-guide/references/concepts.md

ProcedureInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
D
37/100
Unfinished process
References files that are not bundled: ../testany-guide/references/concepts.md
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: 4. 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: ../testany-guide/references/concepts.md

Process rating: all ten parameters 37/100

Will not run. References files that are not bundled: ../testany-guide/references/concepts.md
  • 0Tools and files. 1 referenced file(s) missing: ../testany-guide/references/concepts.md
  • 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
  • 20When it triggers. No condition that starts the skill
  • 100Steps. 30 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1288 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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 63: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 30 items
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 1 scripts are documented

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