ui-verify
Makes a UI pull request autonomously verifiable. `author` writes a Markdown intent spec — the happy path plus out-of-bounds cases from a PR-scoped brainstorm — into the PR description as a collapsed, machine-findable block (delegated to by `create-pr` on UI diffs). `run` resolves the PR's live preview URL via the GitHub deployments API and runs the spec there through `aw-tester`, which may adapt the route but checks every expected outcome with evidence, and reports a verdict plus full-page screenshots (`--no-screenshots` opts out). It then tries to break the same change — hostile input, double submits, failed requests, small viewports — and documents every probe with screenshots, never changing the verdict (`--no-adversarial` opts out). `verify` is author-if-needed, then run. `setup` delegates to `aw-setup --target preview`. A LoreKit loop feeds runner friction into the next spec. Web only. Triggers on "write a preview spec", "verify this PR's preview", "try to break this PR's preview", "/ui-verify".
66
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The agent skill inspects pull request descriptions and comments read via GitHub integrations or MCP tools, exposing the workflow to untrusted outsider-authored text.
- Repository
- mthines/agent-skills
- Commit
39b3f44
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.