Real Skill packageSource verifiedClawHub registry

qa-critical-thinking

当需要挑战已有假设、挖掘隐含约束、发现"所有人都没想过"的测试场景时使用此技能。测试中最常犯的错误是接受了需求文档里的隐含假设——比如"用户一定会有网络"、"输入一定有内容"、"操作顺序一定正确"。用「如果不呢」的深度质疑方式反向思考,暴露那些被默认为"正常"的异常场景。每一个测试场景都应该走一遍"如果这个假设不成立呢"的质疑流程。 触发场景:还有什么、如果...会怎样、逆向思考、你怎么看、这样够吗、质疑、挑战需求、有没有漏、需要怀疑和深度分析时。 Use when the user asks about: challenging unstated assumptions in a requirement to surface scenarios that nobody considered.

Identity and source

Publisher attributionkokxiregistry owner unverified by skillvetai
Functional categorySoftware Developmentautomatically inferred · 53% rule confidence
Package forminstruction bundle3 recorded files
Canonical sourceClawHub registryclawhub:kokxi:qa-critical-thinking
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-critical-thinking

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-critical-thinking

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-critical-thinking

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-critical-thinking
clawhub inspect @kokxi/qa-critical-thinking --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
3 / 3 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:33:57 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:6ac57b7af0e551d7ed76166577590370c00b85eada833f2ea0f86b4ca29e6754
Show up to 3 recorded paths
  • references/thinking-exercises.md
  • skill-card.md
  • SKILL.md

Source changelog

**Changelog for qa-critical-thinking v1.8.0** - Major refactor: moved all critical thinking exercises into a dedicated reference file to reduce SKILL.md length and improve context efficiency. - Added `references/thinking-exercises.md` with detailed scenario-based exercises. - Updated SKILL.md to reference the new exercises file and clarified when to access it. - Removed `skill-card.md`. - Enhanced metadata and structure in SKILL.md for easier integration and maintenance. - Improved documentation on when and how to apply the skill, emphasizing usage within a broader workflow.

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:e88f29ebd84713600a9571f56a0ce91a6ef9fc32a6af397c4adc4981db28337d
1.7.69/1/2026sha256:49626f30bf6fd832d4bb6ef67539b238b367e5e3698715dc0fa591f19cd9b488
1.7.58/30/2026sha256:a6167ab453624292043ded23a1a2311b8aec67260d63338d2d898a90113189ef