revenuecat
Used for all interaction with RevenueCat not covered by a different skill
32
14%
Does it follow best practices?
Impact
38%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./revenuecat/skills/revenuecat/SKILL.mdEvaluation results
20%
Backend Integration Guide for Subscription Management
MCP server usage for RevenueCat interactions
MCP server named
0%
0%
MCP for subscription checks
0%
0%
MCP for entitlements
0%
0%
No SDK as primary
100%
100%
No direct REST API
0%
0%
No manual auth setup
0%
0%
Docs URL referenced
100%
100%
Customer history via MCP
0%
0%
55%
RevenueCat Webhooks Reference Guide
RevenueCat docs fetched using .md URL suffix
Sources section present
100%
100%
Docs domain in sources
100%
100%
.md suffix used
0%
0%
.md URL from docs domain
0%
0%
Event types listed
100%
100%
Payload fields described
100%
100%
40%
10%RevenueCat Entitlements and Offerings Configuration Plan
MCP + docs URL (.md) for entitlement design
MCP server for lookups
0%
0%
MCP server named explicitly
0%
0%
No SDK as primary runtime tool
0%
100%
Docs domain in sources
100%
100%
.md suffix in source URL
0%
0%
Entitlements concept described
100%
100%
Offerings concept described
100%
100%
- Repository
- RevenueCat/rc-claude-code-plugin
- Commit
407e465
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.