技能库智客分类：Agent 工作流 release-notes-one-pager

Release Notes One Pager

带有亮点的一页 HTML, 添加,固定, 突破了变化,已知问题,升级说明. 只要用户不提供细节,就写出明确的"无"样式部分.

官方网址：GitHub

技能介绍

先看中文介绍；官方 description 原文单独保留，不改写 SKILL.md。

做什么

带有亮点的一页 HTML, 添加,固定, 突破了变化,已知问题,升级说明. 只要用户不提供细节,就写出明确的"无"样式部分.

何时用

官方 description 未单独写出 Use when。按规范，代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露：启动时只加载 name 与 description（约 100 token）；任务匹配后才读入整份 SKILL.md 正文；scripts/、references/、assets/ 仅在需要时再读。本文件正文结构：Release Notes One-Pager Skill、Resource map、Workflow、Step 0 — Pre-flight、Step 1 — Start from the shared seed、Step 2 — Build release-note structure。其中含规范建议的小节：分步指令。

文件分析

文件分析：除 SKILL.md 外，正文引用了 assets/template.html、references/layouts.md、references/checklist.md，属于带资源的技能包，这些文件按需再读。

官方 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.

Release Notes One-Pager SkillResource mapWorkflowStep 0 — Pre-flightStep 1 — Start from the shared seedStep 2 — Build release-note structureStep 3 — Honesty rules for missing detailsStep 4 — Self-checkStep 5 — Emit artifact

来源分类：GitHub skill

来源与网址

市场来源：GitHub

开源榜 Skill 分类

SKILL.md 与 Agent 调用

官方规范 ↗

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.

发现技能客户端向 Agent 提供名称与描述目录。
匹配与调用用户指定或任务匹配后，载入 SKILL.md 指令。
按需加载按步骤读取参考文档、使用脚本与素材。

指令中引用的文件 · 3

assets/template.html
references/layouts.md
references/checklist.md

以下路径提取自原文；文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围，保留技能包的附属文件，安装后检查客户端能否发现该技能。

该技能引用了附属文件，请从来源获取完整目录；仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理，确认其中的目标目录与客户端匹配。

把 Agent Skill「release-notes-one-pager」安装到我的项目：SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-2000aeff9892bd6d-Release-Notes-One-Pager.html
请存为 .cursor/skills/release-notes-one-pager/SKILL.md 或 .claude/skills/release-notes-one-pager/SKILL.md，frontmatter 的 name 与 description 保持原样，不要改写。
该技能还带 scripts/、references/、assets/ 等文件，请从 https://github.com/nexu-io/open-design/tree/HEAD/skills/release-notes-one-pager 取完整目录，不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表，确认实际名称。

npx skills add 'https://github.com/nexu-io/open-design/tree/HEAD/skills/release-notes-one-pager' --list

目标客户端安装范围

npx skills add 'https://github.com/nexu-io/open-design/tree/HEAD/skills/release-notes-one-pager' --skill 'release-notes-one-pager'

CLI 会交互选择目标 Agent，默认安装到项目；用户级安装使用 -g。先通过查看命令核对仓库内容，再用 npx skills list 检查已安装技能。

SKILL.md 原文可复制，不会改动源文件

# 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-sentence summary.
2. Added (use Layout 7 log-list; section root must include `id="added"`).
3. Fixed (use Layout 7 log-list; section root must include `id="fixed"`).
4. Breaking changes (use Layout 7 log-list, or one row explicitly saying "None"; section root must include `id="breaking-changes"`).
5. Known issues (Layout 7 or card list; section root must include `id="known-issues"`).
6. Upgrade note (short steps list or explicit no-action statement; section root must include `id="upgrade-note"`).
7. 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>`.

阅读排版

--- 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 platform: desktop scenario: engineering preview: type: html entry: index.html design_system: requires: true sections: [color, typography, layout, components] 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 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: - `

Release Notes One Pager

技能介绍

做什么

何时用

代理如何加载

文件分析

SKILL.md 与 Agent 调用

安装这个技能

相关技能

Skill Creator

Clawdhub

Agent Team Orchestration

Superpowers