Skip to content
TrustedSkillsbeta
Back to all skills

Phoenix Playwright Tests

Checked
arize-ai·vlatest·testing

Automatically generate and execute robust UI tests from specifications using AI, identifying regressions and improving application quality.

Repository

Install on your platform

This skill no longer installs under the name phoenix-playwright-tests. SKILL.md is marked internal, so the skills CLI hides it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

arize-ai

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned arize-ai/phoenix at b438233ce4.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
b438233ce4
Manifest
.agents/skills/phoenix-playwright-tests/SKILL.md
Scanned
3 files, 911 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to execute Playwright tests directly within the Phoenix environment, allowing for automated browser interaction and validation. It streamlines the testing workflow by integrating test execution capabilities into the agent's operational context.

When to use it

  • Automating end-to-end user journey verification across different browsers.
  • Validating UI changes after deploying new features or updates.
  • Running regression suites to ensure existing functionality remains intact.
  • Generating visual reports of test results for stakeholder review.

Key capabilities

  • Direct integration with the Playwright testing framework.
  • Execution of browser automation scripts within Phoenix.
  • Support for various browser environments (Chromium, Firefox, WebKit).
  • Automated handling of common web interactions like clicks and form submissions.

Example prompts

  • "Run the full regression suite for the checkout flow using Playwright."
  • "Execute a specific test case to verify the new login button functionality."
  • "Generate a report of all failed tests from the last deployment cycle."

Tips & gotchas

Ensure your Phoenix environment has the necessary dependencies installed before attempting to run complex browser automation tasks. Limit concurrent test executions if you encounter resource constraints during large-scale testing sessions.