Tailwind V4
v1.1.0Tailwind CSS v4 with CSS-first configuration and design tokens. Use when setting up Tailwind v4, defining theme variables, using OKLCH colors, or configuring...
⭐ 0· 92·0 current·0 all-time
byKevin Anderson@anderskev
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 (Tailwind v4, CSS-first theming, OKLCH colors, dark mode) match the SKILL.md and reference files. All examples, package suggestions, and config advice relate to setting up and using Tailwind v4 and Vite; there are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
The SKILL.md and reference files limit themselves to front-end build setup, CSS directives, theming patterns, dark-mode strategies, and small client-side snippets (localStorage/matchMedia). There are no instructions to read system files, access secrets, call unexpected external endpoints, or exfiltrate data. The SSR snippet uses dangerouslySetInnerHTML — a standard FOUC-prevention pattern for injecting small inline scripts; it's safe when the injected string is static and controlled by the developer.
Install Mechanism
This is instruction-only with no install spec and no code files to execute. It recommends installing packages from the package manager (pnpm/npm) which is expected for this purpose; nothing is downloaded from arbitrary URLs or written by the skill itself.
Credentials
No environment variables, credentials, or config path access are requested. The skill's examples use local build/dev tooling and browser APIs (localStorage, matchMedia) which are appropriate and proportionate for a frontend theming guide.
Persistence & Privilege
The skill is not always-enabled and uses the platform defaults for invocation. It does not request persistent system privileges or attempt to modify other skills or global agent settings.
Assessment
This is a documentation-only skill for setting up a CSS-first Tailwind v4 workflow — it doesn't request secrets or install code itself. Before copying examples into a project: 1) verify any npm/pnpm packages and versions (install from the official registry and check the package maintainer), 2) review and test the SSR inline script (it uses dangerouslySetInnerHTML and reads localStorage — that's normal for FOUC prevention but only safe if the script content is developer-controlled), 3) confirm external resources like Google Fonts are acceptable for your privacy/CSP rules, and 4) test changes in a staging environment (and check your final build outputs) before deploying to production.Like a lobster shell, security has layers — review code before you run it.
latestvk970150va508ek2wqsdrcb2q8983phng
License
MIT-0
Free to use, modify, and redistribute. No attribution required.