Index of every page on this site: llms.txt
All skills
segmently-ai avatar

/segmently-cli-paywall-ab-rollout

@f3f9f19
Run it yourself

Segmently CLI scenario wrapper for creating and verifying sandbox Stripe paywall A/B onboarding rollouts. Use when a task needs to create or demonstrate two paywall onboarding variants, publish them, publish an A/B test, probe runtime routing, and return public URLs through the Segmently CLI. Also trigger when Segmently Launch Assistant returns executeWith.skill/owningSkill=segmently-cli-paywall-ab-rollout, especially for sandbox paywall products, paid onboarding offers, and A/B rollout DO flows.

  • 3 files
  • 27.5 KB
  • Updated 5 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/segmently-ai/segmently-support-plugins/segmently-cli-paywall-ab-rollout

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈134 tokens for metadata: the name and description. ≈1.5k when used: this file. ≈85 more on demand in 1 file.

Description uses 6.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈536 characters, or 6.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Segmently CLI Paywall A/B Rollout

Use this skill for the reusable sandbox paywall A/B scenario. It is an automation wrapper around the CLI facade, not a new product API. It supports two rollout modes:

  • funnelManifest: create two new onboarding variants from inline manifests.
  • clonedFunnelVersion: keep an existing source funnel as control, clone the source version into a treatment funnel, mutate one Paywall screen's product list, publish both placements, and publish the A/B test.

Preconditions

  • Run from the installed skill directory or pass the script path explicitly.
  • Confirm the public Segmently CLI is installed and authenticated:
    segmently auth status
  • If the CLI reports auth_required, run segmently auth login --env <env> for the intended environment and retry after segmently auth status --env <env> succeeds.
  • Use a cloned/test funnel and Stripe sandbox/test account unless the user has explicitly approved the target production experiment.
  • Minimum target context for clone-based rollout is: project id, source funnel id, source version/draft id, paywall screen id or confirmation to use the default Paywall screen, treatment product ids or approval to create sandbox products, and explicit approval before publishing A/B traffic.
  • The authenticated CLI identity must include: projects:read,funnels:read,funnels:write,themes:read,themes:write,publish:write,stripe:read,stripe:write.
  • The project must have a connected Stripe sandbox/test account.
  • Prefer an active project theme. If the project has no active theme, run segmently themes list/global/import/set-active first.

Canonical Command

node scripts/run-paywall-ab-rollout.mjs \
  --project <projectId>

Useful options:

--suffix <stable-id>              # deterministic aliases for reruns
--paywall-product-id <id>         # reuse an existing Segmently paywall product
--source-funnel-id <id>           # enable clonedFunnelVersion mode
--source-version-id <id>          # source version to clone
--source-web-placement-alias <a>  # optional source onboarding URL in summary
--paywall-screen-id <id>          # screen key/id to mutate, default Paywall
--clone-name <name>               # treatment funnel name
--clone-version-name <name>       # treatment version name
--treatment-paywall-product-ids <ids>
                                  # comma-separated treatment product ids
--probe-samples <count>           # default 30
--public-base-url <url>           # default comes from CLI env
--output <path>                   # write the final summary JSON

What The Script Does

Default funnelManifest mode:

  1. Ensures a Stripe test-mode paywall product unless --paywall-product-id is supplied.
  2. Builds two inline funnelManifest variants:
    • control: goal -> name -> email -> paywall -> paid success
    • treatment: same variable and paywall contract with different copy
  3. Runs:
    segmently ab-tests rollout apply --publish --probe
  4. Returns the control URL, treatment URL, A/B URL, paywall product id, publication id, and probe results as JSON.

clonedFunnelVersion mode:

  1. Requires --source-funnel-id and --source-version-id.
  2. Ensures one Stripe test-mode treatment paywall product unless --paywall-product-id or --treatment-paywall-product-ids is supplied.
  3. Builds a rollout manifest with:
    • control: existingFunnelVersion from the source funnel/version.
    • treatment: clonedFunnelVersion from the same source funnel/version.
  4. Mutates --paywall-screen-id in the treatment clone through the backend SimplifiedV2ScreenAdapter, preserving the source funnel unchanged.
  5. Publishes the generated control placement, treatment placement, and A/B placement, then probes the public A/B URL.
  6. Returns source editor URL, optional source public URL, control/treatment onboarding URLs, treatment clone editor URL, A/B URL, publication id, and probe results as JSON.

Example clone run:

node scripts/run-paywall-ab-rollout.mjs \
  --project <projectId> \
  --source-funnel-id <funnelId> \
  --source-version-id <versionId> \
  --source-web-placement-alias <existing-source-alias> \
  --paywall-screen-id Paywall \
  --clone-name "Paywall Product Treatment"

Safety Rules

  • The wrapper is sandbox-only for Stripe product creation. It always sends mode: "test" to stripe paywall-product ensure.
  • The wrapper must not print API keys, tokens, refresh tokens, or credentials.
  • Use --paywall-product-id when you need to avoid creating another Stripe product.
  • In clone mode, the source funnel/version is used read-only; the Paywall mutation is applied only to the treatment clone.
  • Do not use this wrapper for production traffic experiments without a separate product rollout review.
  • If runtime probe fails, inspect the JSON output first. The created artifacts are intentionally left in place for debugging and reruns.

Verification

Minimum local smoke:

node --check scripts/run-paywall-ab-rollout.mjs
node scripts/run-paywall-ab-rollout.mjs --help

Full verification against a customer-approved test project:

node scripts/run-paywall-ab-rollout.mjs \
  --project <projectId> \
  --source-funnel-id <funnelId> \
  --source-version-id <versionId> \
  --probe-samples 30 \
  --output checks/paywall-ab-rollout-summary.json

Related CLI Surfaces

  • segmently stripe paywall-product ensure
  • segmently themes list/global/import/set-active
  • segmently ab-tests rollout apply --publish --probe
  • source.type = "existingFunnelVersion"
  • source.type = "clonedFunnelVersion"
  • /api/cli/v1/projects/:projectId/stripe/paywall-products/ensure
  • /api/cli/v1/projects/:projectId/ab-tests/rollout/apply

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at f3f9f19. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 5 months ago

README badge

README badge for segmently-ai/segmently-support-plugins/segmently-cli-paywall-ab-rollout