expo-module

Guide for writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%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 body is a well-structured, actionable reference: concrete scaffold commands, complete multi-language code, a validated multi-step workflow, and clean progressive disclosure to verified reference files. It avoids re-explaining basics Claude already knows.

Dimension	Reasoning	Score
Conciseness	Largely lean and executable, assuming Claude's competence; the explanatory blockquote earns its place by documenting a concrete gotcha rather than padding with concepts Claude already knows.	3 / 3
Actionability	Provides copy-paste-ready commands (create-expo-module with CI=1 and a flag table) plus complete Swift, Kotlin, TypeScript, and JSON config examples — no pseudocode.	3 / 3
Workflow Clarity	Clear sequence (scaffold → rename → pod install) with an explicit validation checkpoint noting that skipping pod install "causes iOS build failures", plus enumerated removal steps for module-only/view-only variants.	3 / 3
Progressive Disclosure	Body is a concise overview pointing to five real, one-level-deep reference files (all verified to exist), each with a one-line description in a clearly signaled References section.	3 / 3
	Total	12 / 12 Passed

Description

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

A strong, third-person description that lists concrete capabilities and provides an explicit Use-when trigger, giving it high specificity, completeness, and distinctiveness. Voice is correctly third person with no over-claims.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete capabilities — "module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system" — rather than vague abstractions.	3 / 3
Completeness	Explicitly answers both what (the capabilities list) and when ("Use when building or modifying native modules for Expo"), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes natural user-facing terms ("Expo native modules", "native views", "config plugins", "building or modifying native modules") that a user would plausibly say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche — Expo native modules/views via the Expo Modules API — with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/expo/skills/expo-module/SKILL.md
Commit: 11c74d6

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