CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

testing-review

Reviews unit/integration/E2E coverage, checks for fragile/flaky tests, asserts clinical safety checks, and reviews verification sequence. Use during test addition or refactoring.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable review skill: concrete file conventions, named verification commands with proportionality rules, and domain-specific safety checks, all in a compact body. Its only weakness is that the review checklist is a flat list of assertions rather than a sequenced review workflow with validation steps.

DimensionReasoningScore

Conciseness

The ~25-line body is lean and directive with zero concept over-explanation: every line ('Mock these services with predictable fixtures', 'verify:release only after explicit user approval') adds guidance Claude doesn't already have.

5 / 5

Actionability

Concrete, executable guidance throughout: file conventions ('*.test.ts', 'ui-*.spec.ts'), named commands ('verify:ui', 'verify:release'), and specific safety assertions (citation indexing, fallback on weak RAG evidence, tenant isolation). Minor gaps remain, e.g. no example of how to detect or flag flakiness.

4 / 5

Workflow Clarity

Sequence is present and ordered ('before starting' protocol, checklist areas, then 'After a completed PR review, post one Review record comment'), and the verification gates act as escalation checkpoints with an explicit approval condition for verify:release. The checklist items themselves are unordered bullets rather than a validated sequence, keeping it below a 5.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files needed; sections are well-organized (Protocol, Checklist, Gates) and the external doc references (AGENTS.md, docs/codex-review-protocol.md, pull-request-workflow.md) are one level deep and clearly signaled — per the simple-skill guideline this earns a 5.

5 / 5

Total

18

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with concrete third-person actions and an explicit use-when clause. It falls just short of top marks because the trigger set is narrow and one action ('reviews verification sequence') is vague.

Suggestions

Replace or sharpen 'reviews verification sequence' with a concrete action, e.g. 'reviews verification command selection (verify:ui / verify:release gating)'.

Broaden the when-clause with natural triggers users would actually say: 'Use when adding or refactoring tests, reviewing test coverage, or debugging flaky tests.'

Mention the testing stack (Vitest + Playwright) in the description to improve trigger-term matching and distinctiveness.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Reviews unit/integration/E2E coverage', 'checks for fragile/flaky tests', 'asserts clinical safety checks') in third person, but 'reviews verification sequence' is fuzzy, leaving minor gaps in coverage.

4 / 5

Completeness

Both what (four named review actions) and when ('Use during test addition or refactoring') are present and explicit, but the when-clause is narrow and omits natural triggers like 'reviewing tests' or 'checking coverage'.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('unit', 'integration', 'E2E', 'flaky tests', 'test addition', 'refactoring'), but misses common variations users would say such as 'test suite', 'specs', or framework names (Vitest/Playwright).

4 / 5

Distinctiveness Conflict Risk

The clinical-safety and flaky-test focus gives it a clear niche, but a testing-review scope overlaps somewhat with generic code-review skills triggered by 'refactoring'.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.cursor/skills/testing-review/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.