What is true-skills test-review.md?

A set of instructions for reviewing Katalon tests for requirement coverage, case quality, reliability, and environment readiness. Reliability includes checking whether tests are unstable or flaky, meaning they sometimes fail without a product change.

Finding uncovered requirements, inspecting test-case signals, reviewing execution stability and results, and checking whether the application under test is ready.

It turns test information into a clear verdict with named weak cases instead of leaving a team to interpret disconnected metrics.

How katalon-labs/true-skills configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to katalon-labs/true-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/katalon-labs/true-skills/main/.kiro/steering/test-review.md

Clone the repo

git clone --depth 1 https://github.com/katalon-labs/true-skills

Made for: Kiro.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/katalon-labs/true-skills/test-review/github.svg)](https://agentmods.dev/instructions/katalon-labs/true-skills/test-review)

Your own site

<a href="https://agentmods.dev/instructions/katalon-labs/true-skills/test-review"><img src="https://agentmods.dev/badge/instructions/katalon-labs/true-skills/test-review/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/katalon-labs/true-skills/test-review"><img src="https://agentmods.dev/badge/instructions/katalon-labs/true-skills/test-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,146 This file is loaded in full into every session.

When invoked 1,146 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01146	$0.01146
Opus 5.5	$0.00458	$0.00458
Sonnet 5.5	$0.00229	$0.00229
Haiku 4.5	$0.00115	$0.00115

Measured 1mo ago against content hash 8efcfc971122, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

true-skills test-review.md 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 1mo 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.

.kiro/steering/test-review.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Katalon Test Review

Use this skill for the review stage: inspect coverage, quality, and reliability so weak tests do not enter the pipeline. The output is a verdict with named weak cases, never a metric dump.

Availability Boundary

Available via MCP: coverage review (fetch_requirement_data, find_test_cases_by_requirement, fetch_test_configuration_data), quality review (fetch_test_case_data), reliability review (fetch_test_stability_data, find_test_results), and environment readiness (read_auts).
Not directly available: code/object review, local debug, StudioAssist Ask — these are Studio-desktop operations. For code-lane review, defer to test-case-to-playwright / playwright-execute. Use Browser/Playwright only for AUT sanity checks when asked.

Review Workflow

+---------------------+     +----------------------+     +----------------------+
| Coverage review     | --> | Quality review       | --> | Reliability review   |
| reqs + config       |     | case design signals  |     | flakiness/stability  |
+---------------------+     +----------------------+     +----------------------+
                                                                   |
                                                                   v
                                                         +----------------------+
                                                         | Verdict + weak cases |
                                                         +----------------------+

Steps and tool rules

Coverage review. fetch_requirement_data + find_test_cases_by_requirement for requirement coverage; fetch_test_configuration_data for browser/platform coverage. Flag orphan requirements and under-covered configurations.
Quality review. fetch_test_case_data for design signals; read representative cases with read_test_case when a signal is ambiguous. Flag non-atomic cases (many assertions), missing negative/boundary variants, and vague expected results.
Reliability review. fetch_test_stability_data for flakiness; find_test_results for recent pass/fail history. Flag probabilistically flaky cases that will erode pipeline trust.
Environment readiness. read_auts to confirm an executable AUT exists for the suite.
Verdict. One of Approve / Approve with fixes / Reject for pipeline, followed by the specific cases to fix and why. State the risk if approving with known gaps.

Read the full file on GitHub · 102 lines

Changes

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.

1mo ago First seen · 102 lines · 1,146 tokens per session scan A 8efcfc971122

Subscribe to this mod's changes

true-skills test-review.md is an instructions file published in the GitHub repository katalon-labs/true-skills (10 stars, last pushed 4d ago), licensed MIT. It adds 1,146 tokens to every session, about $0.0046 per session on Opus 5.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-08.

Analytics and metrics Claude Code Testing agent-skills agentic-ai ai-testing cursor github-copilot

understudy qa-engineer.instructions.md

Instructions for erniker/understudy, covering qa engineer — quality assurance specialist instructions, 🎯 recommended model: {{modelqa}}, (use /model in cli or model picker in vs code), identity and expertise.

erniker/understudy · 1,600 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

true-skills: Instructions file for Kiro