revenuecat-status
Get a quick overview of your RevenueCat project configuration including apps, products, entitlements, offerings, and webhooks.
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./revenuecat/skills/revenuecat-status/SKILL.mdQuality
Discovery
67%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 is specific about what it does and targets a clear niche (RevenueCat project configuration), making it distinctive. However, it lacks an explicit 'Use when...' clause, which limits completeness, and uses second person ('your') which is noted but not as heavily penalized as first person. Adding trigger guidance and more natural user terms would strengthen it.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about their RevenueCat setup, subscription configuration, or wants to inspect their in-app purchase products and offerings.'
Include natural trigger terms users might say, such as 'subscriptions', 'in-app purchases', 'IAP setup', 'monetization config', or 'RevenueCat dashboard'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete entities: apps, products, entitlements, offerings, and webhooks. The action 'Get a quick overview of your RevenueCat project configuration' is concrete and clear. | 3 / 3 |
Completeness | Clearly answers 'what' (get an overview of RevenueCat project configuration including specific entities), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'RevenueCat', 'apps', 'products', 'entitlements', 'offerings', 'webhooks', and 'project configuration', which are relevant. However, it misses common user phrasings like 'subscription setup', 'in-app purchases', 'IAP', or 'monetization' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'RevenueCat' is a very specific product/platform, making this skill highly distinctive and unlikely to conflict with other skills. The combination of RevenueCat + project configuration overview creates a clear niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that clearly instructs Claude on how to orchestrate multiple RevenueCat MCP tools to produce a project status report. The workflow is logical and complete, with good error handling and a useful output template. Minor verbosity in the description section and some redundancy between sections prevent a perfect conciseness score.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like the Description block that largely repeats the usage context. The output format template is useful but slightly verbose. Some redundancy between the description and the instructions. | 2 / 3 |
Actionability | The skill provides concrete, specific tool names to call (list-projects, list-apps, list-products, etc.), a clear output format template, specific argument handling logic including partial matching, and explicit error handling guidance. Claude knows exactly what to do at each step. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with logical ordering: parse arguments → get projects → gather stats → present summary → highlight issues. Error handling is addressed (no matching project → list available ones). The 'Highlight Issues' step serves as a validation/quality check on the data gathered. This is a read-only operation so destructive-operation feedback loops are not needed. | 3 / 3 |
Progressive Disclosure | For a single-purpose skill under 80 lines with no need for external references, the content is well-organized with clear sections (Description, Usage, Instructions with numbered steps). No bundle files are needed for this straightforward MCP tool orchestration skill. | 3 / 3 |
Total | 11 / 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.