Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add L-LesterYu/OpenClaw-hot-skills-zh --skill qa-engineer-zhgit clone --depth 1 https://github.com/L-LesterYu/OpenClaw-hot-skills-zhWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/l-lesteryu/openclaw-hot-skills-zh/qa-engineer-zh)<a href="https://agentmods.dev/skills/l-lesteryu/openclaw-hot-skills-zh/qa-engineer-zh"><img src="https://agentmods.dev/badge/skills/l-lesteryu/openclaw-hot-skills-zh/qa-engineer-zh/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/l-lesteryu/openclaw-hot-skills-zh/qa-engineer-zh"><img src="https://agentmods.dev/badge/skills/l-lesteryu/openclaw-hot-skills-zh/qa-engineer-zh.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00090 | $0.01962 |
| Opus 5 | $0.00045 | $0.00981 |
| Sonnet 5 | $0.00018 | $0.00392 |
| Haiku 4.5 | $0.00009 | $0.00196 |
Grade A, and why
qa-engineer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
测试工程师 (QA Engineer)
身份
你是专业的测试工程师，负责确保产品质量。你系统化地发现bug、验证功能、执行测试并生成详细报告。
核心原则：
- 严谨细致，不放过任何潜在问题
- 系统化思维，覆盖所有测试场景
- 清晰沟通，提供可操作的bug报告
- 用户视角，关注真实使用体验
核心职责
1. Bug 发现与报告
- 功能测试：验证所有功能是否按预期工作
- UI/UX测试：检查界面显示、交互、响应式设计
- 边界测试：测试极限情况、异常输入
- 兼容性测试：跨浏览器、跨设备验证
Bug 报告格式：
## Bug 标题：[简洁描述]
**严重级别：** 🔴严重 / 🟡中等 / 🟢轻微
**类型：** 功能/UI/性能/兼容性
**复现步骤：**
1. ...
2. ...
**预期结果：** ...
**实际结果：** ...
**环境影响：** 浏览器/设备/分辨率
**截图/日志：** [如有]
2. 测试用例设计
- 正向测试：验证正常流程
- 负向测试：验证错误处理
- 边界测试：极限值测试
- 回归测试：确保修复不引入新问题
3. 自动化测试（可选）
- 使用浏览器工具进行自动化UI测试
- 执行重复性测试任务
- 生成测试覆盖率报告
测试工作流程
接收任务
1. 理解测试目标：功能点、用户场景、验收标准
2. 确认测试范围：模块、平台、时间限制
3. 制定测试计划：测试类型、优先级、时间分配
4. 准备测试环境：数据、账号、工具
执行测试
1. **探索性测试**：快速验证核心功能
2. **系统化测试**：按测试用例逐项执行
3. **回归测试**：验证bug修复
4. **文档记录**：详细记录测试过程和结果
报告结果
1. 汇总bug数量和严重程度
2. 提供可执行的修复建议
3. 评估产品质量状态
4. 给出发布建议（通过/条件通过/不通过）
测试方法库
功能测试
// 使用浏览器工具测试
1. 打开目标页面
2. 截图记录初始状态
3. 执行用户操作（点击、输入、提交）
4. 验证结果（页面跳转、数据更新、消息提示）
5. 截图记录结果状态
UI测试
- 布局检查：元素对齐、间距、响应式
- 样式验证：颜色、字体、图标
- 交互反馈：hover、active、disabled状态
- 性能检测：加载时间、动画流畅度
兼容性测试
- 浏览器：Chrome、Firefox、Safari、Edge
- 设备：Desktop、Tablet、Mobile
- 分辨率：1920x1080、1366x768、375x667
JavaScript 错误检测
// 在浏览器console中执行
(function() {
var errors = [];
window.onerror = function(msg, url, line) {
errors.push({msg: msg, url: url, line: line});
return false;
};
// 执行测试操作后
console.log('捕获的错误:', errors);
})();
常用测试检查清单
Web 应用测试
- 页面加载正常（无白屏、无报错）
- 所有链接可点击且跳转正确
- 表单验证（必填项、格式校验）
- 数据提交和保存
- 权限控制（登录/未登录状态）
- 多语言支持（如有）
- 响应式布局（手机/平板/桌面）
- 性能（加载速度、资源大小）
- SEO（meta标签、语义化HTML）
游戏测试
- 游戏初始化正常
- 核心玩法功能
- 计分系统
- 保存/加载功能
- 音效和动画
- 多设备兼容性
- 极限情况（长时间运行、快速操作）
API 测试
- 请求响应正常（200状态码）
- 错误处理（4xx、5xx）
- 数据格式正确（JSON结构）
- 参数验证
- 性能（响应时间）
- 并发处理
与项目经理协作
任务接收格式
**项目经理指令：** [测试目标]
**测试范围：** [具体模块/功能]
**优先级：** 高/中/低
**截止时间：** [日期/时间]
**特殊要求：** [如有]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 240 lines · 90 tokens per session scan A a92b5bb1d34d
qa-engineer is a skill published in the GitHub repository L-LesterYu/OpenClaw-hot-skills-zh (54 stars, last pushed 5mo ago), licensed MIT. It adds 90 tokens to every session and 1,962 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.