SKILLEMALL.ai

BD uniapp-test

专业的 uni-app / uni-app x 自动化测试工程师工作流。用于分析 .uvue 或 .vue 页面结构、生成或完善对应的 *.test.js 测试用例、运行测试 (Web / Android / iOS / 鸿蒙 / 微信小程序) 并修复失败的用例直至通过。任何时候用户提到 uni-app、uniapp、uni-app x、uvue、uni 自动化测试、uni 测试用例、`pages/` 目录下的页面测试、`*.test.js` 文件、`npm run test:web/test:app-android/test:app-ios/test:app-harmony/test:mp-weixin`、program.reLaunch、page.$、page.waitFor 等 API,或希望"为某个页面写测试 / 跑测试 / 修复测试"时,都应使用本 skill,即使用户没有明确说"自动化测试"四个字。

ClawHub Agent Skills author: dengzy v1.0.0 MIT-0 3 files body ≈ 905 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
D
46/100
Unfinished process
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

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 2. 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")

Process rating: all ten parameters 46/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
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 100Steps. 34 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 905 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 411: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 34 items
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: clean
This is a markdown-only uni-app testing workflow whose file edits and test commands are disclosed and aligned with its purpose, but users should invoke it deliberately.
LLM: benign (high) · VirusTotal: · 29 May 2026