audit
Audit Interface Quality
Frontend teams need clear evidence before fixing interface problems. This skill produces a prioritized audit across accessibility, performance, theming, responsiveness, and design patterns.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "audit" from https://skillstore.io/skills/pbakaus-audit.md and its manifest at https://skillstore.io/api/skills/pbakaus-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 "audit". Audit a dashboard before launch.
Expected outcome:
A prioritized report with an anti-pattern verdict, executive summary, findings by severity, systemic issues, positive findings, and fix priorities.
Using "audit". Review a component library for theming quality.
Expected outcome:
A component-focused audit that identifies token misuse, dark mode gaps, contrast problems, and recommended normalization work.
Using "audit". Check a mobile checkout flow.
Expected outcome:
A responsive and accessibility report covering touch targets, overflow, keyboard access, form labels, and release-blocking issues.
Security Audit
SafeThe three static findings are false positives caused by Markdown examples that wrap slash commands in backticks. No evidence found for shell execution, command injection, network access, data exfiltration, or prompt injection in SKILL.md.
Risk Factors
⚙️ External commands (3)
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/pbakaus-audit/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/pbakaus-audit?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/pbakaus-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/pbakaus-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/pbakaus-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
pbakaus. (2026). audit security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/pbakaus-audit/audits/4BibTeX citation
@techreport{pbakaus-pbakaus-audit-2026,
author = {pbakaus},
title = {audit security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/pbakaus-audit/audits/4},
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: "audit security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "pbakaus"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/pbakaus-audit/audits/4"
identifiers:
- type: other
value: "skillstore:pbakaus-audit:audit:4"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
pbakaus-audit
2026-08-21
cygnusfear-audit
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Pre-release frontend review
Audit a new feature before launch and rank blocking issues by user impact.
Design system compliance check
Find hard-coded styles, broken dark mode states, and inconsistent token usage across interface files.
Accessibility remediation planning
Create a clear issue list with WCAG context, affected locations, and recommended fix priorities.
Try These Prompts
Audit the settings page for accessibility, performance, theming, and responsive design. List only issues that need action.
Audit the checkout flow and identify critical or high severity issues that should block release. Include impact and next steps.
Audit shared UI components for token usage, dark mode support, responsive behavior, and recurring design anti-patterns.
Audit the full dashboard experience and group findings into immediate, short-term, medium-term, and long-term remediation work.
Best Practices
- Run the audit on a specific feature or flow when possible.
- Provide screenshots, routes, or component names to improve location accuracy.
- Use the priority sections to plan fixes before starting implementation.
Avoid
- Do not ask the skill to fix issues during the audit.
- Do not treat every visual concern as critical severity.
- Do not rely on the audit as the only accessibility validation step.