CtrlK
BlogDocsLog inGet started
Tessl Logo

rc-error-handling

Use this skill when handling errors from the RevenueCat Android SDK. Covers PurchasesError, the PurchasesErrorCode enum, the userCancelled flag on PurchasesTransactionException, and the recommended UI response per code.

71

Quality

88%

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

90%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 focused, executable error-handling skill with lean code and decision tables and a clear phased workflow plus checklist. The only gap is the absence of a true validate/retry feedback loop and any internal content split.

DimensionReasoningScore

Conciseness

Lean phased structure (Understand/Plan/Execute) with no padding about concepts Claude already knows; every line is RevenueCat-specific (types, flags, decision tables, code) and earns its place.

5 / 5

Actionability

Three copy-paste-ready Kotlin snippets (purchase catch, non-purchase catch, userFacingMessage mapping) plus two decision tables give fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Clear Understand→Plan→Execute sequence with a closing Checklist checkpoint and explicit decision guidance, but it is a review checklist rather than a true validate→fix→retry feedback loop, so it sits just below a 5.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clearly signaled one-level-deep external reference (the 'Full chapter' link) and no nested references, though all content is inline with no file split to demonstrate appropriate separation.

4 / 5

Total

18

/

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.

A strong description that explicitly states both what it covers and when to use it, anchored to a specific SDK and concrete error types. Minor room to broaden trigger synonyms (purchase failed, IAP).

DimensionReasoningScore

Specificity

Names the domain (RevenueCat Android SDK errors) and several concrete capabilities ('PurchasesError, the PurchasesErrorCode enum, the userCancelled flag on PurchasesTransactionException, and the recommended UI response per code') — more than 1-2 actions but not the multi-verb comprehensiveness of a 5.

4 / 5

Completeness

Explicitly answers both 'what' (covers PurchasesError, the enum, the userCancelled flag, per-code UI response) and 'when' ('Use this skill when handling errors from the RevenueCat Android SDK') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('RevenueCat Android SDK', 'PurchasesError', 'PurchasesErrorCode') with good coverage, but omits common synonyms a user might actually utter like 'purchase failed', 'IAP', or 'in-app purchase error'.

4 / 5

Distinctiveness Conflict Risk

The RevenueCat Android SDK + PurchasesError-code niche is specific with distinct triggers and minimal overlap risk against 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.