Create a single HTML page that organizes release highlights, additions, fixes, breaking changes, known issues, and upgrade guidance. Missing information is explicitly labeled, helping readers distinguish supplied details from information that was not provided.
Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note. Writes explicit "None" style sections whenever the user does not provide details.
release-notes-one-pager turns release details into a single HTML page. It starts with the version, date, and a short summary, followed by additions, fixes, breaking changes, known issues, and any actions needed when upgrading. It uses the included template and organizes the page so readers can follow internal links to individual sections.
Use it to share the changes in a new version with users or colleagues. It also works when only some release information is available. Missing details are explicitly identified, allowing you to prepare the document without filling gaps with guesses.
The workflow expects an existing DESIGN.md and reads it to apply colors and other design choices to the template. Missing information uses prescribed wording; versions and dates are never guessed. Linked buttons are included only when a real destination is available.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 20, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Produce a single-page release notes document in HTML.
release-notes-one-pager/
├── SKILL.md ← this file
├── example.html ← quality bar and style reference
├── assets/
│ └── template.html ← local seed file to copy to project index.html
└── references/
├── checklist.md ← P0 / P1 / P2 gates
└── layouts.md ← local section skeletons
Do not write CSS from scratch unless the user explicitly asks for a bespoke structure.
assets/template.html.references/layouts.md.DESIGN.md and map it to the six :root variables.Copy assets/template.html to project index.html.
Update:
<title>#added, #fixed, #upgrade-note)href destination, or omit the topnav CTA entirely if no real destination existsid attributesInside <main id="content">, compose this section order:
id="added").id="fixed").id="breaking-changes").id="known-issues").id="upgrade-note").For every CTA in the emitted HTML (topnav, hero, closing strip), replace both the visible label and the href destination with real, safe values. If no real destination is available, omit the CTA entirely—do not use a placeholder such as href="#", a misleading page-anchor, or REPLACE_WITH_REAL_URL. Hero CTAs are optional; only add them when real destinations exist.
If the user does not provide details, do not invent them. Write explicit placeholders:
No summary provided.No additions providedNo fixes providedNoneNone reportedNo upgrade actions required based on provided informationIf release version or date is missing, use — and label the field rather than guessing.
Run references/checklist.md. Every P0 must pass.
Wrap output as:
<artifact identifier="release-notes-one-pager" type="text/html" title="Release Notes">
<!doctype html>
<html>...</html>
</artifact>
One sentence before the artifact. Nothing after </artifact>.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a three-scene video composition in a retro pixel style using a Hyperframes HTML template. Customize titles, labels, and colors while preserving scene transitions, short scene durations, and repeatable animation timing.
Create and revise headlines, descriptions, and main text for paid social and search ads. Use it to develop ad copy options and refine wording through repeated rounds of revision.
Create a three-page editorial motion sequence with dark backgrounds, serif typography, staged text reveals, and chapter transitions. The result is a single HTML file suited to fashion-inspired storytelling and short visual presentations.
Inspect and test web pages through a browser automation command-line tool. Navigate, click, enter text, capture screenshots, and extract page details, with a focus on checking local OpenDesign previews and reviewing web app quality.
Plan an AI music album from its concept through lyric drafts, track order, and export. Intended for independent album experiments and brand soundtracks, with the full production workflow provided through a separately installed upstream bundle.
Create generative art, or images made with programmed rules, using p5.js. Fixed random seeds make each rendering reproducible, supporting procedural posters, still images that suggest motion, and studies of artistic frame composition.