wunderui-token-check
Replace Hardcoded Styles with WunderUI Tokens
Hardcoded colors and dimensions make WunderUI projects harder to theme consistently. This skill compares literals with bundled tokens and supports reviewed replacements with measured differences.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "wunderui-token-check" from https://skillstore.io/skills/wunder-ui-wunderui-token-check.md and its manifest at https://skillstore.io/api/skills/wunder-ui-wunderui-token-check/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "wunderui-token-check". Inspect a component with arbitrary padding of 16 pixels and a radius of 10 pixels.
Resultado esperado:
- Padding: the spacing scale has an exact 16-pixel match, classified as swap.
- Radius: the nearest bundled radius is 8 pixels, a 2-pixel difference classified as visible.
- No source edits were requested.
Usando "wunderui-token-check". Inspect a fixed white background before adding dark mode.
Resultado esperado:
- Fixed white background: classified as visible because replacing it with a semantic token changes dark-mode behavior.
- The bundled background token is white in light mode and dark in dark mode.
- Review the intended surface role before approving a replacement.
Auditoría de seguridad
Riesgo medioMost static findings match harmless regular expressions, template strings, documentation, or expected local operations. Four findings confirm unsafe report output or report-supplied paths, allowing external file overwrites through symlinks or a tampered report. A separate semantic finding identifies symlink traversal during scanning; no evidence found of malicious intent, prompt injection, credential collection, or network transmission.
Preocupaciones de seguridad confirmadas (1)
Elementos de revisión de capacidades (4)
Estas son capacidades locales reales que pueden esperarse para esta habilidad, por lo que requieren revisión, pero no se cuentan como comportamiento malicioso confirmado.
Factores de riesgo
🌐 Acceso a red (1)
⚙️ Comandos externos (48)
⚡ Contiene scripts (4)
📁 Acceso al sistema de archivos (19)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/wunder-ui-wunderui-token-check/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/wunder-ui-wunderui-token-check?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/wunder-ui-wunderui-token-check?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wunder-ui-wunderui-token-check/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/wunder-ui-wunderui-token-check.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
wunder-ui. (2026). wunderui-token-check security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wunder-ui-wunderui-token-check/audits/1Cita BibTeX
@techreport{wunder-ui-wunder-ui-wunderui-token-check-2026,
author = {wunder-ui},
title = {wunderui-token-check security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/wunder-ui-wunderui-token-check/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-token-check 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-token-check/audits/1"
identifiers:
- type: other
value: "skillstore:wunder-ui-wunderui-token-check:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Clean Up Component Styles
Compare component literals with WunderUI tokens and review supported replacements before editing source.
Review Token Coverage
Group distant values and decide whether each needs an existing semantic token, a new token, or an explicit exception.
Prepare Theme Changes
Inspect fixed colors and suggested light and dark values before planning a theming migration.
Prueba estos prompts
Check my trusted WunderUI project for hardcoded colors, spacing, and radii. Inspect symlinks before scanning. Summarize findings without changing source files.
Scan this component and explain its nearest tokens and measured differences. Compare suggested light and dark values. Do not apply replacements until I approve.
Generate a fresh report for these trusted source folders. Show the proposed swap replacements and wait for approval. Then apply them, rescan, and run project checks.
Group review findings by value and semantic role. Recommend mappings or exceptions, including dark-mode effects. Propose explicit selections for approval and identify manual spacing edits.
Mejores prácticas
- Use a clean version-control checkpoint, trusted source folders, and a freshly generated report; inspect symlinks and report targets before fixing.
- Approve replacements by semantic role and inspect both theme modes rather than relying only on measured distance.
- Rescan after edits, review the diff, run project checks, and inspect affected components visually.
Evitar
- Running fix against a supplied or tampered report without checking its paths and replacements.
- Treating low color distance as proof of accessibility, transparency preservation, or identical dark-mode behavior.
- Replacing every review finding automatically or changing artwork and brand colors without a design decision.
Preguntas frecuentes
Which assistants can use this skill?
What must my project provide?
What do swap, visible, and review mean?
Does it rewrite every finding?
Does it send project data to a service?
What security precautions are necessary?
Detalles del desarrollador
Autor
wunder-uiLicencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Ref.
e406bf64b5db6e514879399e87b346fa7ff7c2fb
Actualidad del mantenimiento
11/10/2026
Uso
0 descargas · 0 vistas
Estructura de archivos