CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

82

1.25x
Quality

73%

Does it follow best practices?

Impact

99%

1.25x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/expo/skills/use-dom/SKILL.md

The canonical home for this skill is use-dom in Intelligent-Internet/ii-agent

SKILL.md
Quality
Evals
Security

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.

A strong, example-driven reference: fully executable code covering the realistic use cases, explicit rules and limitations, and clean section organization. The only notable improvements are trimming minor redundant boilerplate across snippets and moving the longest examples into a references file.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no explaining what webviews or libraries are — with only minor trimmable padding: the opening section restates the frontmatter description, and each snippet repeats the 'dom: import("expo/dom").DOMProps' boilerplate and near-duplicate styled-component examples.

4 / 5

Actionability

Fully executable, copy-paste-ready TSX throughout: the 'use dom' directive pattern, dom prop options, async native-action props, recharts/react-syntax-highlighter usage, the router-hooks workaround, asset requiring, and platform behavior — covering the common cases comprehensively.

5 / 5

Workflow Clarity

Single-action skill made unambiguous by the numbered 'Rules for DOM Components' checklist and an explicit problem→solution pattern for router hooks; no validation checkpoints are needed since nothing is destructive or batch-oriented. Minor gap: no explicit step ordering for first-time setup.

4 / 5

Progressive Disclosure

No bundle files exist, and the single self-contained file is well-sectioned with a clear header hierarchy (When to Use / When NOT / Rules / patterns / Platform Behavior / Tips), making navigation easy. Minor gap: some long example sections (recharts, router workarounds) could be split into a references/ file to keep SKILL.md leaner.

4 / 5

Total

17

/

20

Passed

Description

65%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 states concrete, distinct capabilities in a clear niche, but lacks any explicit 'when to use' trigger guidance, which limits its discoverability and caps completeness. Adding a 'Use when...' clause and a few more natural trigger terms (e.g. React Native, web-only libraries) would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when running web-only libraries (recharts, syntax highlighters, rich text editors) in an Expo/React Native app, or when migrating existing React web components to native.'

Include the natural synonyms users would say — 'React Native' and 'webview' variants — to improve trigger-term coverage from good to comprehensive.

Optionally enumerate 1-2 more concrete capabilities (charts, iframes/embeds, WebGL) to lift specificity beyond 1-2 actions.

DimensionReasoningScore

Specificity

Names the domain ('Expo DOM components', 'webview on native') and 1-2 concrete actions ('run web code in a webview on native and as-is on web', 'migrate web code to native incrementally'), but coverage is not comprehensive — no mention of charts, web-only libraries, or CSS features.

3 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the second sentence ('Migrate web code to native incrementally') is another capability statement, not a 'when'. Per rubric guidance this caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'Expo DOM components', 'webview', 'web code', 'native', 'web', 'migrate'. A few natural terms users would say are missing, e.g. 'React Native' and specific web-only library names like 'recharts'.

4 / 5

Distinctiveness Conflict Risk

'Expo DOM components' is a clear niche with distinct, specific triggers; minimal overlap or conflict risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.