Repository navigation
fix(skills): correct experiment, audience, and dashboard-link guidance - #63
Merged
Merged
Conversation
- experiment-analysis: valid exposure_status values (exposed / not_exposed; omit for all enrolled), screenshot the published paywall, treat catalog trial/price fields as possibly stale, call "Exposed customers" "Paywall viewers", add the missing Step 6, fix the frontmatter name. - experiments: duplicate treatments from the published paywall; finish the truncated custom-paywall sentence. - audiences: inspect segments with read-only preview-audience (sorting, stats, is_approximate) instead of saving one with create-audience. - dashboard-links / audiences: link the "Dashboard URL for this result" the MCP server returns; hand-built routes are the fallback. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jefago
approved these changes
Sep 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Some toolkit skills tell agents to make calls the MCP server rejects, or to read the wrong data. The Rico versions of the same skills have been fixed since these were ported. This PR brings those fixes over, plus a few toolkit bugs.
What changed
revenuecat-experiment-analysisexposure_status: valid values areexposedandnot_exposed; omit the parameter to get all enrolled customers. The old text listedenrolled, which the MCP schema doesn't accept, and restricted the filter to existing-customer experiments.render-paywall-screenshotnow passesversion: "published", and is skipped when every offering has a custom paywall. The tool defaults to the draft, so the agent could analyze edits customers never saw.indicative_price,trial_durationanddurationcan be stale, so confirm them withget-product-store-statebefore stating them as fact or calling one a confound. If the user disputes a claim, the agent checks it itself instead of asking them to.Exposed customersmetric "Paywall viewers".namechanged fromexperiment-analysistorevenuecat-experiment-analysisto match the folder. It was the only skill where the two differed.revenuecat-experimentssource_paywall_version: published, and usedraftonly when the source was never published. Otherwise a treatment copies unpublished draft edits.paywall_id: null), the paywall change has to happen in the app.revenuecat-audiencespreview-audiencewithbody.rules. The old flow saved an audience withcreate-audience, after a confirmation, just to look at a sample.sort_by/sort_direction, for exampletotal_spent+descfor the top spenders.stats, not the sample size, and say "about N" whenis_approximateis true.revenuecat-dashboard-links/revenuecat-audiencesDashboard URL for this resultline (89 API tools, pluspreview-audienceforbody.rules). Link that URL; the hand-built routes are now the fallback for the CLI, charts, and pages not fetched through a tool.No version bump or CHANGELOG entry. Those go in one release PR together with #62 and the store-state / charts / troubleshoot PR, so the plugin ships once.
For reviewers
preview-audienceand the MCP dashboard-URL lines are confirmed live on the production MCP server.Testing
Only skill text changed. I checked every parameter named above (
exposure_statusenum,source_paywall_version, therender-paywall-screenshotversiondefault, thepreview-audiencesort and stats fields, which tools setdashboardLink) against the MCP server's generated schemas and tool mapping.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only skill text changes; no runtime code, auth, or data paths affected.
Overview
Updates four RevenueCat agent skills so guidance matches current MCP behavior and avoids invalid tool calls.
Audiences (
revenuecat-audiences): Segment inspection uses read-onlypreview-audienceinstead of creating saved audiences to peek at a sample. Documentssort_by/sort_direction(e.g. top spenders),statsfor counts (with approximate wording), and preferring the "Dashboard URL for this result" line over hand-built filter URLs.Dashboard links (
revenuecat-dashboard-links): Agents should link MCP-returned dashboard URLs first; manual route tables are fallback only (CLI, charts, unfetched pages).Experiment analysis (
revenuecat-experiment-analysis): Renames skill torevenuecat-experiment-analysis. Fixesexposure_statustoexposed/not_exposed(omit for all enrolled). Paywall screenshots useversion: "published"; skip when all variants are custom paywalls. Warns that catalog prices/trials may be stale—verify withget-product-store-state. Adds parallel calls within steps, Step 6 reporting with links, and "Paywall viewers" wording for exposed-customers metric.Experiments setup (
revenuecat-experiments):duplicate-offeringshould passsource_paywall_version: publishedwhen copying treatment paywalls; clarifies thatpaywall_id: nullmeans paywall changes happen in the app, not RevenueCat.Reviewed by Cursor Bugbot for commit 3d9e40b. Bugbot is set up for automated code reviews on this repo. Configure here.