Name: revenuecat
Rating: 60.4 (1 reviews)
Author: RevenueCat

Blog Docs Log in Get started

revenuecat

Used for all interaction with RevenueCat not covered by a different skill

1.08x

Quality

58%

Does it follow best practices?

Impact

38%

1.08x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./revenuecat/skills/revenuecat/SKILL.md

Quality

Content

75%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.

The body is appropriately lean and points Claude to the right tool and docs, but lacks specifics on which MCP operations to perform or when to consult the docs versus the MCP server. Adding a short list of key MCP operations would improve actionability.

Suggestions

List 2-3 key RevenueCat MCP operations (e.g., 'get_customer_purchase_history', 'list_offerings') so Claude knows what is callable without browsing docs.

Clarify when to consult the docs URL versus calling the MCP server directly (e.g., 'Call the MCP server for live data; consult the docs only for schema/field reference').

Add a minimal section header (e.g., '## Usage') to give the short body light structure.

Dimension	Reasoning	Score
Conciseness	The two-sentence body ('Use the RevenueCat MCP server for all interaction with RevenueCat' and the docs URL with the '.md' tip) is lean and assumes Claude's competence with no padding, matching 'lean and efficient; every token earns its place'; it is not a 4 because there are no over-explanation instances to trim.	5 / 5
Actionability	It gives concrete pointers (named MCP server, specific docs URL, the '.md' URL trick) but no executable commands or specific MCP tool calls, matching 'some concrete guidance but incomplete; missing key details'; it is not a 4 because which MCP operations to use are unspecified, and not a 2 because the pointers are specific rather than mere hints.	3 / 5
Workflow Clarity	This is a simple single-purpose skill whose core action ('Use the RevenueCat MCP server for all interaction with RevenueCat') is unambiguous, scoring near the top per the simple-skill note; it is not a 5 because the secondary instruction to consult docs introduces a mild branch without specifying when each path applies.	4 / 5
Progressive Disclosure	The body is appropriately brief with no monolithic wall of text and no nested references (only a one-level external docs pointer), and no bundle files exist to misorganize; it is not a 5 because there are no section headers to structure the content, even though little structure is needed.	4 / 5
	Total	16 / 20 Passed

Description

41%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.

The description correctly targets a specific product niche but is vague about capabilities and lacks explicit 'Use when...' trigger guidance. Adding concrete actions and natural trigger phrases would lift the weakest dimensions.

Suggestions

Add 1-2 concrete actions, e.g. 'Fetch subscription status, manage offerings, and read customer entitlements via RevenueCat'.

Append an explicit trigger clause, e.g. 'Use when the user asks about RevenueCat subscriptions, entitlements, or in-app purchase data'.

Include natural synonyms/users' phrases (e.g. 'subscriptions', 'paywall', 'entitlements') so the skill triggers on real user language.

Dimension	Reasoning	Score
Specificity	The phrase 'all interaction with RevenueCat' names the domain but provides no concrete actions (e.g., fetch subscriptions, manage offerings), matching the 'names the domain but actions are minimal or generic' anchor; it is not a 1 because it does specify a real product domain, and not a 3 because no concrete capabilities are enumerated.	2 / 5
Completeness	It states a clear (if broad) 'what' ('all interaction with RevenueCat') while 'when' is only weakly implied by the negative clause 'not covered by a different skill', and there is no explicit 'Use when...' trigger guidance, which per the guidelines caps completeness at 3; it is not a 2 because a 'what' is present, and not a 4 because the 'when' is not explicit.	3 / 5
Trigger Term Quality	The only keyword is the product name 'RevenueCat'; there are no natural user-facing phrases such as 'Use when managing subscriptions' or 'in-app purchases', matching the 'one or two generic keywords; missing the natural phrases users say' anchor; it is above 1 because the product name is a real trigger, but below 3 for lack of common variations.	2 / 5
Distinctiveness Conflict Risk	RevenueCat is a specific SaaS product giving the skill a clear niche with minimal conflict risk against unrelated skills, matching 'mostly distinct; minor overlap risk'; it is not a 5 because 'all interaction ... not covered by a different skill' is a broad catch-all that could overlap with a future RevenueCat-specific skill.	4 / 5
	Total	11 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: RevenueCat/rc-claude-code-plugin
Path: revenuecat/skills/revenuecat/SKILL.md
Commit: 7aa440b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.