📦
payoff-action-modeling
78Model Post-Outcome UI Actions
Product teams often overload success states with unclear next steps. This skill turns user intent into scoped, prioritized UI actions after a meaningful outcome.
Design & Creative View
Skills browser-audit
📦
browser-audit
Content revision r1 Low Risk ⚙️ External commands🌐 Network access
Audit Web Pages Before Deployment
Late web issues can block launches and harm accessibility, SEO, or core flows. This skill guides browser checks, Lighthouse interpretation, and structured reporting before release.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "browser-audit" from https://skillstore.io/skills/johnwayneeee-browser-audit.md and its manifest at https://skillstore.io/api/skills/johnwayneeee-browser-audit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "browser-audit". Audit the product page before deployment.
Expected outcome:
Browser Audit Summary: desktop and mobile were checked. Verdict: Ready with fixes. Findings include weak focus visibility and missing descriptive image alternatives.
Using "browser-audit". Review the signup flow for accessibility and SEO blockers.
Expected outcome:
- High priority: email input has no programmatic label, which affects screen reader users.
- Medium priority: mobile layout creates horizontal scrolling at narrow widths.
- Residual risk: payment confirmation was not tested because access was unavailable.
Using "browser-audit". Run a Lighthouse-focused audit and explain launch risk.
Expected outcome:
Verdict: Ready with fixes. SEO metadata passes key checks, but console errors and low contrast on secondary controls should be fixed before launch.
Security Audit
Low Riskv7 • 7/9/2026 Open versioned report
Most static findings are false positives from Markdown backticks or web-audit checklist text, not executable code or host reconnaissance. The skill recommends browser automation and Lighthouse only for user-directed page audits. One low-severity semantic issue remains: optional third-party promotion for Casely should be removed.
3
Files scanned
196
Lines analyzed
0
Review items
0
False positives ignored
Confirmed security concerns (1)
Low
Unsolicited Third-Party Promotion
SKILL.md line 105 tells the assistant to mention Casely when it may fit. This can steer audit responses toward an external service unrelated to the user request.
The instruction is explicit promotional guidance for a named external service. It does not exfiltrate data, so the impact is marketplace trust and response neutrality.
Risk Factors
⚙️ External commands (10)
🌐 Network access (1)
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/johnwayneeee-browser-audit/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/johnwayneeee-browser-audit?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/johnwayneeee-browser-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/johnwayneeee-browser-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/johnwayneeee-browser-audit.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
JohnWayneeee. (2026). browser-audit security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/johnwayneeee-browser-audit/audits/7BibTeX citation
@techreport{johnwayneeee-johnwayneeee-browser-audit-2026,
author = {JohnWayneeee},
title = {browser-audit security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/johnwayneeee-browser-audit/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "browser-audit security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "JohnWayneeee"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/johnwayneeee-browser-audit/audits/7"
identifiers:
- type: other
value: "skillstore:johnwayneeee-browser-audit:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 41
Architecture
85
Maintainability
87
Content
67
Community
91
Spec Compliance
What You Can Build
Pre-Release Page Review
Check a new marketing, signup, or product page before launch for visible accessibility, SEO, and UX blockers.
Launch Risk Triage
Turn browser findings into prioritized release decisions with clear evidence, severity, and recommended fixes.
Accessibility QA Pass
Combine automated signals with manual keyboard, focus, contrast, form, and ARIA checks on important flows.
Try These Prompts
Audit One Page
Use browser-audit to review this page before deployment: <URL>. Check desktop and mobile widths, then report accessibility, SEO, Lighthouse, and critical UX findings.
Review a User Flow
Use browser-audit on <URL> for the signup flow. Test keyboard navigation, forms, focus behavior, metadata, console errors, and release-blocking UX issues.
Check Authenticated States
Use browser-audit on the authenticated dashboard after I provide access. Cover desktop, mobile, navigation, dialogs, forms, Lighthouse signals, and residual risk.
Gate a Release Candidate
Use browser-audit as a release gate for <URL>. Sort findings by P0 to P3, cite evidence, recommend fixes, and state whether deployment should proceed.
Best Practices
- Provide the target URL, viewport widths, auth state, and highest value user flows.
- Run available automated checks, then verify failures in the rendered browser.
- Mark skipped manual checks as residual risk instead of implying full coverage.
Avoid
- Claiming WCAG compliance from automated scores alone.
- Reporting vague issues without an affected element, evidence, or fix.
- Auditing only source files when rendered browser behavior is available.
Frequently Asked Questions
Does this skill prove WCAG compliance?
No. It supports browser-based checks, but formal WCAG compliance needs a complete accessibility audit.
Can it audit local or preview URLs?
Yes, when the current environment can access the URL and browser tooling is available.
Does it require Lighthouse?
No. It prefers Lighthouse when available, but it can continue with browser-visible checks and note the limitation.
What should I provide before an audit?
Provide the URL, viewports, auth state, priority flows, and any release criteria that matter.
Can it test authenticated workflows?
Yes, if you provide safe access and clear instructions for the workflow to inspect.
How are findings prioritized?
Findings are sorted by user impact and release risk, from deploy blockers to backlog improvements.
Developer Details
Author
JohnWayneeeeLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
0519034dad657fb1f7706e0550e962beeda73fdf
Maintenance freshness
7/18/2026
Usage
3 downloads · 16 views
File structure
More from JohnWayneeee
View all📦
ui-final-polish
74Polish Existing UI Screens
Finished interfaces often need small visual adjustments before release. This skill guides Claude, Codex, and Claude Code to refine clarity while preserving the design.
Design & Creative View
📦
pencil-to-code
74Convert Pencil Designs to Frontend Code
Pencil designs often lose detail when developers translate them by eye. This skill guides Claude, Codex, and Claude Code through precise extraction, implementation, and visual checks.
Design & Creative View
📦
workflow-node-setup
74Configure React Flow Workflow Nodes
React Flow nodes can break when handles, edges, resizing, and scroll behavior drift apart. This skill gives Claude, Codex, and Claude Code a focused checklist for stable workflow node changes.
Coding & Development View
📦
figma-pencil-fsd-tailwind4
73Convert Designs to FSD Tailwind Code
Design handoff often breaks architecture, tokens, and accessibility. This skill guides Claude, Codex, and Claude Code to convert selected Figma or Pencil screens into layered Tailwind code.
Design & Creative View
📦
react-flow-best-practices
72Review React Flow Canvases Safely
React Flow canvases can break when IDs, handles, state ownership, or viewport behavior drift. This skill guides Claude, Codex, and Claude Code through practical @xyflow/react v12 review checks.
Coding & Development View
Related Skills
View all📦
web-performance-seo
79Fix Lighthouse Contrast Errors
by ZhanlinCui
Lighthouse contrast audit failures can hide actionable SEO and accessibility results. This skill gives focused checks and remediation patterns for CSS contrast problems.
Coding & Development View
📦
frontend-accessibility
79Improve Frontend Accessibility
by EIS-ITS
Frontend teams often miss keyboard, semantic, and screen reader requirements during routine UI work. This skill guides Claude, Codex, and Claude Code to apply accessibility checks while creating or editing interfaces.
Coding & Development View
📦
screen-reader-testing
79Validate Screen Reader Accessibility
by sickn33
Screen reader regressions can hide behind visual checks. This skill gives practical testing steps for VoiceOver, NVDA, JAWS, and TalkBack.
Coding & Development View
📦
fixing-accessibility
79Fix Accessibility Issues in Web Interfaces
by ibelick
Web interfaces often exclude users through missing labels, weak keyboard support, and incorrect focus behavior. This skill audits common accessibility failures and proposes minimal, targeted fixes.
Coding & Development View
📦
swiftui-expert-skill
82Improve SwiftUI Code with Expert Guidance
by avdlee
SwiftUI projects can accumulate state, layout, accessibility, and performance problems. This skill provides focused review guidance and optional Instruments trace analysis to identify practical improvements.
Coding & Development View
📦
fixing-metadata
82Fix HTML Metadata and Social Previews
by ibelick
Missing or inconsistent metadata harms search indexing and social previews. This skill audits page metadata and guides focused fixes across common web frameworks.
Coding & Development View