Skills wunderui-theme

📦

wunderui-theme

Name: wunderui-theme
Author: wunder-ui

Content revision r1 Medium Risk 🌐 Network access⚡ Contains scripts⚙️ External commands📁 Filesystem access

Generate WunderUI Brand Themes

Branding WunderUI requires consistent colour tokens and readable light and dark states. This skill generates brand CSS and reports contrast checks from one hexadecimal colour.

Supports: Claude Codex Code(CC)

📊 71 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "wunderui-theme" from https://skillstore.io/skills/wunder-ui-wunderui-theme.md and its manifest at https://skillstore.io/api/skills/wunder-ui-wunderui-theme/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.

Markdown detail GET /skills/wunder-ui-wunderui-theme.md Signed manifest GET /api/skills/wunder-ui-wunderui-theme/manifest Signed lockfile GET /api/skills/wunder-ui-wunderui-theme/lockfile

Test it

Using "wunderui-theme". Generate a global theme using #0F766E.

Expected outcome:

The supplied colour remains the primary colour at step 600.
The stylesheet includes eleven brand shades and light and dark token overrides.
The report lists checked colour pairs, measured contrast, and any adjusted shades.

Using "wunderui-theme". Create a customer preview scoped to .acme with a large radius.

Expected outcome:

Brand tokens are declared on the .acme wrapper and its light and dark variants.
Radius changes are omitted because WunderUI compiles them into global utilities.
The report includes scope notes and contrast results.

Using "wunderui-theme". Check an existing WunderUI theme stylesheet.

Expected outcome:

The checker uses installed WunderUI styles when available, otherwise built-in defaults.
The report lists passing, failing, and unresolved colour pairs in both modes.
The normal console workflow returns exit code 2 when any checked pair fails.

Security Audit

Medium Risk

v1 • 10/10/2026 Open versioned report

Most static alerts match JavaScript syntax, CSS selectors, colour conversion, or documentation rather than dangerous execution. Report writes can overwrite unrelated files, and untrusted font values can inject additional CSS. No evidence found of credential access, network exfiltration, malware, or prompt injection.

Files scanned

774

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

scripts/theme.mjs:231 scripts/theme.mjs:278 scripts/theme.mjs:332-337 scripts/theme.mjs:549

Untrusted Font Values Can Inject CSS

Font text passes through fontStack without escaping CSS delimiters. Untrusted values can add rules or resource URLs when the generated stylesheet is imported.

The CLI accepts arbitrary font strings and interpolates them into CSS declarations. Exploitation requires untrusted font input and subsequent stylesheet use.

Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

scripts/theme.mjs:532

Synchronous file operations

writeFileSync(file, text)

writeFileSync replaces existing report targets without the CSS overwrite guard. A report path matching source CSS can destroy that file during make or check.

Risk Factors

🌐 Network access (5)

package.json:17 scripts/theme.mjs:10 scripts/theme.mjs:483 SKILL.md:8 SKILL.md:56

⚡ Contains scripts (2)

scripts/theme.mjs:356 scripts/theme.mjs:434

⚙️ External commands (50)

📁 Filesystem access (12)

scripts/theme.mjs:14 scripts/theme.mjs:396 scripts/theme.mjs:532 scripts/theme.mjs:552 scripts/theme.mjs:588 scripts/theme.mjs:231 scripts/theme.mjs:295 scripts/theme.mjs:403 scripts/theme.mjs:404 scripts/theme.mjs:405 scripts/theme.mjs:434 scripts/theme.mjs:548

Audited by: codex

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.

Open versioned report

Copy report link

https://skillstore.io/skills/wunder-ui-wunderui-theme/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/wunder-ui-wunderui-theme/security.svg)](https://skillstore.io/skills/wunder-ui-wunderui-theme?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/wunder-ui-wunderui-theme?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wunder-ui-wunderui-theme/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/wunder-ui-wunderui-theme.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

wunder-ui. (2026). wunderui-theme security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wunder-ui-wunderui-theme/audits/1

BibTeX citation

@techreport{wunder-ui-wunder-ui-wunderui-theme-2026,
  author = {wunder-ui},
  title = {wunderui-theme security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/wunder-ui-wunderui-theme/audits/1},
  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: "wunderui-theme security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "wunder-ui"
date-released: "2026-10-10"
url: "https://skillstore.io/skills/wunder-ui-wunderui-theme/audits/1"
identifiers:
  - type: other
    value: "skillstore:wunder-ui-wunderui-theme:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Rebrand an Application

Generate global brand tokens and review light and dark contrast before importing the stylesheet.

Preview Customer Branding

Create a scoped theme for a customer preview without changing the brand tokens outside its wrapper.

Review Theme Contrast

Check a custom WunderUI stylesheet and review unresolved tokens or failing colour pairs.

Try These Prompts

Generate a First Theme

Generate a WunderUI theme from #0F766E. Use separate CSS and report files. Show contrast results and ask before changing existing project files.

Customize Brand Styling

Create a global WunderUI theme using #0F766E, accent #F59E0B, large radius, and the already loaded Geist font. Explain any contrast failures.

Build a Scoped Preview

Generate a WunderUI theme from #059669 scoped to .acme. Preserve surrounding styles, omit radius changes, and report light and dark contrast.

Audit Existing Theme CSS

Check our WunderUI theme CSS against installed library styles. Write the report to a separate unused path. Explain failures without modifying the theme.

Best Practices

Use confirmed hexadecimal colours and trusted font names; review generated CSS before importing it.
Choose separate, intended CSS and report paths, and obtain approval before replacing project files.
Import the theme after WunderUI styles and verify representative components in both light and dark modes.

Avoid

Treating selected contrast checks as proof of complete WCAG compliance.
Passing untrusted font text or setting a report path to an existing source file.
Expecting scoped radius changes, automatic font loading, or full neutral and semantic palette replacement.