segmently-test-kit

Validate Segmently SHOW and E2E DO actions against runtime contracts.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/segmently-ai/segmently-support-plugins --skill segmently-test-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: segmently-test-kit
Source: https://github.com/segmently-ai/segmently-support-plugins/tree/main/plugins/segmently-launch-assistant/skills/segmently-test-kit
Command: npx skills add https://github.com/segmently-ai/segmently-support-plugins --skill segmently-test-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a safe runtime companion for Segmently Launch Assistant browser work, so SHOW and E2E DO actions can be executed with clear boundaries, required preflight checks, and evidence-based verification.

Core Features & Use Cases

  • SHOW support: Guides read-only browser navigation, focus, and screenshot evidence when a launch contract names this skill as the companion.
  • E2E DO support: Enforces explicit execution approval, required target identifiers, and post-action read-back verification for controlled UI mutations.
  • Preflight and safety checks: Reminds the agent to confirm Segmently CLI auth, browser tooling, and access readiness before claiming success.
  • Use case: A launch flow needs browser-backed validation on a customer project, and this skill keeps the interaction within the generated contract instead of inventing actions or requesting sensitive credentials.

Quick Start

Ask the assistant to use segmently-test-kit for the generated Segmently browser contract and verify the required preflight, target, and evidence steps before proceeding.

Frequently Asked Questions about segmently-test-kit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify browser automation actions against a runtime contract?

Browser automation actions are verified by enforcing explicit execution approval, required target identifiers, and post-action read-back verification for controlled UI mutations. This ensures actions align with the generated runtime contract before proceeding.

What safety checks are required before running E2E testing in a launch flow?

E2E testing requires preflight safety checks to confirm CLI authentication, browser tooling availability, and access readiness. These checks must pass before executing any controlled UI mutations or claiming verification success.

Can I use screenshot evidence for read-only browser navigation during preflight checks?

Screenshot evidence is supported for read-only browser navigation and focus operations. The skill guides these actions to capture visual proof when a generated launch contract names it as the companion for verification.

Does this skill execute UI mutations without explicit approval?

No, controlled UI mutations require explicit execution approval and specific target identifiers. The skill enforces these boundaries to prevent inventing actions or requesting sensitive credentials outside the runtime contract.

What happens if my launch flow lacks CLI authentication for browser verification?

Browser verification cannot complete successfully without CLI authentication. The skill enforces preflight reminders to confirm CLI auth and browser tooling readiness before attempting any approved, target-specific actions.

Why does browser-backed E2E testing need a companion skill for launch flows?

A companion skill provides clear boundaries and evidence-based verification for E2E DO and SHOW actions. It keeps browser interactions within the generated contract instead of allowing unrestricted or unsafe operations.