All skills
segmently-ai avatar

/segmently-launch-guide

@330af37

Use this orchestration skill when a customer wants to launch or publish a Segmently web funnel, connect Stripe/Facebook/TikTok/analytics, create paywall products, ask what's left, change a setting, get article/screenshot guidance, or SHOW/DO a supported editor task. It selects evidence and offers TEACH, SHOW, CLI DO, E2E DO, or handoff. It is not the CLI/browser execution owner; for DO delegate to executeWith.skill/owningSkill companion such as segmently-cli-guide, segmently-cli-paywall-ab-rollout, segmently-cli-custom-screen-guide, segmently-cli-image-upload, segmently-cli-articles, playwright-bowser, segmently-test-kit, or claude-design.

  • 251 files
  • 17.1 MB
  • Updated last week
  • GitHub

Use this Skill: https://skilld.dev/gh/segmently-ai/segmently-support-plugins/segmently-launch-guide

This session only. Nothing lands on disk.

referencesproject-status.md

≈683 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Project status — milestones and "what's left"

Before doing anything, understand where the project already is so you only do what's missing. Compose customer-safe CLI reads into a milestone snapshot, then compare it to the goal. All reads are delegated to segmently-cli-guide.

Milestones and the read that observes each

Milestone Read done when
Funnel created funnels list at least one funnel exists
Theme applied themes list (active theme) — or funnels get for a funnel-attached theme the project has an active theme, or the funnel references a source/project theme
Analytics connected analytics settings get a provider is configured
Facebook pixel analytics settings get a Facebook pixel id is set
TikTok pixel analytics settings get a TikTok pixel id is set
Stripe connected stripe account --mode test and stripe account --mode live the requested mode reports connected; sandbox/test connected with live disconnected still means test payments can be prepared while live charges need live Stripe Connect
Paywall products created stripe products at least one product exists
Products attached to paywall funnels export a paywall screen lists products
Sandbox purchase verified test purchase + publish verify a test purchase completed
Web placement configured web-placements list a placement is attached
Attribution configured web-placements list source/metadata mappings exist
Custom domain verified domains verify verification is ready (or default chosen)
Published publish verify the live URL is reachable
Launch verified publish verify the funnel was checked at the chosen depth

Goals and "what's left"

A goal is a set of milestones. Common goals:

  • First-value launch — funnel + theme + screens + publish.
  • Monetized launch — adds Stripe + paywall products + attach + test purchase.
  • Ads-ready paid launch — adds analytics + pixels + placement + attribution.
  • Full production launch — adds custom domain + deeper verification.

A project can pursue several goals at once. For each goal, report:

  1. milestones already done,
  2. the next missing milestone,
  3. the shortest next action to advance it.

Some launch steps are human decisions, not reads (e.g. the product strategy, the screen blueprint). Those stay "to do" until the customer provides them — say so honestly rather than implying they are complete.

Note on persistence

The milestone snapshot is cached per project so progress survives across sessions. It is derived from reads — never a separate source of truth. Re-read to refresh.

Source: SKILL.md on GitHub

No third-party reports yet.

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

Last checked against GitHub yesterday.

Activeupdated last week

README badge

README badge for segmently-ai/segmently-support-plugins/segmently-launch-guide