CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/detox-testing

Authors React Native E2E tests with Detox (Wix) - gray-box architecture (runs in-process with the app), `element(by.id|by.text|by.label)` matchers, `waitFor()` for explicit sync beyond Detox's automatic async tracking, Jest runner. Use when the app is React Native and speed matters. For Flutter use flutter-testing; for black-box cross-platform use appium-testing; for YAML-declarative flows use maestro-flows; for non-RN native use xcuitest-suite or espresso-suite.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

92%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 well-structured body: every step is copy-paste executable, the workflow has explicit validation checkpoints with error-recovery loops, and detail is correctly pushed to a verified one-level-deep reference file. The only deduction is minor redundancy (auto-sync rationale repeated; worked example duplicating the Step 3 spec).

DimensionReasoningScore

Conciseness

Efficient overall — commands, complete code, and dense tables with little padding ('npm install --save-dev detox / npx detox init', anti-patterns table). Minor trimmable redundancy: the gray-box auto-sync point is restated in the intro and Step 5, and the worked example re-uses the Step 3 spec. Not a 5 because those repeats could be tightened; not a 3 because no section explains concepts Claude already knows.

4 / 5

Actionability

Fully executable throughout: install/scaffold commands, a complete runnable Jest spec, JSX `testID` snippets, `waitFor`/`whileElement` patterns, `detox test` invocations per platform, and a copy-paste-ready GitHub Actions YAML. Covers the common cases end-to-end.

5 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced with cross-references ('Add `testID` props (Step 4)' from the overview), explicit validation checkpoints ('Verify: `detox build` must finish and emit the app binary before Step 6'; 'assert every spec reports green'), and fix-and-re-run feedback loops ('read the Detox error... fix the matcher or add a `waitFor` (Step 5), and re-run').

5 / 5

Progressive Disclosure

SKILL.md stays an overview: the matcher/action/assertion catalog is split into `references/element-api.md`, which exists, is one level deep (it links only to external Detox docs), and is clearly signaled twice (Step 3 and the References section). Everything inlined — CI config, worked example, anti-patterns — is overview-appropriate, so navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

87%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: concrete capabilities at API specificity, an explicit 'Use when' trigger, and explicit routing to every neighboring skill. Only minor gaps — a few natural synonyms ('end-to-end', 'mobile test automation') and unmentioned capabilities (assertions, CI) keep specificity and trigger coverage at 4.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete capabilities with API-level specifics ('gray-box architecture (runs in-process with the app)', '`element(by.id|by.text|by.label)` matchers', '`waitFor()` for explicit sync', 'Jest runner'). Not a 5 because actions/assertions and CI coverage are absent from the description.

4 / 5

Completeness

Explicitly answers what ('Authors React Native E2E tests with Detox (Wix)... matchers... waitFor()... Jest runner') and when ('Use when the app is React Native and speed matters'), plus routing guidance to five alternatives. Matches the top anchor with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'React Native', 'E2E tests', 'Detox', 'speed matters', 'Flutter', 'black-box cross-platform', 'YAML-declarative'. Missing common variations like 'end-to-end' or 'mobile test automation', so it falls just short of the comprehensive synonym coverage anchor.

4 / 5

Distinctiveness Conflict Risk

Clear RN-E2E niche with explicit disambiguation: 'For Flutter use flutter-testing; for black-box cross-platform use appium-testing; for YAML-declarative flows use maestro-flows; for non-RN native use xcuitest-suite or espresso-suite.' Minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents