replay-qa-api Skill
Use when calling Replay QA's REST API directly from Codex. Covers bearer-token setup, Replay recording prerequisites, project creation from Replay recordings or target URLs, polling, bug retrieval, journeys, test runs, explorations, and fix workflow discipline. Published by openai in plugins.
Decision snapshot
Is this a fit?
Testing, Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
19 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is replay-qa-api Skill?
Use when calling Replay QA's REST API directly from Codex. Covers bearer-token setup, Replay recording prerequisites, project creation from Replay recordings or target URLs, polling, bug retrieval, journeys, test runs, explorations, and fix workflow discipline. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Data analysis
- Testing use cases
- Data analysis use cases
Declared skill metadata
- Source file: plugins/replayio/skills/replay-qa-api/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use replay-qa-api Skill
- Use it for testing.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/replayio/skills/replay-qa-api/SKILL.md
What it does
Use when calling Replay QA's REST API directly from Codex. Covers bearer-token setup, Replay recording prerequisites, project creation from Replay recordings or target URLs, polling, bug retrieval, journeys, test runs, explorations, and fix workflow discipline.
Skill instructions
Replay QA API Use the Replay QA REST API directly when a task needs Replay QA analysis. This skill is instructions-only: do not use Replay MCP tools, Codex apps, or plugin hooks as substitutes for Replay QA REST API calls. Replay.io Skill Prerequisite Before making any Replay QA API call, make sure the replayio skill in this same Codex plugin bundle has been loaded and applied for the current session. If setup is unknown, load ../replayio/SKILL.md first and follow it before continuing. In particular, verify: - REPLAYAPIKEY is mapped from SECRETREPLAYAPIKEY when available. - REPLAYQAAPIKEY is mapped from SECRETREPLAYQAAPIKEY. - AGENTBROWSEREXECUTABLEPATH points at Replay Chromium. - RECORDALLCONTENT and RECORDREPLAYVERBOSE are set. - Any Replay recording referenced by Replay QA has uploaded or has a concrete recording UUID. Do not proceed with project creation or polling if this prerequisite is unknown. Load and apply the replayio skill first, then return to this skill. Authentication R
Verified compatibility and discovery
Frequently asked questions
What is replay-qa-api?
replay-qa-api is a open-source AI agent skill with Copy skill directory. Use when calling Replay QA's REST API directly from Codex. Covers bearer-token setup, Replay recording prerequisites, project creation from Replay recordings or target URLs, polling, bug retrieval.
Who is replay-qa-api best for?
replay-qa-api is best for reusing agent instructions, scripts, and references, testing workflows, data analysis workflows.
How do I install replay-qa-api?
Install or run replay-qa-api using Copy skill directory. Check replay-qa-api for the latest setup command.
Is replay-qa-api actively maintained?
replay-qa-api may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
