Individual skill

cross-browser-qa

0upvotes

Verify browser-engine compatibility.

skills/cross-browser-qa/SKILL.md

Read pinned source

Source commit 9922fa0af0aea32443cf7365ef5024dc7797382d

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 137
Repository last updated: Oct 22, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

accessibility Repository topic
codex Repository topic
codex-skills Repository topic
frontend Repository topic
motion Repository topic
nextjs Repository topic
react Repository topic
tailwind Repository topic
web-design Repository topic
agent-skills Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,286 bytes
agents/openai.yamlasset · 212 bytes
references/cross-browser-qa-guide.mddoc · 2,245 bytes

Read excerpt


# Cross Browser QA

Use this skill to catch browser-specific issues that one local Chromium pass will miss.

## Workflow

1. Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
2. Read [Cross Browser QA Guide](references/cross-browser-qa-guide.md) before claiming the site is ready.
3. Compare the affected path across the supported available engines, concentrating on changed CSS, focus, scrolling, media and input behavior. Record engine/version and unavailable coverage.
4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
5. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.

## Scoped execution