CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

revenuecat-experiment-analysis

Use when the user asks to analyze or understand a RevenueCat experiment or its results.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./revenuecat/skills/revenuecat-experiment-analysis/SKILL.md
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 strong, tightly written operational workflow: concrete tool invocations with parameters, explicit sequencing and skip conditions, and genuinely non-obvious domain knowledge (status lifecycles, price-data staleness, published-vs-draft paywall versions). All four dimensions land at 4 rather than 5 only for small polish items — filler phrases, template placeholders, and a slightly overlong inline caveat.

DimensionReasoningScore

Conciseness

The body is a lean, step-scoped instruction set — tool names, parameters, and domain facts Claude cannot be assumed to know (status semantics like "paused means... up to 400 days", USD-only indicative pricing, stale catalog fields). Only minor padding keeps it from anchor 5: filler like "Use your best judgment", a repeated skip-warning for Step 3, and the introductory paragraph restating the ordering rules twice.

4 / 5

Actionability

Nearly every step gives an executable tool call with exact parameters and values (e.g. `expand: offering.package.product.indicative_price and offering.paywall`, `version: "published"`, the four named chart_name values). Minor gaps hold it below anchor 5: Step 3 uses template placeholders like `start_date: {experiment_start_date}`, and Step 5 ("Use your best judgment") is inherently interpretive without concrete interpretation heuristics.

4 / 5

Workflow Clarity

The 6-step sequence is explicit with ordering rules, a "[DO NOT SKIP]" marker, precise conditional skips (skip a step only if the information is already in hand; skip 2b when every paywall_id is null), and a feedback loop (a disputed claim must be re-verified via `get-product-store-state` instead of pushed to the user). It is read-only analysis so the destructive-operation validation cap does not apply; it sits just under anchor 5, whose richer checklist/error-recovery structure it doesn't fully match.

4 / 5

Progressive Disclosure

The skill is a single well-organized file with per-step headers, and its cross-references (`revenuecat-store-state`, `revenuecat-dashboard-links`) are clearly signaled one level deep. It is not a 5 under the rubric's own exception (that is reserved for under-50-line skills with no external references): at ~80 lines, some inline detail — the indicative-price caveat paragraph in Step 2a — could live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

48%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 has an explicit, well-formed 'Use when...' trigger and a distinct niche, but it is thin: it never concretely states what the skill does, and its trigger vocabulary omits the most natural synonym ("A/B test"). It clearly beats generic one-liners like "Helps with documents" yet falls short of the good examples that pair concrete capabilities with rich trigger phrases.

Suggestions

State concrete capabilities after the trigger, e.g. "Fetches experiment setup, paywalls, supporting chart data, and results for a RevenueCat experiment, then interprets variant performance. Use when the user asks to analyze or understand a RevenueCat experiment, A/B test, or its results."

Add natural trigger synonyms users would actually say — "A/B test", "test results", "experiment performance" — to improve both trigger term coverage and completeness of the 'what'.

DimensionReasoningScore

Specificity

The description names the domain ("a RevenueCat experiment or its results") but its only actions are the generic verbs "analyze or understand" — it never states concrete capabilities like pulling chart data, comparing offerings, or rendering paywall screenshots. This matches the anchor 'Names the domain but actions are minimal or generic' rather than anchor 3, which requires at least 1-2 concrete actions.

2 / 5

Completeness

The "when" is explicit ("Use when the user asks to analyze or understand a RevenueCat experiment or its results"), but the "what" is vague — "analyze or understand" merely restates the trigger instead of describing what the skill does (fetch setup, chart data, and results, then interpret them). It falls short of anchor 4, which requires a substantive 'what' paired with the 'when', so it lands at anchor 3's level with a weak 'what' rather than a weak 'when'.

3 / 5

Trigger Term Quality

"RevenueCat", "experiment", "results", and "analyze" are natural terms a user would say, but common variations are missing — most notably "A/B test" (the everyday synonym users use for experiments) as well as "test results" or "experiment performance". It sits between anchor 3 ('some relevant keywords but missing common variations') and anchor 4, and the missing 'A/B test' synonym keeps it at 3.

3 / 5

Distinctiveness Conflict Risk

"RevenueCat experiment" is a clear niche with distinct triggers — a user mentioning RevenueCat experiments is unambiguously routed here. It is not a 5 because it could overlap slightly with sibling RevenueCat skills (e.g. store-state or dashboard-links skills referenced in the body) for generic "RevenueCat results" phrasing, matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills').

4 / 5

Total

12

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

RevenueCat/ai-toolkit

Path

revenuecat/skills/revenuecat-experiment-analysis/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.