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.

evalsGRADER_INSTRUCTIONS.md

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

Behavioral eval — GRADER instructions (segmently-launch-guide)

You are the skill-creator GRADER agent. First READ the official rubric and follow it exactly. It ships with the installed skill-creator skill/plugin; locate that skill's agents/grader.md file in the current agent runtime before grading.

You grade a BATCH of behavioral evals of the customer-facing segmently-launch-guide skill. You are given a list of ids. For EACH id:

  1. Look up the eval in <skill-root>/evals/scenario-evals.json (match id). Use its prompt, scenario, lang, and expectations.
  2. Read the transcript at …/qa-screenshots/launch-guide-verification/evals/<NN>-<scenario>-<lang>/transcript.md (<NN> = id zero-padded to 2). The trailing SKILLS_USED: line is METADATA — do not grade it as content, but DO record whether it contains segmently-launch-guide.
  3. Grade EACH expectation strictly PASS or FAIL with a cited quote/evidence from the transcript. Burden of proof to PASS is on the expectation; superficial or coincidental satisfaction = FAIL (per the rubric). A wrong leg, a missing/incorrect verify, a dishonest handoff ("done" for Stripe/DNS), or any customer-unsafe leak = FAIL the relevant expectation.
  4. Per the rubric's "Critique the Evals" step, flag weak expectations (would pass a wrong answer) and important uncovered outcomes in eval_feedback.

Output

For each id, WRITE a grading.json (the grader.md schema: expectations[], summary{passed,failed,total,pass_rate}, eval_feedback, and add a top-level "triggered_launch_guide": true|false from the SKILLS_USED line) to that eval's folder: …/qa-screenshots/launch-guide-verification/evals/<NN>-<scenario>-<lang>/grading.json

Final reply to me: a compact list, one line per id: <id> <scenario>/<lang>: PASS x/N [trig=Y/N] plus a short phrase on any FAIL or weak expectation.

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