CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concise overview with a solid verification section, undermined by missing referenced platform files and absent executable code examples.

Suggestions

Add the missing platforms/*.md files (ios, android, kmp, flutter, react-native) or remove the references so navigation is not broken.

Include at least one short executable logIn/logOut snippet inline so the skill is actionable before the platform files are read.

Add an explicit error-recovery step (e.g., on logOut-with-anonymous-user error, fall back to the 'is signed in' guard and retry) to complete the workflow feedback loop.

DimensionReasoningScore

Conciseness

Lean and token-efficient; every line covers RevenueCat-specific behavior Claude would not already know (anonymous ID aliasing, logOut-on-anonymous errors, restore-vs-login), with no padding or explanation of generic concepts.

5 / 5

Actionability

Gives concrete API names and a precise platform-detection procedure, but no executable code and the 'platforms/*.md' files that should carry the wired-up logIn/logOut examples are absent from the bundle, leaving key implementation detail missing.

3 / 5

Workflow Clarity

Clear detect → concepts → implement → verify sequence with an explicit verification checklist, but no error-recovery feedback loop (validate → fix → retry) around the identity-switching operations.

4 / 5

Progressive Disclosure

The overview is well-signaled and one level deep by design, but the referenced 'platforms/ios.md', 'platforms/android.md', 'platforms/kmp.md', 'platforms/flutter.md', and 'platforms/react-native.md' files do not exist in the bundle, so navigation is broken.

3 / 5

Total

15

/

20

Passed

Description

100%Weight 40%Scale 1-5

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, specific description that answers what and when with concrete trigger phrases and natural keywords, tightly scoped to RevenueCat identity/auth integration.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'log in', 'log out', 'sync a user', 'switch RevenueCat user', 'move a user from anonymous to identified', 'set appUserID', 'handle account switching' — with comprehensive coverage across the skill's domain.

5 / 5

Completeness

Explicit 'what' ('Tie RevenueCat identity to your app's auth system') and an explicit 'Use when...' clause enumerating concrete trigger phrases.

5 / 5

Trigger Term Quality

Uses natural phrases a user would say ('log in to RevenueCat', 'log out', 'sync a user', 'switch RevenueCat user') plus synonyms and platform names (iOS, Android, KMP, Flutter, React Native).

5 / 5

Distinctiveness Conflict Risk

A narrow RevenueCat identity niche with distinct triggers; minimal overlap risk with sibling skills (setup, purchases, gating).

5 / 5

Total

20

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RevenueCat/rc-claude-code-plugin
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.