e2e-test
Add and fix Detox E2E tests (smoke and regression) for MetaMask Mobile using withFixtures, Page Objects, and tests/framework. Use when creating a new spec, fixing a failing E2E test, adding page objects and selectors, or adding MetaMetrics analytics expectations (analyticsExpectations).
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (Detox E2E testing for MetaMask Mobile), lists specific capabilities and patterns, and includes an explicit 'Use when' clause with multiple concrete trigger scenarios. The description is concise yet comprehensive, uses third-person voice correctly, and includes domain-specific terminology that would naturally match developer queries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: add Detox E2E tests, fix failing E2E tests, create specs, add page objects and selectors, add MetaMetrics analytics expectations. Also names specific tools/patterns: withFixtures, Page Objects, tests/framework. | 3 / 3 |
Completeness | Clearly answers both 'what' (add and fix Detox E2E tests using specific patterns) and 'when' (explicit 'Use when' clause listing four specific trigger scenarios: creating specs, fixing failing tests, adding page objects/selectors, adding analytics expectations). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'Detox', 'E2E tests', 'smoke', 'regression', 'MetaMask Mobile', 'spec', 'failing E2E test', 'page objects', 'selectors', 'analyticsExpectations', 'MetaMetrics'. These cover the domain-specific vocabulary a developer working on this project would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Detox E2E testing specifically for MetaMask Mobile, with named patterns (withFixtures, Page Objects) and specific features (analyticsExpectations). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured routing/overview skill that excels at progressive disclosure and workflow clarity. Its main weakness is that it defers all concrete, executable guidance to reference files, meaning the skill itself lacks actionable code examples or templates. There is also some redundancy between the decision tree and the reference table.
Suggestions
Include at least one minimal, executable code example of a basic spec using withFixtures and POM to make the skill immediately actionable without opening references.
Consolidate the decision tree and the reference table into a single navigation structure to reduce redundancy and improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but has some redundancy — the decision tree and the reference table at the bottom convey largely the same information. The 'What This Skill Does' section also partially restates the workflow overview. However, it avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The 10 Golden Rules provide concrete, specific constraints (e.g., 'no element(by.id()) in spec files', 'always use withFixtures'), and the decision tree gives clear routing. However, the skill itself contains no executable code examples or copy-paste-ready templates — all concrete guidance is deferred to reference files. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Steps 0-5) with an explicit iteration/feedback loop (Step 5: fix → lint → run until green). The decision tree provides unambiguous routing for different task types. Validation checkpoints are explicit (lint/tsc before running, iterate until green). | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the skill serves as a clear overview/router with well-signaled, one-level-deep references organized by action. The decision tree and reference table both clearly indicate when to open each file, and the instruction to not read references until directed is explicit. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- MetaMask/metamask-mobile
- Commit
bee9b14
- 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.