ClawHub

UX Baseline Check

v1.0.0

Core pack — always active for visual work. Enforces UX quality standards on any screen, flow, form, or dashboard. Ensures nothing ships with missing states....

⭐ 0· 108·0 current·0 all-time
byai-ron@aa-on-ai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name, description, and SKILL.md all describe a UX checklist for frontend visual work; nothing requested (no env vars, no binaries, no installs) is out of scope for that purpose. Minor inconsistency: the prose repeatedly calls this a "core" and "always active" pack, but the registry flags show always: false — the claim of automatic always-on activation is not reflected in the metadata.
✓
Instruction Scope
Runtime instructions are a human-facing checklist and process guidance. They do not instruct the agent to run commands, read files, access environment variables, or send data to external endpoints. The only non-technical directive is to "tell Aaron explicitly" when gaps are documented (an internal workflow instruction, not a technical operation).
✓
Install Mechanism
No install spec and no code files — instruction-only. Nothing is written to disk and there are no download URLs or package installs to evaluate, which is lower risk.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. There is no disproportionate access requested.
ℹ
Persistence & Privilege
The SKILL.md claims the pack auto-activates alongside design reviews and is "always active," but the registry flags do not set always: true. The skill is user-invocable and allows autonomous invocation (platform default); this combination is normal. If you expect it to be forced on for all agents, that is not reflected in metadata.
Assessment
This is a low-risk, instruction-only UX checklist that matches its stated purpose. Before installing: (1) Note the mismatch between the README wording ("core / always active") and the registry flag (always: false) — if you want it enforced globally, confirm how that will be configured. (2) The skill references an individual ("Aaron"); confirm that contact is meaningful within your team or adjust the workflow text. (3) Source/homepage are missing; if you require publisher provenance, verify the owner ID or obtain an internal version of the checklist. (4) Because it is instruction-only and requests no credentials, there is no technical risk from installs or env-var exfiltration — treat it as a policy/checklist document and review the wording to fit your org processes before enabling autonomous invocation if you have concerns.

Like a lobster shell, security has layers — review code before you run it.

latestvk973thg60zhkqy2ax0gmmk7n9x838fr6

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments