XLSX vs expo-ui
Side-by-side comparison of two Claude Agent Skills. Pick the right one for Claude Code or Claude Desktop.
Comparison
| Feature | XLSX | expo-ui |
|---|---|---|
| Bundled scripts | yes | yes |
| Allowed tools | 3 | 1 |
| Install scope | personal | personal |
| Category | data | data |
| Verified | ||
| License | MIT | MIT |
| Author | Anthropic | Expo |
| Repo | anthropics/skills | expo/skills |
When to pick XLSX
Work with Excel (.xlsx) spreadsheets: read data, compute formulas, build sheets with formatting and charts, and export analysis as real workbooks.
When to pick expo-ui
Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo/ui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom/bottom-sheet, or RN built-in Picker/Switch; use @expo/ui instead. Fall back to RN built-ins only when @expo/ui is missing the component. NOTE: @expo/ui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList/FlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI/Jetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching.
Looking for something else? Browse all skills.