Skills/ClawHub/xiaoyaoclaw-beautify-github-readme

xiaoyaoclaw-beautify-github-readme@1.0.14

CAUTION· static only

Publisher claims: "OpenClaw skill that beautifies GitHub READMEs: redesign a repository homepage or create project-native visual assets — pure SVG heroes, section headers, diagrams, badges, GIF motion graphics, showcase modules, or hybrid SVG-composed PNG/WebP — with built-in render-level visual verification (scripts/visual_verify.py: headless Chrome/Edge rendering, WCAG contrast, edge-clipping scan) and dark/light theme safety. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README, or to create README visual assets. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset. Activate only when the user explicitly asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README, or to create README visual assets. Do not activate for general questions, passive reading, or discussion of a README that does not request visual or audit work. Capabilities are split across the bundled scripts: scripts/visual_verify.py renders assets with headless Chrome/Edge and checks WCAG contrast and edge clipping, scripts/render_motion_gif.py turns named SVG layers into an animated GIF, scripts/audit_readme.py performs the static README/SVG audit, and scripts/svg_safety.py is the shared trust boundary that vets untrusted SVG input for both render paths. 中文:面向 OpenClaw 的 GitHub README 视觉美化技能:重新设计仓库主页,或创建项目原生 视觉素材——纯 SVG hero、章节标题、流程图、徽章、动效 GIF、SVG 混合构图等,内置渲染级 视觉验证(无头 Chrome/Edge 渲染、WCAG 对比度、边缘贴边检测)与深浅双主题安全。 能力由内置脚本分工实现:visual_verify.py 负责渲染级验证,render_motion_gif.py 负责 SVG 分层转 GIF,audit_readme.py 负责静态审计,svg_safety.py 是两条渲染路径共用的 不可信 SVG 信任边界。 仅当用户明确要求美化/重新设计/升级/简化/审查 GitHub 仓库主页或制作 README 视觉素材时 激活;对 README 的一般性提问、被动阅读或讨论不激活本技能。 触发词:README美化、美化README、GitHub主页设计、仓库主页改版、README hero、 README视觉、SVG首图、readme redesign、beautify readme、README 动效。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher dtsola · publishing for 48 daysInstalls 726Last detonated 23 min ago

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-16 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

MEDIUM
Python subprocess execution detectedscripts/svg_safety.py:206 · Python subprocess execution detectedreturn subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 5,390 lines in 25 files.

Cost to the agent

Instructions loaded
≈5,880 tok
1 file · 25 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim dtsola: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim dtsolaPropose a patch to the maintainer