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

revenuecat-status

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

The body is a well-structured, actionable read-only status workflow with specific tool calls, clear conditional sequencing, and a built-in issue-highlighting quality check; its only weakness is minor redundancy where the Description section restates the frontmatter.

Suggestions

Remove or condense the 'Description' section since it duplicates the frontmatter description, relying on the Instructions to convey the same information more concretely.

Tighten the output template by collapsing decorative formatting where it does not aid comprehension.

Dimension	Reasoning	Score
Conciseness	The instructions are lean, name specific MCP tools directly, and assume Claude's competence without explaining what RevenueCat or entitlements are, but the 'Description' section restates the frontmatter and the output template is somewhat elaborate, so it is mostly rather than perfectly efficient.	2 / 3
Actionability	It names exact tools (list-projects, list-apps, list-products, list-entitlements, list-offerings, list-webhook-integrations), specifies $ARGUMENTS parsing with case-insensitive partial matching, and provides a copy-ready formatted output template, giving fully executable guidance.	3 / 3
Workflow Clarity	Five clearly numbered, sequenced steps include conditional branches (filter/no-match/all-projects handling) and a built-in quality-check step (Highlight Issues) that catches misconfigurations; since this is a read-only query rather than a destructive or batch-mutating operation, no validation feedback-loop cap applies.	3 / 3
Progressive Disclosure	The skill is self-contained with no external bundle files present, and content is well-organized into clearly headed sections (Description, Usage, Instructions) with no nested references or monolithic wall of text, satisfying the well-organized-sections criterion.	3 / 3
	Total	11 / 12 Passed

Description

47%

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 distinctive and names the RevenueCat domain with concrete sub-components, but it is written in second-person voice and omits an explicit 'Use when...' trigger clause, capping both specificity and completeness.

Suggestions

Rewrite in third-person voice (e.g., 'Summarizes a RevenueCat project configuration...') to avoid the specificity penalty.

Add an explicit trigger clause such as 'Use when checking RevenueCat project setup or auditing entitlements and offerings.'

Lead with a concrete action verb and consider framing multiple distinct actions (e.g., 'Summarizes apps, products, entitlements, offerings, and webhooks for a RevenueCat project') to strengthen specificity.

Dimension	Reasoning	Score
Specificity	The description names the RevenueCat domain and enumerates concrete components (apps, products, entitlements, offerings, webhooks), which would anchor at 2, but it uses second-person voice ('your RevenueCat project configuration'), which the rubric penalizes by reducing specificity by 1, flooring it at the scale minimum.	1 / 3
Completeness	It clearly answers 'what' the skill does (overview of project configuration and listed components), but provides no 'Use when...' or equivalent explicit 'when' trigger guidance, which the rubric caps at 2.	2 / 3
Trigger Term Quality	It includes relevant domain keywords a user would say ('RevenueCat', 'project configuration', 'apps', 'products', 'entitlements', 'offerings', 'webhooks'), but lacks an explicit trigger framing or common variations, so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	'RevenueCat project configuration' with its specific component list is a narrow, well-defined niche with distinct triggers, making it unlikely to conflict with other skills.	3 / 3
	Total	8 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: RevenueCat/rc-claude-code-plugin
Commit: 5cb348c

Reviewed: 4 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.