qa-input-validation@1.8.0
CAUTIONPublisher claims: "在测试工作流开始前检查用户输入是否包含有效的需求描述和足够的上下文信息。当用户的测试请求过于模糊(只说"帮我测试"却没说测什么)、缺少必要的需求文档或上下文时,应当使用此技能来验证输入完整性。如果输入验证失败,必须返回缺失信息清单要求用户补充。适用于启动任何测试设计流程的第一步。 触发场景:需求不清楚、信息不够、这个需求能测吗、用户输入模糊时自动激活(第一步)。 Use when the user asks about: checking whether the user's test request contains enough context before any test design work starts." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-29 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
No other findings across 301 lines in 3 files.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim kokxi: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.