component-view-test
Write, fix, and update component view tests (*.view.test.tsx) for MetaMask Mobile using the tests/component-view/ framework. Use when creating a new view test file, fixing a failing view test, updating tests after a component change, or creating a new renderer or preset for a view.
94
92%
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 an excellent skill description that clearly defines its scope, lists concrete actions, includes an explicit 'Use when' clause with multiple trigger scenarios, and is highly distinctive due to its specific file patterns and framework references. It follows the third-person voice convention and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Write, fix, and update component view tests', specifies the file pattern '*.view.test.tsx', names the framework 'tests/component-view/', and mentions creating renderers or presets. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (write, fix, update component view tests using the tests/component-view/ framework) and 'when' with an explicit 'Use when' clause listing four specific trigger scenarios: creating new test files, fixing failing tests, updating after component changes, and creating renderers/presets. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'view test', 'view.test.tsx', 'MetaMask Mobile', 'failing view test', 'component change', 'renderer', 'preset'. These cover the natural language a developer working in this codebase would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically targets '*.view.test.tsx' files in the 'tests/component-view/' framework for MetaMask Mobile. The file pattern, framework name, and project scope make it very unlikely to conflict with other testing or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 skill that serves as an effective routing document for a complex testing framework. Its strengths are the clear decision tree, actionable golden rules, executable commands, and excellent progressive disclosure to reference files. The main weakness is moderate redundancy between the decision tree, workflow summary, and reference table, which could be consolidated to save tokens.
Suggestions
Consolidate the decision tree, workflow summary section, and reference table into a single section — they currently overlap significantly in describing which reference to open for which task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts, but includes some redundancy — the decision tree, workflow summary, and reference table all partially overlap in describing when to open which file. The 'What Are Component View Tests?' section could be trimmed since it partially restates what the golden rules enforce. | 2 / 3 |
Actionability | Provides concrete, executable commands (exact jest invocation with config file, coverage command), specific file paths, a clear decision tree for which action to take, and 10 enforceable golden rules with specific do/don't guidance. The test IDs convention, AAA pattern requirement, and assertion patterns are all specific and actionable. | 3 / 3 |
Workflow Clarity | The decision tree clearly sequences the three main workflows (write, fix, update) with explicit steps including when to open references, when to run tests, and a self-review checkpoint after tests pass. The fix workflow includes a run → identify → fix → re-run feedback loop. Validation is built into the process via the self-review checklist reference. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the SKILL.md serves as a clear overview with a decision tree directing to three well-signaled, one-level-deep reference files (writing-tests.md, navigation-mocking.md, reference.md). The table at the bottom clearly maps actions to files with descriptions of when to open each. Explicit instruction to not read references until directed. | 3 / 3 |
Total | 11 / 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.