Skills

RevenueHog ships four Claude skills. Each is a SKILL.md that teaches Claude a RevenueHog workflow. They are installed with the Claude Code plugin or copied into .claude/skills/. Each stands alone, and they cross-reference each other.

revenuehog-insightsCopy Anchor Link

Queries the MCP server to answer questions about revenue, subscriptions, attribution, experiments, reviews, feedback and Apple payouts.

Triggers: "how is my revenue doing", "how is my MRR doing", "which app has the best ROAS", "is my paywall test a winner", "why did revenue drop", "what are users saying in reviews", "show me the bug reports", "any feature requests", "when is my next Apple payment", "create a RevenueHog API key", "send my feedback forms to RevenueHog".

What it teaches Claude:

• Use rh_query first for anything countable, and the specialist tools (rh_reviews, rh_feedback, rh_experiment_results, rh_payouts) only when the grid cannot express the question.
• Prefer the smallest query: one totals row over a breakdown, a ranked limit over every row.
• Call rh_meta with topic schema when unsure a measure exists, and freshness before asserting a number.
• Always state the window and that money is USD.
• Treat a new API key secret as shown once. Prefer a workspace-wide key (no appId) to route every app's feedback.
• If the tools are not available, tell the user to connect the server and stop. Never invent numbers.

See Query recipes for the kind of calls it makes.

revenuehog-integrationCopy Anchor Link

Wires identify, attribute, signpost events and server-driven paywall SKUs into an app against the /api/sdk/v1 endpoints, so purchases link to your own user IDs and onboarding steps feed the funnel.

Triggers: "add RevenueHog to this app", "integrate RevenueHog", "wire up RevenueHog attribution", "link purchases to my users", "instrument onboarding steps", "make my paywall products server-driven".

There is no API key: iOS apps authenticate with App Attest. Revenue, MRR, churn, the live feed, customers and alerts need no SDK at all; they run server-side from your App Store Connect key. See SDKs.

revenuehog-experimentsCopy Anchor Link

Signs a terminal in to the dashboard and runs paywall SKU A/B tests: set the products each entitlement offers, create and start experiments, reweight or pause them, read results with Wilson intervals and sample ratio mismatch health, and conclude by promoting a winner.

Triggers: "set up an A/B test for my paywall", "test annual first against monthly first", "which paywall variant is winning", "change what my paywall offers", "log in to RevenueHog".

Sign-inCopy Anchor Link

The skill uses the OAuth 2.0 device authorization grant through its helper script:

scripts/rh.sh login     # prints a URL and an 8-character code (XXXX-XXXX)
scripts/rh.sh whoami
scripts/rh.sh apps      # appId  bundleId  name
scripts/rh.sh logout

You approve the code at /device in a browser where you are signed in to RevenueHog. Codes expire after 15 minutes. The resulting session token is cached at ~/.revenuehog/token.json (mode 600) and expires like a normal session, about a week. It is not an API key: never put it in a repository, CI secret or env file. Set RH_API to point the script at another server.

The skill does not create products, set prices, build a paywall UI or decide entitlement. See Experiments.

revenuehog-paywallCopy Anchor Link

Audits an app for every place a paywall decides which products to show, across Swift and StoreKit 2, React Native and Android Play Billing, then rewires each call site to a RevenueHog paywall fetch with a compiled-in fallback, adds the impression beacon, and registers the current lists as entitlement defaults. The paywall's look, purchase flow and entitlement logic stay as they are.

Triggers: "make my paywall server-driven", "find where my paywalls are", "my product ids are hardcoded", "I want to A/B test my paywall offers".

See Paywall.

RelatedCopy Anchor Link