Expo Native UI Guide

The files show no malware, credential theft, covert exfiltration, destructive defaults, or disproportionate permissions. Camera, microphone, and media-library permissions are partly disclosed, and the README says telemetry is off by default. Points are deducted because confirmation, data-flow boundaries, rollback, failure recovery, and dependency-security guidance are incomplete; media examples also use remote resources.

The coverage is broad and most examples are readable, but there are material contradictions: the main document forbids Picker and expo-symbols while controls.md demonstrates Picker and icons.md imports expo-symbols. Expo Go, SDK, and New Architecture compatibility is also incomplete. Static review provides no key-path tests or abnormal-input feedback, so the score remains below the 10-point static ceiling.

The audience and main scenarios are clear, and routing is explicitly delegated to expo-router. References are organized by animation, controls, media, storage, and related topics. Points are deducted for missing explicit inputs, outputs, non-fit boundaries, and trigger conditions; platform and SDK constraints are scattered, with no Chinese-language support or mainland-China reachability guidance.

The skill has front matter, a version, MIT licensing, topic-based reference files, and many examples. Points are deducted for the absence of a changelog, explicit maintenance owner, or update path; installation notes, troubleshooting, known limitations, and compatibility matrices are thin, and internal naming and policy conflicts remain.

The material supplies directly adaptable snippets for native-feeling Expo colors, controls, animation, media, storage, and visual effects, so the core use case has clear value. Points are deducted because some recommendations or examples may be outdated, contradictory, or SDK/platform-specific, and there is no static evidence of representative output validation; users still need substantial manual checking.

Evidence consists mainly of revisioned skill files, references, README, license, and limited CI checks; the README identifies Expo documentation, CLI, and EAS CLI as the source of truth. Points are deducted because CI checks description/version limits rather than the skill’s technical guidance, and there is no committed test suite, third-party corroboration, or independently reproducible key-path evidence, keeping the score at or below the static 5-point ceiling.