Name: revenuecat
Rating: 35.6 (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

18%

Does it follow best practices?

Impact

38%

1.08x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./revenuecat/skills/revenuecat/SKILL.md

Quality

Content

22%

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

This skill is extremely minimal, providing almost no actionable guidance beyond pointing to an MCP server and external documentation. It lacks concrete examples, specific tool/command usage, workflow steps, or any structured content that would help Claude effectively interact with RevenueCat. The only useful piece of information is the `.md` URL suffix tip for accessing docs.

Suggestions

Add concrete examples of MCP server tool calls for common RevenueCat operations (e.g., fetching subscriber info, checking entitlements, listing offerings).

List the specific MCP server tools available and their parameters, or at minimum provide a quick-start example showing a complete interaction.

Add a workflow for common tasks like checking a user's subscription status, including what tools to call and in what order.

Include specific guidance on when to use the MCP server vs. when to consult the docs, and what common pitfalls to avoid.

Dimension	Reasoning	Score
Conciseness	The content is very short (2 sentences), which is efficient, but the second sentence about appending `.md` to URLs is useful non-obvious information. However, the first sentence is somewhat redundant if the skill's purpose is already clear from context.	2 / 3
Actionability	The skill provides no concrete commands, code examples, API calls, or specific MCP server tool names. It only vaguely directs to use an MCP server and refer to docs, without showing how to actually interact with RevenueCat.	1 / 3
Workflow Clarity	There is no workflow, no steps, no sequence, and no validation. The skill provides no guidance on how to accomplish any specific task with RevenueCat.	1 / 3
Progressive Disclosure	It references external docs with a useful tip about accessing markdown versions, but there are no bundle files, no structured sections, and no clear navigation to specific topics or capabilities.	2 / 3
	Total	6 / 12 Passed

Description

14%

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 description is a vague catch-all that fails to specify any concrete capabilities, actions, or meaningful trigger conditions. It relies entirely on the existence of other skills to define its scope by exclusion, which makes it nearly useless for skill selection. It needs a complete rewrite with specific actions and explicit trigger guidance.

Suggestions

List specific concrete actions this skill performs with RevenueCat (e.g., 'Configure offerings, manage entitlements, set up paywalls, query subscriber status').

Add an explicit 'Use when...' clause with natural trigger terms like 'RevenueCat setup', 'subscriptions', 'in-app purchases', 'entitlements', 'paywalls'.

Instead of defining scope by exclusion ('not covered by a different skill'), positively define what this skill handles to reduce conflict risk with other RevenueCat skills.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'All interaction with RevenueCat' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	The 'what' is essentially absent (no specific capabilities listed), and the 'when' is defined only as a catch-all fallback ('not covered by a different skill'), which provides no actionable trigger guidance.	1 / 3
Trigger Term Quality	It includes 'RevenueCat' which is a relevant keyword a user might mention, but provides no other natural trigger terms related to specific tasks, features, or concepts (e.g., subscriptions, in-app purchases, paywalls, entitlements).	2 / 3
Distinctiveness Conflict Risk	As a catch-all description, it is inherently conflict-prone. It defines itself only by exclusion ('not covered by a different skill'), making it impossible to distinguish from other RevenueCat-related skills without knowing the full skill set.	1 / 3
	Total	5 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: RevenueCat/rc-claude-code-plugin
Commit: 473fd50

Reviewed: 1 day 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.