Conciseness

The body is lean and dense — install fallbacks, auth checks, key-type distinctions, discovery commands, envelope shapes, exit codes, and upload constraints are each stated in a line or two with no concept explanations Claude already knows. Every token earns its place, matching the 5 anchor.

Actionability

Guidance is fully executable throughout: `rc --version`, `npx @revenuecat/cli <command>`, `brew install RevenueCat/tap/rc`, `rc auth status --json`, `rc commands --schemas --json`, exact image/font formats and size limits, and 'Confirm flags with `rc schema media-assets upload`'. Commands are copy-paste ready and cover the common cases, matching the 5 anchor.

Workflow Clarity

'Before the first command' is a clearly numbered setup sequence with explicit validation checks (`rc --version`, `rc auth status --json`), decision branches for failure (npx/brew/npm fallbacks; `RC_API_KEY` for CI), and error-recovery guidance (exit-code table; 'when in doubt use `rc commands --schemas`' for the silent `rc schema apps:create` failure). This matches the 5 anchor's explicit validation and feedback loops.

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, yet is organized into clear, well-labeled sections; cross-references to other skills (`revenuecat-paywall-design`, `revenuecat-dashboard-links`) are clearly signaled inline. Per the rubric's simple-skill note, this earns a 5.

Specificity

Multiple concrete actions are named with exact commands — 'uploading paywall images to the Media Gallery (`rc media-assets upload`)', 'custom paywall fonts (`rc fonts upload`)', plus 'install, authentication, command discovery, and output conventions'. It falls just short of the 5 anchor because the CLI's core catalog operations (products, entitlements, offerings, paywalls) are not named, a minor coverage gap.

Completeness

The 'what' is explicit ('Drive RevenueCat from the terminal with the `rc` CLI... Covers install, authentication, command discovery, and output conventions') and the 'when' is an explicit 'Use for' clause with concrete triggers ('Use for uploading paywall images to the Media Gallery... or custom paywall fonts... MCP has no upload tools for these'). Both are clearly and concretely answered, matching the 5 anchor; the 4 anchor's 'when could be more explicit' does not apply.

Trigger Term Quality

Natural trigger terms are present — 'RevenueCat', 'terminal', 'CLI', 'rc', 'paywall images', 'Media Gallery', 'paywall fonts', 'MCP server', 'CI' — matching what a user would say when needing this skill. A few natural terms are missing (e.g., 'offerings', 'entitlements', 'products'), so it fits the 4 anchor ('good keyword coverage; a few natural terms missing') rather than comprehensive 5.

Distinctiveness Conflict Risk

Clear niche (the `rc` CLI as an alternative to the RevenueCat MCP server) with distinct triggers, and it explicitly disambiguates from MCP ('MCP has no upload tools for these'), so conflict risk is minimal — matching the 5 anchor.