CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rc-catalog-management

Use this skill when managing the Android product catalog through the Play Console and the RevenueCat dashboard. Covers the two sided catalog flow (create in Play Console, import or map in RevenueCat), entitlement and offering maintenance, and why you do not call the Google Play Developer API directly.

Quality

85%

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

88%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 tightly written, actionable runbook: phased workflow, exact click-paths, executable Kotlin snippets, a verification checklist, and concrete error-recovery guidance. Its only weaknesses are minor: a few trimmable lines and a thin reference layer that keeps all detail inline.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: compact tables, minimal Kotlin snippets, and no re-explanation of concepts Claude already knows. A few lines could be trimmed (e.g., 'Read this phase before you touch anything', restating the no-direct-API constraint already in the description), so it is not a 5.

4 / 5

Actionability

Fully executable guidance: exact UI navigation paths ('Play Console -> Monetize -> Products -> Subscriptions'), copy-paste-ready Kotlin for entitlement checks and offerings, concrete package identifiers ($rc_monthly, $rc_annual), and a specific error signature (PurchasesException with PurchasesErrorCode.ConfigurationError). The common cases (add product, import, wire into offering, targeting) are each covered with specific steps.

5 / 5

Workflow Clarity

Clear phased sequence (Understand, Plan, Execute, Verify) with an explicit verification checklist covering all six checkpoints and an error-recovery loop: 'If awaitOfferings() returns null...' enumerates causes and fixes, including the exact exception and error code to check. Well above the anchor requiring explicit validation steps and feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is well-organized with clear section headers and a single, clearly signaled one-level-deep reference (the 'Full chapter' external link). Not a 5 because the skill exceeds 50 lines with all content inlined and no reference structure for the more detailed material (e.g., REST API endpoints or dashboard deep-dives), which is a minor organization gap rather than a clear split.

4 / 5

Total

18

/

20

Passed

Description

78%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 specific, uses an explicit 'Use this skill when...' trigger clause, and carves out a distinct niche around Play Console and RevenueCat catalog management. Its main weakness is trigger-term breadth: it omits natural synonyms like 'subscriptions', 'in-app purchases', and 'paywall' that users might say instead.

DimensionReasoningScore

Specificity

Names concrete actions ('create in Play Console, import or map in RevenueCat', 'entitlement and offering maintenance') tied to specific surfaces. Not a 5 because coverage has gaps (no mention of base plans, offers, prices, or targeting/placements); not a 3 because it lists several specific actions rather than just 1-2.

4 / 5

Completeness

Has both a clear 'what' (two-sided catalog flow, entitlement/offering maintenance, why not to call the Play Developer API) and an explicit 'when' ('Use this skill when managing the Android product catalog through the Play Console and the RevenueCat dashboard'). Not a 5 because the when-clause relies on one trigger scenario rather than varied concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes natural terms users would say: 'Android product catalog', 'Play Console', 'RevenueCat', 'entitlement', 'offering'. Missing a few common variations such as 'subscriptions', 'in-app purchases', or 'paywall', so it falls just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche at the intersection of Play Console and RevenueCat catalog management; the named tools and concepts are unlikely to collide with unrelated skills. Explicitly distinguishes itself from direct Google Play Developer API usage.

5 / 5

Total

17

/

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

Path

revenuecat-play-billing/skills/rc-catalog-management/SKILL.md

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.