Dark Theme React UI System

The skill is primarily for generating local React/Tailwind UI and shows no malware, credential theft, covert exfiltration, or destructive defaults. However, dependencies use broad version ranges, and the skill lacks dependency security review, data-flow disclosure, user-confirmation guidance, rollback guidance, and external-resource risk notes, so substantial points are deducted.

The stack, configuration, and component examples are broadly consistent and include states such as loading, errors, and modal dismissal. However, the documented structure references pages and components not supplied in the evidence, some examples have likely issues such as Badge classes requiring extra configuration and Checkbox animation depending on the checked prop, and the Toast source is truncated. No key-path tests or diagnosable failure procedures are provided, so the static ceiling and uncertainty require a conservative score.

The audience and scenarios are clear: dark React dashboards, admin panels, and data-rich interfaces, with component, layout, mobile, and animation patterns. Non-fit cases, invocation conditions, input/output boundaries, and accessibility tradeoffs are not clearly stated, and the documentation is mainly English. npm reachability in mainland China is not established, but the evidence does not show that the core function entirely depends on an unreachable overseas service.

The skill has front matter, an MIT license, author metadata, version 1.0.0, progressive sections for configuration, components, tokens, and patterns, plus examples. It lacks a changelog, compatibility matrix, explicit maintenance owner, and update path; some referenced files cannot be fully verified from the supplied material, so full marks are not justified.

The configuration, CSS tokens, React components, and page templates provide reusable material for common dark administrative UI tasks. However, there is no complete runnable project, some dependencies or referenced files are missing from the evidence, and examples include placeholders and likely integration or runtime issues. Outputs would require meaningful assembly and review, warranting a conservative static score.

The supplied source is auditable and includes concrete version ranges, code, and configuration examples; the repository README also mentions CI and tests. Nevertheless, no skill-specific test suite, execution result, or third-party reproduction evidence is provided, and some source content is truncated, preventing independent reproduction of key paths.