AIOZ UI V3 Skills
v1.0.0Build UI components and pages using AIOZ UI V3 design system. Use this skill whenever the user wants to create, edit, or style React components using AIOZ UI...
⭐ 0· 434·0 current·0 all-time
bydatnguyenaioz@datnguyen26730
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (AIOZ UI V3 → code) matches the content: mapping rules, component API, color/typography/icon references. The skill does not request unrelated credentials, binaries, or config paths.
Instruction Scope
SKILL.md and the reference files only instruct how to translate Figma MCP tokens/names into imports, props, Tailwind classes, and component usage. There are no instructions to read arbitrary host files, access environment variables, call external endpoints, or exfiltrate data.
Install Mechanism
This is instruction-only with no install spec and no code/executable artifacts. The references mention package imports (e.g. @aioz-ui/core-v3, @aioz-ui/icon-react) but the skill itself does not attempt to download or install anything.
Credentials
The skill declares no required environment variables, credentials, or config paths. The references include project-local tsconfig/package.json examples (workspace references) that are reasonable for a component library but do not request secrets.
Persistence & Privilege
always:false and default model invocation are used. The skill does not request permanent presence or modify other skills or system-wide settings.
Assessment
This skill is a set of authoring rules and reference docs—it won't run code or ask for secrets. Before using generated code in a real project, check the imports it produces: you will likely need to install packages such as @aioz-ui/core-v3 and @aioz-ui/icon-react from your package registry, so verify those packages and versions come from a trusted source. Also review the setup examples (they reference a monorepo/workspace layout and local paths) and adapt them to your project; always inspect generated JSX/TSX before running builds to catch incorrect imports or unexpected runtime dependencies.Like a lobster shell, security has layers — review code before you run it.
latestvk97dtkxjsmxgk2g4sqfeepfe5s81sp76
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
