use-dom
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
66
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 99%
↑ 1.25xAgent success when using this skill
Validation for skill structure
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a specific technology (Expo DOM components) and its purpose but lacks explicit trigger guidance, which significantly limits Claude's ability to know when to select this skill. The description would benefit from a 'Use when...' clause and more natural user-facing keywords.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Expo DOM components, embedding web views in React Native, or incrementally migrating web code to native apps.'
Include common user-facing keywords and variations such as 'React Native', 'hybrid app', 'web-to-native migration', 'cross-platform', or 'webview embedding'.
List more specific concrete actions such as 'create DOM components', 'embed React components in webviews', 'configure web-native interop'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Expo DOM components, webview, native/web) and describes actions (run web code, migrate incrementally), but lacks comprehensive concrete actions like specific operations or capabilities. | 2 / 3 |
Completeness | Describes what it does (run web code in webview, migrate web code) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'Expo DOM components', 'webview', 'native', 'web code', but missing common variations users might say like 'React Native', 'hybrid app', 'web-to-native', or 'cross-platform'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Expo DOM components' is fairly specific to a particular technology, but 'web code' and 'native' are broad terms that could overlap with general React Native or mobile development skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent code examples that are immediately usable. The main weaknesses are some unnecessary explanatory content at the beginning and lack of explicit workflow/validation steps. The document would benefit from trimming the 'when to use' sections and adding troubleshooting guidance.
Suggestions
Remove or significantly condense the 'What are DOM Components?' and 'When to Use/NOT to Use' sections - Claude can infer appropriate use cases from the examples
Add a troubleshooting section or validation steps (e.g., 'If the DOM component shows blank, check that props are serializable')
Consider splitting advanced topics (Expo Router integration, native actions) into separate reference files with links from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanatory sections like 'What are DOM Components?' and 'When to Use/NOT to Use' that explain concepts Claude could infer. The code examples are lean, but the surrounding prose could be tightened. | 2 / 3 |
Actionability | Excellent executable code examples throughout - every concept is demonstrated with copy-paste ready TypeScript/TSX code. The examples cover basic usage, props, native actions, web libraries, CSS, routing, and assets with complete, runnable snippets. | 3 / 3 |
Workflow Clarity | The skill covers individual features well but lacks explicit workflow sequencing for creating DOM components. There's no validation/verification step mentioned (e.g., how to test if the DOM component is working correctly, debugging tips for common issues). | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear headers, but it's a monolithic document with no references to external files for advanced topics. The platform behavior table and tips section are good, but detailed topics like debugging or performance optimization could be split out. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.