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.

1.25x

Quality

76%

Does it follow best practices?

Impact

99%

1.25x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/ii_agent/agents/skills/builtin/expo-use-dom/SKILL.md

Quality

Content

82%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.

The content is highly actionable with comprehensive executable examples and clean organization. It is slightly verbose in a few redundant examples but otherwise respects Claude's competence.

Suggestions

Consolidate the two similar styled-component examples into one to trim redundancy.

Consider moving the Router API reference list into a separate reference file to better separate overview from API detail.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code with brief framing; minor over-explanation (the 'What are DOM Components?' intro and a few near-duplicate styled-component examples) keeps it just below the lean anchor 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready examples covering the common cases — basic component, dom prop options, native actions, web libraries, CSS, router, and assets.	5 / 5
Workflow Clarity	Rules and pattern sections give unambiguous guidance for a non-destructive reference skill; no explicit multi-step sequence or validation checkpoints are needed, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references; all content is inline since no bundle files exist, which is appropriate but leaves minor room for splitting reference material out.	4 / 5
	Total	17 / 20 Passed

Description

70%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.

The description is specific, distinct, and uses natural trigger terms, but it omits an explicit 'Use when...' clause, capping its completeness. Adding trigger guidance would round it out.

Suggestions

Append an explicit 'Use when...' clause (e.g., 'Use when running web-only React libraries in an Expo app or migrating web components to native').

Add a few synonyms or concrete library triggers (e.g., 'recharts', 'react-syntax-highlighter') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Expo DOM components') and three concrete actions — 'run web code in a webview on native', 'as-is on web', and 'Migrate web code to native incrementally' — matching the 'several specific actions' anchor rather than the 1-2 actions of score 3.	4 / 5
Completeness	Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Expo DOM components', 'webview', 'web code', 'native', 'web') with good coverage; falls short of 5 because it lacks synonyms or explicit extensions.	4 / 5
Distinctiveness Conflict Risk	'Expo DOM components' is a clear niche with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Intelligent-Internet/ii-agent
Path: src/ii_agent/agents/skills/builtin/expo-use-dom/SKILL.md
Commit: 28563d6

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.