Real Skill packageSource verifiedClawHub registry

qa-test-reporting

输出面向不同受众的测试报告——日报给团队同步进度、周报给项目经理、质量报告给管理层决策。当测试执行完成需要汇总结果、或者上级问"质量怎么样"的时候使用此技能。不同角色关心的数据不同:开发关心Bug明细,经理关心通过率和趋势,老板关心风险和发版决策。报告内容适配受众,关键指标量化呈现,风险区域必须单独成节并醒目标注。 触发场景:测试报告、日报、周报、迭代报告、报告模板、质量汇报、进度汇报、向管理层汇报测试进展时。 Use when the user asks about: writing test reports for different audiences — daily reports for the team, weekly reports for the PM, and quality summaries for management.

Identity and source

Publisher attributionkokxiregistry owner unverified by skillvetai
Functional categoryData, Spreadsheets & Analyticsautomatically inferred · 59% rule confidence
Package forminstruction bundle4 recorded files
Canonical sourceClawHub registryclawhub:kokxi:qa-test-reporting
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 9/29/2026.claude/skills/qa-test-reporting

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 9/29/2026.agents/skills/qa-test-reporting

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 9/29/2026skills/qa-test-reporting

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @kokxi/qa-test-reporting
clawhub inspect @kokxi/qa-test-reporting --version 1.8.0

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
4 / 4 inspected as text
Checked
9/29/2026, 5:42:26 AM
Scanner
0.1.3
Policy
1.0.3
1 inferred permission indicators
  • network access — automatically inferred
1 dependency and API indicators
  • api: clawhub.ai
External clawhub result: clean

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
9/29/2026, 4:38:04 AM
Release binding
Matches this record
  • vt: clean
  • skillspector: suspicious
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:02fa827349c3292e4b274f425362d77235525e38197ea966d931eb89114c4137
Show up to 4 recorded paths
  • assets/report-templates.md
  • references/audience-needs.md
  • skill-card.md
  • SKILL.md

Source changelog

## qa-test-reporting v1.8.0 - Major update: Skill documentation and reporting structure revised for clarity and traceability. - SKILL.md reworked: clearer principles, stricter report structure, and explicit rules for conclusions and risk sections. - Reporting templates and audience-needs references added for easier report customization (`assets/report-templates.md`, `references/audience-needs.md`). - Outdated skill-card removed; migration to more detailed metadata. - Enhanced traceability and requirements for output content (IDs, reference values, and minimum report sections now more explicit). - Guidance and documentation now match upstream skill ecosystem structure and terminology.

Release security diff

mediumCompared fixed releases 1.7.7 and 1.8.0; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • permission surface changed
  • file surface changed
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.7.79/27/2026sha256:48232a75aa6a3dd5508713511b917079309ba0de58fb4de8d5fc31bc6d20f751
1.7.69/1/2026sha256:9c7383554d9e860ab95ad03ea6f1e2cbc3071fe88f337721009d394ed62c471e
1.7.58/30/2026sha256:30f511f1eeed0e9352ad591e186f5a751c4d5edbb8934d068169cbcc1e9f8fb0
1.7.08/16/2026sha256:710328440aeb370e18664d50f5d1567ddb1b1fed8b6fc368cf965929f8818104