CtrlK
BlogDocsLog inGet started
Tessl Logo

create-revenuecat-project

Set up a complete RevenueCat project from scratch — creates apps, products, entitlements, offerings, and packages in the correct order. Use when the user wants to create a new RevenueCat project, configure in-app purchases, set up subscriptions or monetization, or bootstrap IAP infrastructure for iOS, Android, or Web.

81

1.06x
Quality

82%

Does it follow best practices?

Impact

98%

1.06x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A clearly sequenced, actionable bootstrap guide with good structure and concrete tool/command names. Its main weakness is the absence of explicit validation checkpoints in a batch-creation workflow, capped per the rubric.

Suggestions

Add explicit validation checkpoints between Phase 2 steps: verify a project_id was returned before creating apps, and confirm each app/product exists before attaching entitlements or packages.

Replace the generic 'continue with remaining steps if possible' error guidance with dependency-aware rules so a failed prerequisite step halts dependent steps rather than silently proceeding.

Add a final verification step in Phase 3 confirming the 'default' offering is marked current and every product is attached to its package/entitlement before declaring setup complete.

DimensionReasoningScore

Conciseness

Largely lean and tool-focused without explaining concepts Claude already knows, with minor trim opportunities (the opening line restates the description; the summary template is useful but long).

4 / 5

Actionability

Names concrete MCP tools and equivalent `rc` commands per step plus a concrete summary template, but omits required parameters/field signatures for each call, leaving minor gaps.

4 / 5

Workflow Clarity

Steps are explicitly ordered 1–9 with a dependency note, but validation checkpoints are absent (only a reactive error section that says "continue with remaining steps if possible"); for a batch creation workflow the missing validation caps this at 3.

3 / 5

Progressive Disclosure

Well organized into Phase 1/2/3 and Error Handling sections with clearly signaled cross-skill references (revenuecat-cli, /rc:create-app); no bundle files exist and content is appropriately self-contained, with minor organization gaps in Phase 2's mixed prose/tool listings.

4 / 5

Total

15

/

20

Passed

Description

96%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.

A strong, well-structured description that clearly states capability, sequencing, and explicit use-when triggers with good synonym coverage. The only minor risk is overlap on generic monetization/IAP phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "creates apps, products, entitlements, offerings, and packages in the correct order" — covering the full RevenueCat resource model comprehensively.

5 / 5

Completeness

Explicitly answers both what (the resources created, in order) and when ("Use when the user wants to create a new RevenueCat project, configure in-app purchases, set up subscriptions or monetization...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural user terms with synonyms: "RevenueCat project", "in-app purchases", "IAP infrastructure", "subscriptions", "monetization", and platform names iOS/Android/Web.

5 / 5

Distinctiveness Conflict Risk

Clearly RevenueCat-scoped with a distinct niche, but the broad "configure in-app purchases / set up subscriptions or monetization" triggers carry minor overlap risk with a generic IAP/monetization skill.

4 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RevenueCat/rc-claude-code-plugin
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.