根据PRD或者你的测试用例来编写和修改测试用例
v1.0.1全面测试用例编写和优化技能。当用户需要基于需求文档或现有测试用例设计、评审、优化测试用例时使用。 技能支持分析用户提供的需求文档（PRD、用户故事、API文档等）或现有测试用例， 生成全面、准确的测试用例，或对现有测试用例进行评审、完善和优化。 技能覆盖功能、性能、安全、易用性、界面、兼容性、异常场景等多个测试维...
⭐ 0· 36·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (comprehensive test-case writer) aligns with the SKILL.md content. The skill requests no credentials and has no install steps, which is appropriate. One minor note: compatibility.tools lists shell-style utilities (bash, grep, glob, edit, write) that are not referenced in the prose; those tools could allow file I/O in some runtimes but their presence is not inconsistent with a skill that may read user-provided documents.
Instruction Scope
SKILL.md stays on-topic: it instructs the agent to analyze user-provided requirements or existing test cases and to produce/optimize test cases across multiple dimensions. It does not instruct reading unrelated system files, environment variables, or exfiltrating data to external endpoints.
Install Mechanism
No install spec and no code files (instruction-only). This minimizes risk and is proportionate for a documentation/authoring skill.
Credentials
The skill declares no required environment variables, no credentials, and no config paths — appropriate for the stated functionality.
Persistence & Privilege
Flags show always:false and normal user-invocable/autonomous settings. The skill does not request permanent presence or elevated system-wide privileges.
Assessment
This skill is instruction-only and appears internally consistent with its purpose of generating and improving test cases. Before using it: (1) do not paste sensitive credentials or production-only secrets into prompts — the skill does not need them; (2) if your agent runtime grants skills file access or shell access (the compatibility.tools list suggests that capability), avoid giving the skill direct access to sensitive files unless you intend it; (3) review generated test cases for correctness and for any project-specific legal/IP constraints (the skill explicitly references commercial game titles, so be careful about proprietary or NDA-covered materials); (4) treat outputs as draft guidance and validate them in your test environment. If you want a stronger assurance, ask the publisher for provenance (source/homepage) or request that the skill explicitly document how it handles user-supplied artifacts.Like a lobster shell, security has layers — review code before you run it.
latestvk97bzkp6bvqbvhf0t3e0yp01nn84afzx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.