release-notes-one-pager
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.
Profile →npx skills add nexu-io/open-design --skill release-notes-one-pager --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Release Notes One-Pager Skill Produce a single-page release notes document in HTML. ## Resource map ``` 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. ## Workflow ### Step 0 — Pre-flight 1. Read `assets/template.html`. 2. Read `references/layouts.md`. 3. Read active `DESIGN.md` and map it to the six `:root` variables. ### Step 1 — Start from the shared seed Copy `assets/template.html` to project `index.html`. Update: - `<title>` - topnav logo text - topnav link labels (destinations are pre-wired to `#added`, `#fixed`, `#upgrade-note`) - topnav CTA label and `href` destination, or omit the topnav CTA entirely if no real destination exists - ensure the topnav link targets exist by adding matching section `id` attributes ### Step 2 — Build release-note structure Inside `<main id="content">`, compose this section order: 1. Hero (Layout 1 or 2): version, date, one-senten
- Resource map
- Workflow
- Step 0 — Pre-flight
- Step 1 — Start from the shared seed
- Step 2 — Build release-note structure
- Step 3 — Honesty rules for missing details
- Step 4 — Self-check
- Step 5 — Emit artifact
What does the release-notes-one-pager skill do?
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.
How do I install it?
Run `npx skills add nexu-io/open-design --skill release-notes-one-pager --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.