CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

90%

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.

A well-structured, actionable skill body that sequences a multi-step catalog flow with concrete steps, executable Kotlin, and a verification checklist. It is concise and navigable, with only minor prose to trim and no need for deeper file splitting.

DimensionReasoningScore

Conciseness

Largely lean and dense with tables and code, assuming Claude's competence; only minor connective prose such as 'Read this phase before you touch anything.' could be trimmed.

4 / 5

Actionability

Provides concrete UI navigation paths (e.g. 'Play Console -> your app -> Monetize -> Products -> Subscriptions') and copy-paste-ready Kotlin snippets covering the common end-to-end flow.

5 / 5

Workflow Clarity

Clear Phase 1→4 sequence (Understand, Plan, Execute, Verify) with an explicit verification checklist table and an error-recovery note for the null-offering case.

5 / 5

Progressive Disclosure

Well-organized into clear section headers in a single file with one clearly signaled one-level external reference (the full chapter link); no bundle files to split, but content stays inline rather than being distributed.

4 / 5

Total

18

/

20

Passed

Description

92%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, specific description that clearly states the two-surface catalog flow and an explicit 'Use when' trigger, with distinct domain anchors. The only gap is missing synonyms like 'subscriptions' or 'paywall' for fuller trigger coverage.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'create in Play Console, import or map in RevenueCat' and 'entitlement and offering maintenance' — giving comprehensive coverage of the catalog domain.

5 / 5

Completeness

Explicitly answers what ('two sided catalog flow', entitlement/offering maintenance) and when ('Use this skill when managing the Android product catalog through the Play Console and the RevenueCat dashboard') with concrete trigger phrases in third-person voice.

5 / 5

Trigger Term Quality

Strong natural domain terms ('Play Console', 'RevenueCat dashboard', 'entitlement', 'offering') that users would say, but lacks common synonyms such as 'subscriptions', 'in-app purchases', or 'paywall'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Android product catalog management across Play Console and RevenueCat) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

19

/

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.