// Use this when the user wants to improve README, docs pages, or microsites so a new reader can understand what the project is, how to use it, what artifacts exist, and what the scope boundaries are within one screen.
Use this when the user needs to choose between multiple ML routes after survey but before committing to implementation. Compares candidate approaches, selects one, records rejected routes, and keeps a fallback.
Use this when the project needs real baseline results before or alongside the main model. Runs classical or literature-aligned baselines under the same protocol and writes a reproducible baseline summary.
Use this when the project needs a dedicated data-quality review before model review. Checks data reality, split correctness, label health, leakage risk, shape consistency, and mock-data disclosure.
Use this when the user wants a draft paper, figure bundle, README, release page, or experiment artifact reviewed before sharing. Checks evidence binding, claim scope, captions, layout clarity, and release readiness.
Use this when the user wants to improve chart quality, standardize plotting style, regenerate release figures, or add captions/protocol notes. Normalizes fonts, colors, legends, units, and scope notes across Scientify figures.
[Read when prompt contains /research-experiment]
| name | release-layout |
| description | Use this when the user wants to improve README, docs pages, or microsites so a new reader can understand what the project is, how to use it, what artifacts exist, and what the scope boundaries are within one screen. |
| metadata | {"openclaw":{"emoji":"🪄"}} |
Don't ask permission. Just do it.
Use this skill for outward-facing packaging surfaces such as:
README.mddocs/index.htmlThis skill improves structure and legibility. It does not upgrade the scientific claim on its own.
A first-time reader should understand, within one screen:
If a page is generated by a script, prefer editing the generator rather than the built HTML.
If review/release_gate.json exists, read it before polishing release-facing copy.
Check whether the hero / opening section answers the four core questions above.
Prefer this order:
Use references/page-structure.md.
Reduce:
HOLD, stale, or missing for a share-ready artifact set, do not present the project as fully ready to share.