The direct answer
Create a data-only Codex skin package by separating visual intent from installation behavior. Put the theme name, allowed settings, background image, preview image, license, and digest metadata in the package. Keep scripts, executables, arbitrary CSS, and provider settings out.
Why data-only matters
A visual theme is easy to trust emotionally because it looks harmless. That is exactly why theme packages should be constrained. When a Codex skin package is data-only, a user can inspect it without executing it. If the package asks to run a command, the user has crossed from design into software.
This model also helps creators. They can share artwork and composition decisions without becoming responsible for platform-specific installers. Installation can remain in a reviewed engine with its own release notes and restore flow.
Recommended package contents
A practical Codex skin package should be small, readable, and boring. The manifest identifies the format and package. The theme JSON stores allowlisted visual values. The background and preview are compressed images. The license explains rights. The digest metadata helps detect accidental changes.
If different assets have different terms, list them file by file. Do not hide a rights problem behind a broad license.
- manifest.json for package identity and format.
- theme.json for allowlisted visual settings.
- background.webp for the optimized artwork.
- preview.webp for quick inspection.
- LICENSE.txt for use, modification, and redistribution terms.
- signature.json or digest metadata for integrity context.
What to reject
Reject packages that include shell scripts, PowerShell scripts, compiled binaries, arbitrary CSS injection, encoded payloads, app bundle patches, API settings, provider URLs, or instructions that bypass the reviewed installer. Those may be legitimate software in another context, but they should not be disguised as a skin.
Also reject packages that use celebrity photos, fan art, logos, or character art without documented rights. A theme marketplace cannot work if rights review is treated as an afterthought.
How to make the package useful
Include three previews: Home, Task, and Diff. Add a short summary explaining the intended use case, such as low-light focus, warm personal workspace, or high-contrast review mode. Mention tested Codex version and platform status. These details make the package easier to evaluate without adding executable complexity.
Final recommendation
A data-only Codex skin package is the right default for a public gallery. It lets users inspect the visual idea, apply it through trusted tooling, and reject unsafe additions quickly.
FAQ
Can a data-only Codex skin install itself?
No. That is the point. Installation should belong to reviewed tooling, not to the theme package.
Should a Codex skin package include a license?
Yes. The license should explain whether others may use, modify, redistribute, or sell the theme and its assets.