Name: revenuecat-status
Rating: 62.4 (1 reviews)
Author: RevenueCat

revenuecat-status

Get a quick overview of your RevenueCat project configuration including apps, products, entitlements, offerings, and webhooks.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

76%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 highly actionable, naming exact MCP tools and a concrete output template within a clear five-step sequence. Its main weakness is the lack of validation/error-handling checkpoints in the batch gather step, which caps workflow clarity, plus minor redundancy between the frontmatter and the Description section.

Suggestions

Add a validation checkpoint in the gather step: if any list-* tool call fails or returns empty, note it in the report rather than silently omitting the section.

Remove the redundant ## Description section (or the repeated case-insensitive partial-match note) to tighten token efficiency.

Before presenting the summary, verify counts were collected for every project so partial failures surface explicitly.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's familiarity with MCP, naming exact tools and a compact output template; minor redundancy (the ## Description section restates the frontmatter, and case-insensitive partial matching is stated twice) keeps it just below 5.	4 / 5
Actionability	Names all six exact MCP tools (list-projects, list-apps, list-products, list-entitlements, list-offerings, list-webhook-integrations), specifies filtering behavior, and provides a complete copy-paste-ready output template plus concrete issue checks — fully actionable for an instruction-only MCP skill.	5 / 5
Workflow Clarity	The five-step sequence is clearly ordered, but the batch-gather step (iterating projects x five tools) has no validation checkpoint for tool-call failures or empty results; per the rubric's batch-operation cap, a batch workflow without validation cannot score above 3.	3 / 5
Progressive Disclosure	Well-organized into clear sections (Description, Usage, Arguments, Instructions, Highlight Issues) with no nested references and easy navigation; held below 5 because the skill exceeds the ~50-line simple-skill threshold and the Description section duplicates the frontmatter rather than being trimmed.	4 / 5
	Total	16 / 20 Passed

Description

70%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 is specific, domain-distinct, and lists the key configuration entities comprehensively, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness. Adding a trigger clause would lift the strongest remaining weakness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for a summary or status of their RevenueCat project, or wants to review apps, products, entitlements, offerings, or webhooks.'

Add natural synonyms a user might say ('subscriptions', 'in-app purchases', 'paywall configuration') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the RevenueCat domain and enumerates five concrete configuration components (apps, products, entitlements, offerings, webhooks), giving comprehensive coverage; held below 5 because only a single action verb ('Get a quick overview') is used rather than multiple distinct actions.	4 / 5
Completeness	The 'what' is clearly stated ('Get a quick overview of your RevenueCat project configuration including...') but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Good keyword coverage with domain-specific terms a user would say ('RevenueCat', 'apps', 'products', 'entitlements', 'offerings', 'webhooks', 'overview'); not 5 because it lacks synonyms (e.g. 'subscriptions', 'in-app purchases') and any natural trigger phrasing variations.	4 / 5
Distinctiveness Conflict Risk	Targets a clear, narrow niche (RevenueCat project configuration) with entity names specific to that platform, making it highly distinguishable from other skills with minimal conflict risk.	5 / 5
	Total	16 / 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-status/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.