revenuecat-identify-user
Tie RevenueCat identity to your app's auth system. Use when the user asks to log in to RevenueCat, sync a user with RevenueCat, switch RevenueCat user on login, log out of RevenueCat, move a user from anonymous to identified, set appUserID, or handle account switching on iOS, Android, Kotlin Multiplatform, Flutter, or React Native.
68
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (RevenueCat identity and auth integration), provides comprehensive trigger terms covering multiple user phrasings and platforms, and explicitly states when it should be used. It follows the recommended pattern with a concise 'what' statement followed by a detailed 'Use when...' clause.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: tying RevenueCat identity to auth system, logging in, syncing users, switching users on login, logging out, moving from anonymous to identified, setting appUserID, and handling account switching. | 3 / 3 |
Completeness | Clearly answers both 'what' (tie RevenueCat identity to your app's auth system) and 'when' with an explicit 'Use when...' clause listing numerous specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'log in to RevenueCat', 'sync a user', 'switch RevenueCat user', 'log out', 'anonymous to identified', 'set appUserID', 'account switching', plus platform names (iOS, Android, Flutter, React Native, Kotlin Multiplatform). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around RevenueCat identity/auth integration. The specific product name (RevenueCat), feature terms (appUserID, anonymous to identified), and use cases make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has a well-designed structure with clear platform detection logic, useful shared concepts, and strong verification steps. Its main weakness is the lack of any inline executable code—all implementation is deferred to platform files that are not present in the bundle, making the skill incomplete as a standalone document. The shared concepts section is informative but slightly verbose in places.
Suggestions
Include at least one brief executable code example inline (e.g., a minimal logIn/logOut snippet for one platform) so the skill is actionable even without the platform files.
Provide the referenced platform files (platforms/ios.md, platforms/android.md, etc.) in the bundle, or include condensed inline examples for each platform.
Tighten the shared concepts bullets by removing explanations Claude would infer (e.g., 'RevenueCat treats the ID as an opaque string') and focusing on non-obvious constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The shared concepts section is mostly useful but includes some explanatory padding (e.g., 'RevenueCat treats the ID as an opaque string and it is difficult to change later') that Claude would already understand. The platform detection section is well-structured but slightly verbose. Overall efficient but could be tightened. | 2 / 3 |
Actionability | The skill provides clear conceptual guidance and a solid detection algorithm, but contains no executable code examples directly in the body. All implementation is deferred to platform files which are not provided in the bundle. The shared concepts describe what to do but don't show how with concrete code snippets. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced: detect platform → understand shared concepts → read platform-specific implementation → verify. The verification section (step 4) provides explicit validation checkpoints including checking the dashboard, testing sign-out/sign-in flows, verifying anonymous-to-identified aliasing, and error handling for logOut while anonymous. | 3 / 3 |
Progressive Disclosure | The skill references five platform-specific files with clear paths and has a logical structure pointing to them. However, no bundle files were provided, meaning the referenced platform files (platforms/ios.md, etc.) don't actually exist in the bundle. The overview-to-detail split is well-designed in principle but cannot be verified, and the skill also references other skills (integrate-revenuecat, revenuecat-purchase-flow) without paths. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- RevenueCat/rc-claude-code-plugin
- Commit
407e465
- Reviewed
Table of Contents
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.