Menu
Audit tests that may pass without proving the claimed behavior. Use for periodic test-quality reviews or when coverage looks healthy but regressions still escape.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | false-confidence-test-audit |
| description | Audit tests that may pass without proving the claimed behavior. Use for periodic test-quality reviews or when coverage looks healthy but regressions still escape. |
| when_to_use | Activate only when the user requests a test-quality, false-confidence, or assertion-strength audit. Do not rewrite tests until each weakness is reproduced or supported by concrete evidence. |
| argument-hint | [test path, suite, or commit range] |
| disable-model-invocation | true |
| license | Apache-2.0 |
| compatibility | ["codex","claude-standalone","claude-plugin","copilot-plugin","github-repo","open-standard","cursor-native","opencode-native"] |
| result-schema | {"type":"object","required":["scope","findings","commands_run","limitations"],"properties":{"scope":{"type":"string"},"findings":{"type":"array","items":{"type":"object","required":["path","claim","evidence","severity","recommended_probe"],"properties":{"path":{"type":"string"},"claim":{"type":"string"},"evidence":{"type":"string"},"severity":{"type":"string","enum":["high","medium","low"]},"recommended_probe":{"type":"string"}}}},"commands_run":{"type":"array","items":{"type":"string"}},"limitations":{"type":"array","items":{"type":"string"}}}} |
| metadata | {"author":"controlkeel","version":"1.0","category":"quality","ck_mcp_tools":["ck_context","ck_validate","ck_finding","ck_regression_result"]} |
Find tests whose green result overstates what they prove. This is an evidence audit, not a request to maximize coverage or replace outcome tests with implementation checks.
Return output matching the declared result schema. A clean audit states what was inspected and which claims were actually challenged; “no findings” without commands and limitations is incomplete.
Run objective, repeatable improvement work under an immutable verifier and hard iteration, cost, time, and no-progress limits. Use for approved experiments with an automated metric and sandboxed worker.
Write concise, calm technical responses whose structure matches the decision, evidence, or sequence being communicated. Use when drafting substantial plans, reviews, findings, documentation, or completion summaries.
Operate inside a ControlKeel-governed session. Use this before code edits, shell execution, delegation, deploy work, or any task that needs CK validation, findings, budget, proof, or routing context.
Keep a governed session within budget. Use this before long-running agent work, bulk processing, or any task where spend pressure could change the plan.
Close a governed work session with validation, proof, findings, budget, digest, learning, and handoff checks. Use when the user asks to wrap up, stop for the day, or leave work ready for another agent.
Persist session state and hand off in-progress work to a background agent or delegated execution. Use when work outgrows the current session, context is near limit, or a task needs to continue unattended.
