Name: revenuecat
Rating: 58.07 (1 reviews)
Author: RevenueCat

Blog Docs Log in Get started

revenuecat

Used for all interaction with RevenueCat not covered by a different skill

1.00x

Quality

59%

Does it follow best practices?

Impact

50%

1.00x

Average score across 1 eval scenario

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

78%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 a tight, well-disclosed routing overview that appropriately points to the CLI skill and docs, but it stops short of giving executable commands or concrete examples, leaving actionability incomplete.

Suggestions

Add one or two concrete example commands or MCP tool invocations for the most common RevenueCat tasks.

Give brief guidance on when to use the MCP server versus the `rc` CLI so the tool choice is unambiguous.

Optionally show a worked example of fetching a docs page via the `.md` URL trick to make that tip immediately usable.

Dimension	Reasoning	Score
Conciseness	The body is two lean sentences with no padding and no explanation of concepts Claude already knows; every token (the tool choice, the docs URL, the `.md` URL trick) earns its place.	5 / 5
Actionability	It names concrete tools (MCP server or `rc` CLI) and gives one executable tip (append `.md` to a docs URL), but provides no actual commands or code and defers specifics to another skill and external docs, leaving key details missing.	3 / 5
Workflow Clarity	As a simple routing skill the single action (use the RevenueCat MCP server or `rc` CLI) is reasonably clear with no destructive/batch steps requiring validation, though offering two tools without guidance on when to pick which is a minor gap.	4 / 5
Progressive Disclosure	The body is a concise overview that delegates detail via clearly signaled, one-level-deep references (the `revenuecat-cli` skill and the docs URL) with no bundle files needed, matching the well-structured overview anchor.	5 / 5
	Total	17 / 20 Passed

Description

40%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 appropriately scoped to a distinct niche (RevenueCat) with explicit conflict-disambiguation, but it is vague on capabilities and lacks any trigger/when guidance, capping its completeness and specificity low.

Suggestions

Add concrete actions (e.g., 'manage subscriptions, entitlements, offerings, and customer purchase history') instead of 'all interaction'.

Add an explicit 'Use when...' trigger clause naming natural user phrases (e.g., 'Use when the user works with RevenueCat, in-app purchases, paywalls, or subscription entitlements').

Include synonyms/file extensions or related terms a user might actually say to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("RevenueCat") but uses the generic phrase "all interaction" with no concrete actions named, matching the anchor that names a domain with minimal/generic actions.	2 / 5
Completeness	It gives a vague "what" ("all interaction with RevenueCat") and no explicit "Use when..." trigger clause; "not covered by a different skill" is disambiguation rather than a when-condition, matching the vague-what/no-when anchor.	2 / 5
Trigger Term Quality	"RevenueCat" is a relevant natural keyword a user would say, but no synonyms or related terms (subscriptions, in-app purchases, paywalls, IAP) are included, matching the anchor with some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	RevenueCat is a clear niche and the phrase "not covered by a different skill" explicitly defers to more specific skills, reducing conflict risk, though "all interaction" keeps minor overlap with the referenced `revenuecat-cli` skill.	4 / 5
	Total	11 / 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/SKILL.md
Commit: b9b77b1

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.