revenuecat
Used for all interaction with RevenueCat not covered by a different skill
32
14%
Does it follow best practices?
Impact
38%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./revenuecat/skills/revenuecat/SKILL.mdQuality
Discovery
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, lacks natural trigger terms beyond the product name, and provides no meaningful guidance for when Claude should select it. It functions as a fallback bucket rather than a well-defined skill, making it nearly impossible for Claude to make informed selection decisions.
Suggestions
List specific concrete actions the skill performs with RevenueCat (e.g., 'Manages subscriptions, configures offerings, queries entitlements, and handles purchase events in RevenueCat').
Add a 'Use when...' clause with explicit trigger terms like 'subscriptions', 'in-app purchases', 'paywalls', 'entitlements', 'RevenueCat SDK', or 'revenue tracking'.
Replace the catch-all fallback framing ('not covered by a different skill') with a clear scope definition that distinguishes this skill from related 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 (e.g., manage subscriptions, query purchase data, configure offerings). | 1 / 3 |
Completeness | The 'what' is extremely weak ('all interaction' is not a meaningful description of capabilities), and the 'when' is defined only as a catch-all fallback ('not covered by a different skill'), which provides no explicit 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 like 'subscriptions', 'in-app purchases', 'entitlements', 'offerings', or 'paywalls' that users would commonly say. | 2 / 3 |
Distinctiveness Conflict Risk | As a catch-all skill ('not covered by a different skill'), it is inherently designed to overlap with other skills and provides no clear niche or distinct triggers to differentiate it. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a two-sentence stub that provides almost no actionable guidance. It tells Claude to use an MCP server and check docs but gives no concrete examples, commands, workflows, or structured content. It fails to teach Claude anything it couldn't infer from the skill's title alone.
Suggestions
Add concrete examples of common RevenueCat MCP server operations (e.g., specific tool calls for checking subscription status, managing entitlements) with expected inputs and outputs.
Provide a structured workflow for typical RevenueCat tasks, such as looking up a customer, checking entitlements, or debugging purchase issues, with clear step sequences.
Add section headers and organize content into at least a quick-start section and a reference section listing available MCP server tools/capabilities.
Include specific guidance on when and how to fetch docs pages (e.g., which doc pages are most relevant for common tasks) rather than a generic pointer to the docs site.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is very short (2 sentences), which is lean, but the phrase 'for all interaction with RevenueCat' is somewhat redundant given the skill's purpose. It's brief but not because it's well-crafted—it's brief because it lacks substance. | 2 / 3 |
Actionability | The skill provides no concrete commands, code examples, or specific instructions on how to use the RevenueCat MCP server. It merely says to 'use' it and 'refer to' docs, which is vague direction rather than executable guidance. | 1 / 3 |
Workflow Clarity | There is no workflow, no steps, no sequence, and no validation checkpoints. The skill provides no guidance on how to accomplish any specific task with RevenueCat. | 1 / 3 |
Progressive Disclosure | There is no structure whatsoever—no sections, no headers, no references to bundle files. The external docs link is mentioned but with no guidance on what to look for or how to navigate them. | 1 / 3 |
Total | 5 / 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.