CtrlK
BlogDocsLog inGet started
Tessl Logo

rc-revenuecat-vs-raw-billing

Use this skill to decide whether to use RevenueCat or raw Google Play Billing on Android. Provides a side by side reference of what RevenueCat handles versus what remains your responsibility at both client and backend layers.

66

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, lean decision reference that routes the reader from intent to a concrete recommendation via tables and a heuristic. It is actionable and clearly sequenced for a comparison skill, with only minor room to tighten prose and add explicit pre-action checkpoints.

Suggestions

Tighten the Phase 0 intent paragraph and the Phase 1 prose, since the bucket table and the typical-questions list already convey the same intent more concisely.

Add an explicit checkpoint in Phase 3 (e.g. 'confirm every requirement maps to a row before committing to a path') to strengthen the decision workflow's validation step.

Optionally surface one or two concrete raw-PBL API calls for the deferral/revocation escape hatches so the 'keep a raw PBL path' guidance is directly executable.

DimensionReasoningScore

Conciseness

The body is largely lean, using compact comparison tables and a terse quick-gate block, with only minor prose in Phase 0/Phase 1 that rephrases the intent and could be trimmed slightly.

4 / 5

Actionability

Provides concrete, row-by-row mappings of concerns to who handles them plus a numbered recommendation heuristic and a copy-ready quick gate; for a decision skill this is actionable guidance with only minor gaps (no explicit API call examples for the raw-PBL escape hatches).

4 / 5

Workflow Clarity

A clear Phase 0-3 sequence with a bucket-routing table in Phase 1 and decision rules in Phase 3; this is a decision workflow (not destructive/batch) so the validation cap does not apply, but it lacks explicit checkpoints confirming the chosen path before acting.

4 / 5

Progressive Disclosure

Well-organized into labeled phases/sections with a single one-level-deep external reference link at the end and no nested references; the inline comparison tables are the core content and appropriately belong in SKILL.md, with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

87%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 third-person, concise, and cleanly answers both what the skill does and when to use it, with a distinct niche. It is slightly light on keyword synonyms and full enumeration of compared concerns, but otherwise strong.

DimensionReasoningScore

Specificity

Names concrete actions ('decide whether to use RevenueCat or raw Google Play Billing', 'side by side reference of what RevenueCat handles versus what remains your responsibility at both client and backend layers') with specific layer coverage, though it stops short of enumerating the full set of compared concerns.

4 / 5

Completeness

Explicitly answers both what ('Provides a side by side reference of what RevenueCat handles versus what remains your responsibility') and when ('Use this skill to decide whether to use RevenueCat or raw Google Play Billing on Android') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes the natural terms a user would say ('RevenueCat', 'raw Google Play Billing', 'Android') but lacks common synonyms or variations like 'in-app purchases', 'subscriptions', or 'Play Billing Library'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (RevenueCat vs raw PBL comparison on Android) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
RevenueCat/ai-toolkit
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.