Content
81%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-routed reference with executable code throughout and a clean decision tree, supported by real one-level-deep bundle references. Its main cost is token weight: several sections duplicate generic fetch/React Query knowledge Claude already has, and the main file carries detail that belongs in references.
Suggestions
Trim or collapse the "Basic Fetch Usage" and React Query setup sections to a few lines each — Claude already knows standard fetch and TanStack Query boilerplate; keep only the Expo-specific deviations (expo/fetch preference, paused-fetchStatus handling).
Move the token-refresh concurrency pattern and the env-var TypeScript declaration block into a reference file, keeping a one-line pointer in the main body.
Add natural trigger synonyms (HTTP, REST, axios migration) to the description's trigger clause to round out keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Sections like "Basic Fetch Usage" (plain fetch GET/POST), standard React Query provider setup, and generic exponential-backoff retry re-teach patterns Claude already knows, while the Expo-specific material (four states, hydration gating, EXPO_PUBLIC_ build-time inlining) genuinely earns its tokens — fitting mostly-efficient-with-some-unnecessary-explanation rather than the minor-trims anchor. | 3 / 5 |
Actionability | Nearly all examples are copy-paste executable and cover the common cases — complete useQuery/useMutation components, an ApiError class with retry wrapper, a SecureStore auth wrapper, and a typed apiClient — with only the token-refresh snippet's undefined helpers (isTokenExpired, refreshToken) as an exception. | 5 / 5 |
Workflow Clarity | The Decision Tree unambiguously routes every covered scenario (loaders vs basic fetch vs caching vs auth vs offline vs env config) with no gaps, and the skill involves no destructive or batch operations that would require validation checkpoints. | 5 / 5 |
Progressive Disclosure | Both referenced files (references/expo-router-loaders.md, references/offline-and-cancellation.md) exist, are listed with one-line descriptions, linked from sections 5/7 and the decision tree, and are one level deep — but the ~470-line body inlines detailed material (env-var TypeScript declarations, token-refresh machinery) that could live in references, fitting good-structure-with-minor-gaps rather than a clear overview. | 4 / 5 |
Total | 17 / 20 Passed |