Auto-invokedSkill
od-contribute
One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD;…
@nexu-ioView Skill/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.
Install
$ npx -y skills add nexu-io/open-design --skill release-notes-one-pager --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/release-notes-one-pager
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
release-notes-one-pager.SKILL.mdname: 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 skeletonsDo 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>`.
Read more
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 skeletonsDo 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>`.
Ships withopen-design
🎨 Best DeepSeek Harness Design Plugin. The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes, landing pages, dashboards, slides, images & video — real files, HTML/PDF/PPTX/MP4 export. 🤖 Claude Code / Codex / Cursor / DeepSeek Harness / OpenCode & 20+ CLIs via BYOK.
Get the whole plugin, auto-invoked
Stats
95,466
Stars
11,063
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
4d ago
Last commit
4mo ago
Created
Repo: nexu-io/open-design
Other skills on open-design.
@nexu-ioView SkillAuto-invokedSkill
8-bit-orbit-video-temp…
Hyperframes-based video template for retro pixel deck motion design. Use when users want a high-fidelity, multi-scene HTML-to-video composition with advanced…
@nexu-ioView SkillAuto-invokedSkill
ad-creative
Generate and iterate ad creative including headlines, descriptions, and primary text. Useful for paid social and search ad iteration.
@nexu-ioView SkillAuto-invokedSkill
after-hours-editorial-…
Luxury dark-editorial HyperFrames template for three-page cinematic storyboards, inspired by haute couture title cards and magazine chapter spreads. Use when…
@nexu-ioView SkillAuto-invokedSkill
agent-browser
Browser automation CLI for AI agents. Use when the user needs to inspect, test, or automate browser behavior: navigating pages, filling forms, clicking…
@nexu-ioView SkillAuto-invokedSkill
ai-music-album
Full-lifecycle AI music album production — concept, lyric drafting, track sequencing, and export. Useful for indie album experiments and brand soundtracks.
@nexu-ioView Skill