revenuecat-charts
Use when the user asks about RevenueCat data, analytics, charts, KPIs
63
43%
Does it follow best practices?
Impact
95%
1.48xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./revenuecat/skills/revenuecat-charts/SKILL.mdQuality
Discovery
22%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 essentially a trigger clause without any capability description. While it correctly identifies RevenueCat as its domain and provides a 'Use when' pattern, it completely fails to explain what the skill actually does — whether it queries APIs, generates reports, creates visualizations, or something else entirely. The description needs substantial improvement in specificity and completeness.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Queries RevenueCat subscription data, generates revenue charts, and calculates KPIs like MRR, churn rate, and LTV.'
Expand trigger terms to include common RevenueCat-related vocabulary users would naturally say, such as 'subscriptions', 'MRR', 'churn', 'revenue', 'in-app purchases', 'dashboard', or 'metrics'.
Restructure to follow the 'what + when' pattern: lead with specific capabilities, then follow with the 'Use when...' clause.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not describe any concrete actions or capabilities. It only mentions domain terms like 'data, analytics, charts, KPIs' but never states what the skill actually does (e.g., 'generates charts', 'queries RevenueCat API', 'calculates KPIs'). | 1 / 3 |
Completeness | The description answers 'when' (when the user asks about RevenueCat data/analytics/charts/KPIs) but completely lacks the 'what' — there is no explanation of what the skill actually does or what actions it performs. Missing the 'what' component makes this incomplete. | 1 / 3 |
Trigger Term Quality | Includes some relevant natural keywords like 'RevenueCat', 'analytics', 'charts', 'KPIs', and 'data' that users might say. However, it's missing common variations like 'revenue', 'subscriptions', 'MRR', 'churn', 'dashboard', or 'metrics' that users working with RevenueCat would naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'RevenueCat' provides a specific niche, which helps distinctiveness. However, generic terms like 'data', 'analytics', 'charts', and 'KPIs' could overlap with general analytics or charting skills. The lack of specific actions makes it harder to distinguish from other data/analytics skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that provides domain-specific knowledge about RevenueCat's MCP tools and dashboard URL construction that Claude would not otherwise know. Its main strengths are the concrete URL templates, parameter tables, and worked examples. Weaknesses include the lack of validation/error-handling steps in the workflow and the monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Add validation checkpoints: what to check after calling get-chart-data (e.g., verify non-empty response, check for error codes), and how to verify a constructed dashboard URL is valid before presenting it.
Consider splitting the URL construction reference (parameter tables, encoding rules, examples) into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and provides domain-specific knowledge Claude wouldn't have (RevenueCat MCP tools, URL format, parameter mapping). However, the 'Interpreting metrics' section includes some general subscription business concepts (acquisition, conversion, retention, reactivation definitions) that are somewhat verbose and could be tightened. The URL construction examples are appropriately detailed since they encode non-obvious formatting rules. | 2 / 3 |
Actionability | The skill provides highly concrete, copy-paste ready URL templates, exact parameter formats with encoding details, specific tool names to call, complete tables mapping API to dashboard parameters, and worked examples showing how to construct links from user requests. The guidance is specific and executable. | 3 / 3 |
Workflow Clarity | The skill has a clear sequence for constructing dashboard links (6-step process) and a general strategy for chart data retrieval ('start with larger resolution, then narrow down'). However, there are no validation checkpoints — no guidance on what to do if the MCP tools return errors, if the project ID is invalid, or how to verify the constructed URL is correct before presenting it to the user. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's a fairly long monolithic file (~150 lines) with no references to supporting files. The detailed URL construction rules, parameter tables, and metric interpretation guidance could be split into separate reference files, with the SKILL.md serving as a concise overview. However, since no bundle files exist, this is somewhat expected. | 2 / 3 |
Total | 9 / 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.