UI Audit
v1.0.1AI skill for automated UI audits. Evaluate interfaces against proven UX principles for visual hierarchy, accessibility, cognitive load, navigation, and more. Based on Making UX Decisions by Tommy Geoco.
⭐ 20· 7.7k·51 current·52 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (UI audit) match the provided contents: SKILL.md and many references are design checklists and frameworks. The package.json, README, and references all align with an auditing/checklist skill. There are no unrelated credentials, binaries, or platform requirements.
Instruction Scope
Runtime instructions are limited to loading the included reference files, following checklists, and generating audit reports based on user-supplied designs (e.g., Figma URLs). The SKILL.md does not instruct the agent to read system files, environment variables, or to transmit data to unexpected external endpoints.
Install Mechanism
No install spec and no code files to execute; the skill is instruction-only. package.json exists (for distribution) but there is no install script that pulls remote artifacts or executes code beyond a harmless postinstall echo. Low install risk.
Credentials
The skill requests no environment variables, credentials, or config paths. All data the skill would act on is either included (reference files) or provided by the user (design URLs/files), which is appropriate for its purpose.
Persistence & Privilege
always:false (not force-included). disable-model-invocation:false is the platform default and acceptable here; nothing in the skill requests elevated or persistent privileges or modifies other skills or system settings.
Assessment
This skill appears coherent and low-risk: it only contains local UX guidance files and no credential or install requirements. Before using: (1) verify the author/homepage (audit.uxtools.co / GitHub link in package.json) if provenance matters to you; (2) avoid pasting private or sensitive design URLs/files unless you trust the agent/environment (reports may include sensitive UI content); (3) if you install via npm or a skills registry, prefer installing from the official repo or registry to avoid tampered packages; (4) review any generated audit output before sharing externally. If you need higher assurance, confirm the GitHub repository and npm package contents match these files.Like a lobster shell, security has layers — review code before you run it.
latestvk97ew2xp1wcrtwh4zc981444b57ze8g7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.