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 a well-structured 'Use when' clause with multiple trigger scenarios, and is highly distinctive. It follows the third-person voice convention and provides enough specificity to be reliably selected from a large pool of skills.
| 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' (explicit 'Use when' clause covering 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'. The file pattern and framework name are particularly useful for matching user requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically scoped to MetaMask Mobile component view tests using a particular framework and file pattern. The '*.view.test.tsx' pattern and 'tests/component-view/' framework reference make it very unlikely to conflict with general testing or other skill types. | 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 provides clear, actionable guidance for a complex testing framework. Its strongest aspects are the decision tree for workflow routing, the explicit golden rules that serve as guardrails, and the progressive disclosure strategy with clearly signaled references. Minor verbosity in explanatory sections (e.g., 'What Are Component View Tests?') slightly reduces token efficiency but doesn't significantly detract from overall quality.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some sections that could be tightened — the 'What Are Component View Tests?' section explains concepts Claude could infer, and the framework overview repeats information available in references. The golden rules section is valuable but slightly verbose with explanations of each rule. | 2 / 3 |
Actionability | Provides concrete, executable commands (exact jest invocation with config file, coverage command), a clear decision tree for which action to take, specific file paths, and explicit golden rules with named constants and patterns. The guidance is specific enough to act on immediately. | 3 / 3 |
Workflow Clarity | The decision tree clearly sequences the three main workflows (write, fix, update) with explicit steps and validation checkpoints (run tests, then self-review checklist). The fix workflow has a clear feedback loop: run → identify error → apply fix → re-run. The 'no render-only scenarios' rule serves as a validation gate. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in SKILL.md and well-signaled one-level-deep references (writing-tests.md, navigation-mocking.md, reference.md). The table mapping actions to files with 'when to open' guidance is particularly effective. The decision tree explicitly tells Claude when to open each reference. | 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
dedb5dd
- 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.