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.

82

3.84x
Quality

Does it follow best practices?

Impact

100%

3.84x

Average score across 1 eval scenario

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A tight, highly actionable multi-step bootstrap workflow with exact tool names and parameters. The only gap is the absence of explicit per-step validation checkpoints between the nine creation steps, which caps workflow clarity.

Suggestions

Add lightweight validation checkpoints between creation steps (e.g., 'confirm project_id was returned before creating apps'; 'verify each product/entitlement was created before attaching') to lift workflow clarity to 3.

Make the error-handling loop step-aware — name which step's failure maps to which likely fix (e.g., duplicate bundle ID at create-app) rather than only generic guidance.

Clarify the store-credentials dependency: note that App Store Connect / Play Console products must exist (or be stubbed via test_store) before attach-products calls succeed.

DimensionReasoningScore

Conciseness

Lean and assumes competence — no explanations of what RevenueCat or IAP are; each line names a tool or action. The summary template is a concrete output spec, not padded prose.

3 / 3

Actionability

Names exact MCP tools (create-project, create-app, create-product, attach-products-to-entitlement, etc.) with concrete parameters (type: app_store|play_store|test_store|rc_billing, lookup_key "default", $rc_monthly/$rc_annual). Copy-paste ready, not pseudocode.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Phase 1–3, ordered 1–9 with "dependencies matter") plus a reactive error-handling loop, but there are no explicit per-step validation checkpoints for this batch creation workflow, capping clarity at 2 per the batch-operations guideline.

2 / 3

Progressive Disclosure

Single cohesive, interdependent workflow organized into clear sections (Discovery / Create Resources / Summary / Error Handling) with no nested references and no content that would benefit from splitting into separate files.

3 / 3

Total

11

/

12

Passed

Description

100%

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 description: third-person voice, concrete capabilities, explicit "Use when" triggers covering natural phrasings, and a clearly distinct niche. No over-claims or padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "creates apps, products, entitlements, offerings, and packages in the correct order" — enumerating five specific resource types rather than vague language.

3 / 3

Completeness

Explicitly answers both what (set up a complete project; creates apps/products/entitlements/offerings/packages) and when via a clear "Use when the user wants to..." clause with multiple triggers.

3 / 3

Trigger Term Quality

Covers natural terms users would say — "create a new RevenueCat project", "configure in-app purchases", "set up subscriptions", "monetization", "IAP infrastructure" — across iOS/Android/Web.

3 / 3

Distinctiveness Conflict Risk

RevenueCat is a specific niche with distinct triggers ("RevenueCat project", "IAP infrastructure"), making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

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.