agentra-e2e-testing
Browser-based E2E validation for Agentra applications.
Install
mkdir -p .claude/skills/agentra-e2e-testing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14816" && unzip -o skill.zip -d .claude/skills/agentra-e2e-testing && rm skill.zipInstalls to .claude/skills/agentra-e2e-testing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Plan, write, run, or review Agentra E2E tests using Playwright/browser tooling. Use for critical chat/auth/user journeys, flaky tests, screenshots, traces, and browser-driven validation.Key capabilities
- →Identify critical user journeys and owning workspaces
- →Use stable selectors and explicit waits for validation
- →Capture screenshots, traces, or console/network details for diagnosis
- →Quarantine or document flaky behavior
- →Report journey, command, artifacts, result, and follow-up risk
How it works
The skill validates Agentra workflows at the browser level, focusing on critical user journeys, and uses Playwright/browser tooling to capture diagnostic information and report findings.
Inputs & outputs
When to use agentra-e2e-testing
- →Test auth flow redirects
- →Validate chat stream interruption
- →Debug flaky browser-based tests
About this skill
Agentra E2E Testing
Use this skill for browser-level validation of Agentra workflows.
Sources of truth
AGENTS.md- Existing Playwright/browser-use tooling in the Codex environment.
.claude/skills/e2e-testing/SKILL.mdremains a reference for generic E2E patterns when deeper examples are needed.
Workflow
- Identify the critical user journey and owning workspace.
- Prefer existing app scripts and test patterns before introducing new test structure.
- Use stable selectors and explicit waits based on user-visible state.
- Capture screenshots, traces, or console/network details when diagnosing.
- Quarantine or document flaky behavior instead of hiding it with broad waits.
Agentra focus areas
- Auth redirects and signed-in/signed-out states.
- Chat request lifecycle and SSE/stream interruption behavior.
- Error, loading, empty, and cancellation states.
- Runtime smoke handoff when UI symptoms point to AgentCore behavior.
Output
Report journey, command or browser target, artifacts captured, result, and follow-up risk.
When not to use it
- →The user needs generic E2E patterns when deeper examples are needed
- →The user needs to write video scripts or storyboards
Limitations
- →Does not hide flaky behavior with broad waits
- →Does not write video scripts or storyboards
How it compares
This skill provides specialized E2E testing for Agentra workflows, focusing on browser-level validation and specific Agentra focus areas, unlike a generic E2E testing approach.
Compared to similar skills
agentra-e2e-testing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| agentra-e2e-testing (this skill) | 0 | 3mo | No flags | Intermediate |
| ui-ux-expert-skill | 91 | 9mo | Review | Advanced |
| frontend-testing | 11 | 3mo | Review | Intermediate |
| feature-flags | 6 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
ui-ux-expert-skill
fercracix33
Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.
frontend-testing
langgenius
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
react-hook-form-writer
dust-tt
Write and refactor React forms using react-hook-form with Zod validation. Use when creating new form components, converting existing forms to react-hook-form, or implementing form validation patterns.
e2e-tests-studio
mastra-ai
REQUIRED when modifying any file in packages/playground-ui or packages/playground. Triggers on: React component creation/modification/refactoring, UI changes, new playground features, bug fixes affecting studio UI. Generates Playwright E2E tests that validate PRODUCT BEHAVIOR, not just UI states.
ui-testing
alinaqi
Visual testing - catch invisible buttons, broken layouts, contrast