Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note.
Install Release Notes One Pager
$ npx skills add nexu-io/open-design --skill release-notes-one-pager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nexu-io/open-design release-notes-one-pager --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release-notes-one-pager .claude/skills/release-notes-one-pager && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-notes-one-pager" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/release-notes-one-pager into .claude/skills/release-notes-one-pager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-one-pager", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nexu-io/open-design/tree/main/skills/release-notes-one-pagerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nexu-io/open-design --skill release-notes-one-pager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nexu-io/open-design release-notes-one-pager --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/release-notes-one-pager .agents/skills/release-notes-one-pager && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-notes-one-pager" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/release-notes-one-pager into .agents/skills/release-notes-one-pager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-one-pager", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nexu-io/open-design --skill release-notes-one-pager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nexu-io/open-design release-notes-one-pager --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/release-notes-one-pager .cursor/skills/release-notes-one-pager && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-notes-one-pager" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/release-notes-one-pager into .cursor/skills/release-notes-one-pager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-one-pager", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nexu-io/open-design.git --path skills/release-notes-one-pager--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nexu-io/open-design --skill release-notes-one-pager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nexu-io/open-design release-notes-one-pager --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/release-notes-one-pager .gemini/skills/release-notes-one-pager && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-notes-one-pager" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/release-notes-one-pager into .gemini/skills/release-notes-one-pager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-one-pager", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nexu-io/open-design release-notes-one-pagerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nexu-io/open-design --skill release-notes-one-pager -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/release-notes-one-pager .github/skills/release-notes-one-pager && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-notes-one-pager" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/release-notes-one-pager into .github/skills/release-notes-one-pager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-one-pager", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nexu-io/open-design --skill release-notes-one-pager -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nexu-io/open-design release-notes-one-pager --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/release-notes-one-pager .opencode/skills/release-notes-one-pager && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-notes-one-pager" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/release-notes-one-pager into .opencode/skills/release-notes-one-pager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-one-pager", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-notes-one-pager- GitHub stars
- 100k
- Token cost
- ~920 tokens
- SKILL.md length
- 349 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 245
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note.
- Works in 6 steps: Pre-flight → Start from the shared seed → Build release-note structure → …
- Tasks that involve Changelog and release notes
- SKILL.md covers Resource map and Workflow
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Release Notes One Pager is an agent skill from nexu-io/open-design. 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.
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `references/checklist.md` and `references/layouts.md`).
It sits in Development, covering Changelog and release notes. The repository describes itself as: 🎨 Best DeepSeek Harness Design Plugin. The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Changelog and release notes
Example prompts
- “/release-notes-one-pager”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit d9dd6fe. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Notes One Pager loads about 920 tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 349 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nexu-io/open-design at commit d9dd6fe, republished under its Apache-2.0 licence (© nexu-io). 349 words, ~920 tokens.
Download SKILL.mdSave it as
.claude/skills/release-notes-one-pager/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- release-notes-one-pager
- description
- 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.
- triggers
- release notes, changelog, what's new, version update, change log, release summary
- od.mode
- prototype
- od.platform
- desktop
- od.scenario
- engineering
- od.example_prompt
- Write release notes for v2.3.1 with Added, Fixed, Breaking changes, Known issues, and an Upgrade note.
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 skeletonsDo not write CSS from scratch unless the user explicitly asks for a bespoke structure.
Workflow
Step 0 — Pre-flight
- Read
assets/template.html. - Read
references/layouts.md. - Read active
DESIGN.mdand map it to the six:rootvariables.
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
hrefdestination, or omit the topnav CTA entirely if no real destination exists - ensure the topnav link targets exist by adding matching section
idattributes
Step 2 — Build release-note structure
Inside <main id="content">, compose this section order:
- Hero (Layout 1 or 2): version, date, one-sentence summary.
- Added (use Layout 7 log-list; section root must include
id="added"). - Fixed (use Layout 7 log-list; section root must include
id="fixed"). - Breaking changes (use Layout 7 log-list, or one row explicitly saying "None"; section root must include
id="breaking-changes"). - Known issues (Layout 7 or card list; section root must include
id="known-issues"). - Upgrade note (short steps list or explicit no-action statement; section root must include
id="upgrade-note"). - Closing CTA strip (Layout 6).
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.
Step 3 — Honesty rules for missing details
If the user does not provide details, do not invent them. Write explicit placeholders:
- Summary:
No summary provided. - Added:
No additions provided - Fixed:
No fixes provided - Breaking changes:
None - Known issues:
None reported - Upgrade note:
No upgrade actions required based on provided information
If release version or date is missing, use — and label the field rather than guessing.
Step 4 — Self-check
Run references/checklist.md. Every P0 must pass.
Step 5 — Emit artifact
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>.
© nexu-io, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references, assets) in skills/release-notes-one-pager of nexu-io/open-design.
- SKILL.md
- assets/template.html
- example.html
- references/checklist.md
- references/layouts.md
Open the folder on GitHubat commit d9dd6fe
Compare with similar skills
Release Notes One Pager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Notes One Pager this skillnexu-io/open-design | 100k | — | ~920 | Automated safety check: Pass | Apache-2.0 | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 |
Similar skills
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
More from nexu-io/open-design
All 245 skills in this repoHumanize PPT
nexu-io/open-design
Turns raw notes into a talk-ready slide outline with per-page image, diagram or video decisions, then checks the rendered deck against that outline.
Last 30 Days Trend Research
nexu-io/open-design
Produces a cited Markdown briefing on recent community sentiment and social reaction to a topic, labeling every source it could not actually check.
OpenDesign Contribution Flow
nexu-io/open-design
Helps newcomers contribute to OpenDesign: ship a skill or design system, translate docs, fix docs or report a bug, ending in a pull request or issue.
Chat Motion Overlay Generator
nexu-io/open-design
Turns a chat transcript or screenshot into a configurable animated chat clip, rendered as a Remotion bundle with optional transparency.
Flowai Live Dashboard Template
nexu-io/open-design
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity…
Hatch Pet
nexu-io/open-design
Create, repair, validate, preview, and package Codex-compatible animated pet spritesheets from character art, screenshots, generated images, or visual references.
Related
Categories
Questions about Release Notes One Pager
What does Release Notes One Pager do?
Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note. Release Notes One Pager is an agent skill from nexu-io/open-design. Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note.
When should I use Release Notes One Pager?
Release Notes One Pager fits situations like: tasks that involve Changelog and release notes.
How do I install Release Notes One Pager in Claude Code?
Run `npx skills add nexu-io/open-design --skill release-notes-one-pager -a claude-code`. Or copy the skill folder (skills/release-notes-one-pager in nexu-io/open-design) into .claude/skills/release-notes-one-pager in your project. Claude Code loads it when a task matches its description.
How do I install Release Notes One Pager in Codex?
Run `npx skills add nexu-io/open-design --skill release-notes-one-pager -a codex`. Or copy the skill folder (skills/release-notes-one-pager in nexu-io/open-design) into .agents/skills/release-notes-one-pager in your project. Codex loads it when a task matches its description.
Can I use Release Notes One Pager in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nexu-io/open-design --skill release-notes-one-pager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-notes-one-pager, .gemini/skills/release-notes-one-pager, .github/skills/release-notes-one-pager and .opencode/skills/release-notes-one-pager in your project.
What does Release Notes One Pager need to run?
SKILL.md names no scripts, command-line tools or credentials: Release Notes One Pager is instructions for the agent only.
Does Release Notes One Pager access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Notes One Pager safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Notes One Pager use?
Release Notes One Pager is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Notes One Pager use?
About 920 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.
What are the alternatives to Release Notes One Pager?
Skills that share tags, products or a category with Release Notes One Pager: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Notes One Pager?
nexu-io (a GitHub organization) maintains it in nexu-io/open-design, which has 100,100 GitHub stars. The repository holds 245 skills in this directory. The repository was last updated on October 9, 2026.
Source: nexu-io/open-design on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.