expo-ui-jetpack-compose

`@expo/ui/jetpack-compose` package lets you use Jetpack Compose Views and modifiers in your app.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/expo/skills/expo-ui-jetpack-compose/SKILL.md

Quality

Content

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, highly actionable, and well-organized for a simple skill, with executable examples and versioned references throughout. The main gap is workflow clarity: guidance is given as bullets rather than a sequenced, checkpointed workflow.

Suggestions

Convert the build/usage guidance into a short numbered workflow with explicit validation checkpoints (e.g. after install → rebuild → read .d.ts to confirm API → implement → verify against docs).

Add an explicit verify step for the .d.ts reading flow so it functions as a validate-before-implement feedback loop rather than a soft suggestion.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive — bullets, a focused Host example, and exact import paths — with no padding explaining concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	It provides fully executable guidance: an install command, a rebuild command, a shell snippet to locate .d.ts files, versioned doc URLs, and a copy-paste-ready JSX example, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps are present (install, rebuild, read .d.ts, fetch docs, wrap in Host) but are not sequenced as a numbered workflow with explicit validation checkpoints, matching 'steps listed but checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	The skill is a concise single-purpose doc under 50 lines with clearly organized sections and only one-level-deep outward pointers (docs/.d.ts), which per the simple-skills note can score 3 without internal bundle references.	3 / 3
	Total	11 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 clearly identifies the package and domain but is generic and lacks an explicit use-when trigger, capping several dimensions at 2. Adding concrete actions and a 'Use when...' clause would raise specificity, completeness, and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. 'Use when building Expo/React Native UI with Jetpack Compose components or Material 3 styling on Android.'

Enumerate multiple concrete actions (e.g. 'render Compose Views, apply modifiers, build scrollable lists and themed UI') instead of the single verb 'use' to lift specificity.

Include common alternative terms users say (e.g. 'Jetpack Compose UI, Android Views, Material Design 3, Compose modifiers') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Jetpack Compose Views and modifiers') and a single action ('use'), matching the 'names domain and some actions, but not comprehensive' anchor rather than listing multiple concrete actions.	2 / 3
Completeness	It states what the package does but includes no 'Use when...' clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	'Jetpack Compose' is a term developers naturally say, but the description offers no common variations (e.g. Compose UI, Android Views, Material 3), landing on 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	Scoped to a specific package gives it a clear niche, but the trigger is technical and could still overlap with general Compose or Android skills, matching 'somewhat specific but could still overlap'.	2 / 3
	Total	8 / 12 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
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/expo/skills/expo-ui-jetpack-compose/SKILL.md
Commit: 11c74d6

Reviewed: 8 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.