# skins/

> **Not supported yet.** The current scoreboard plugins don't render skins,
> so a skin placed here and selected in config has no effect, and the web UI
> and Plugin Store don't offer them. See
> [docs/SKIN_SYSTEM.md](../docs/SKIN_SYSTEM.md#status-not-supported-yet).

User-installable **visual skins** for the sports scoreboards. Each
subdirectory is one skin:

```text
skins/<skin-id>/
  skin.json     # manifest
  skin.py       # renderer (a ScoreboardSkin subclass)
  preview.png   # optional
```

- Install a skin: `git clone <skin repo> skins/<skin-id>`. The Plugin Store
  refuses registry entries with `"type": "skin"` while skins don't render.
- Select it: set `"skin": "<skin-id>"` in the plugin's section of
  `config/config.json`. The web UI no longer shows a Visual Skin dropdown.
- Build one: start from `example-classic-baseball/` and read
  [docs/CREATING_SKINS.md](../docs/CREATING_SKINS.md). Validate with
  `python scripts/validate_skin.py --skin <skin-id>`.

Skins survive plugin reinstalls/updates (that's why they live here and not in
the plugin's directory). A skin is Python at the same trust level as a
plugin — review before installing.