A read-only quality check for a live website. It checks what the server delivers, what a browser renders, and whether the result differs from approved visual versions.

It helps check routing, page content, layout, browser errors, visual regressions, SEO metadata, structured data, links, and accessibility.

A successful deployment can still show broken images, incorrect content, JavaScript errors, bad links, accessibility problems, or missing search metadata. This sweep gathers those issues into an evidence-based report.

qa — Skill for Claude Code by adobe/skills

About the project

Adobe Skills is a collection of skills, plugins, agents, and MCP servers that extend AI coding agents with workflows for Adobe products and other tasks. Developers use it to help coding agents work with Adobe analytics and application-building tools. The catalogue entries are the repository’s own skills, plugins, agents, and MCP integrations.

adobe/skills · 243 stars · on GitHub · adobe.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add adobe/skills --skill qa

Clone the repo

git clone --depth 1 https://github.com/adobe/skills

Made for: Claude Code.

Or install stardust, the plugin that ships this one along with the rest of its 15 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/adobe/skills/qa/github.svg)](https://agentmods.dev/skills/adobe/skills/qa)

Your own site

<a href="https://agentmods.dev/skills/adobe/skills/qa"><img src="https://agentmods.dev/badge/skills/adobe/skills/qa/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/adobe/skills/qa"><img src="https://agentmods.dev/badge/skills/adobe/skills/qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 150 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,004 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Agent Snooping · line 27
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00150	$0.02004
Opus 5.5	$0.00060	$0.00802
Sonnet 5.5	$0.00030	$0.00401
Haiku 4.5	$0.00015	$0.00200

Measured 10d ago against content hash 8f16cb2c7a71, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

qa scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

The scan reads SKILL.md. This mod also ships 22 executable files (scripts/checks/ai-readability.mjs, scripts/checks/browse.mjs, scripts/checks/chrome.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/stardust/skills/qa/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

stardust:qa — read-only site QA sweep

One live URL in. One evidence-bound findings report out. This skill never edits anything — not site content, not DA documents, not repo code. Its only writes are report artifacts under stardust/qa/. If the user wants findings fixed, that is a separate, explicit follow-up outside this skill.

qa is the post-deploy counterpart of rollout's delivery verification: where rollout asks "did every page ship?", qa asks "is everything that shipped actually correct?" — at all three layers a deploy can silently break:

delivery — what the pipeline serves (.plain.html, full HTML, sheets, sitemap)
rendered — what a browser shows after block decoration (and what it does: an autoplay video that only shows its poster is a rendered defect)
regression — what changed since the last approved state (visual baselines)

A green upper layer never implies the lower one: a publish 200 ≠ delivered, delivered HTML ≠ rendered correctly.

Setup

Run the master skill's setup (skills/stardust/SKILL.md § Setup) if not already done this session. qa works standalone too — it only needs a live base URL.
Resolve the base URL (the *.aem.live host or production domain). If the user didn't give one, look in stardust/rollout/rollout.json (site.liveHost) or ask.
Resolve the inventory source — what pages the sweep covers, merged from any of: stardust/template-map.json (also supplies template assignments for conformance; scripts/from-knowledge.mjs writes it from a spec, plus allowlist entries for 404s the source already had), a paths file, and the live sitemap.xml (always fetched; parity mismatches become findings, so a wrong sitemap can't silently shrink coverage).
Optional inputs that unlock deeper checks:
- --scrape stardust/scrape — verbatim fidelity vs the extraction capture
- --expected-blocks <json> — explicit per-template block expectations
- --parity <json> — dynamic parity file to replay (default stardust/dynamics/parity.json; the dynamics check reports parity-missing when absent)
- --auth-header "token …" / --token-env SITE_TOKEN — protected origins; the secret is sent to the base origin only (otherwise derived by fleet consensus)
- --blocks-dir <dir> — the site's blocks/ checkout, so the editability check can honour @ew-exempt JSDoc tags (otherwise pass --ew-exempt a,b for index-driven blocks)
Browser checks need playwright resolvable from the project (node_modules/playwright). If missing, run the delivery-layer checks only (--checks routing,content,templates,metadata,links) and tell the user what was skipped.
Append a phase-transition line to stardust/status.jsonl per reference/run-status.md (master skill) at sweep start/end.

Read the full file on GitHub · 146 lines

Files

What ships with it

25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago Changed · +1 lines 8f16cb2c7a71
16d ago Changed · +1 lines 4c25df649d1b
1mo ago Changed · +1 lines · +12 tokens per session 53e077b16ca9
1mo ago Changed · +3 lines 9a3d852ec055
1mo ago Changed · +2 lines 90185a10c407
1mo ago Changed · +5 lines 6512eaaa7a7a
1mo ago Changed · +12 lines 51ea09f3c91c
1mo ago First seen · 121 lines · 138 tokens per session scan A 3ea39f64ae5f

Subscribe to this mod's changes

qa is a skill published in the GitHub repository adobe/skills (243 stars, last pushed yesterday), licensed Apache-2.0. It adds 150 tokens to every session and 2,004 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Debugging E2E testing Testing adobe ai-agents skills

diagnosing-bugs

Build a tight, red-capable feedback loop before diagnosing failures, then minimize, test ranked hypotheses, and lock the fix with a regression test.

jellydn/my-ai-tools · 34 tokens

playwright-trace-analyzer

Analyzes Playwright E2E trace.zip archives (and bare trace JSONL when unpacked). Extracts the action timeline, network waterfall, console errors, and DOM-snapshot anchors, then identifies the highest-impact problems (flaky waits, slow selectors, network bottlenecks, hung actions, unhandled console errors, navigation…

mthines/agent-skills · 232 tokens

adhoc-verification

Produce fresh, focused, local verification evidence for a code change without relying on the full test suite. Use when a system reminder (or the user) demands ad-hoc verification after an edit, or when you want to prove one behavior in isolation. Covers the correct way to write a throwaway supertest/harness script…

pedroiff0/awesome-skills · 86 tokens

buildkite-playwright-failures

Analyze Playwright test logs on Buildkite to extract failed-only tests across jobs.

PSPDFKit-labs/pi-skills · 24 tokens

dogfood

Exploratory QA of web apps: find bugs, evidence, reports.

davidtoby/agent-skills · 18 tokens

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens