Back to browse

nexu-io/open-design

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.

77Collecting
See how to use itView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "skills/release-notes-one-pager"
Automated source guideDeploymentStandard source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded deployment guide: release-notes-one-pager

Produce a single-page release notes document in HTML.

npx skills add https://github.com/nexu-io/open-design --skill "skills/release-notes-one-pager"
Check the pinned source

The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.

416 source words · 8 usable sections

Deployment workflow

Read release-notes-one-pager through these 4 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

Workflow

1. Read assets/template.html. 2. Read references/layouts.md. 3. Read active DESIGN.md and map it to the six :root variables.

SKILL.md · Workflow
Read assets/template.html.Read references/layouts.md.Read active DESIGN.md and map it to the six :root variables.
02

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.

SKILL.md · Step 0 — Pre-flight
Read assets/template.html.Read references/layouts.md.Read active DESIGN.md and map it to the six :root variables.
03

Step 1 — Start from the shared seed

Copy assets/template.html to project index.html.

SKILL.md · Step 1 — Start from the shared seed
topnav logo texttopnav 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
04

Step 2 — Build release-note structure

Inside , compose this section order:

SKILL.md · Step 2 — Build release-note structure
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").

Release checklist

Verify each item before delivery

The source section “Workflow” has been checked.

The source section “Step 0 — Pre-flight” has been checked.

The source section “Step 1 — Start from the shared seed” has been checked.

The source section “Step 2 — Build release-note structure” has been checked.

Choose a different workflow

When another Skill is the better fit

mle-workflow

Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

simpy

Build, inspect, test, and analyze bounded process-based discrete-event simulations with SimPy, including events, resources, interrupts, monitoring, replications, warm-up, and reproducible output analysis.

A separate implementation from K-Dense-AI/scientific-agent-skills; compare its source, maintenance signals, and permission requirements.

Open source detail

suede-code-grader

Give a blunt A-F ship grade for a code change across correctness, security, data, UX, verification, and deploy readiness. Use for a grade, not a findings review.

A separate implementation from JasonColapietro/suede-creator-skills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the release-notes-one-pager source document cover?

Produce a single-page release notes document in HTML.

How do I install release-notes-one-pager?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "skills/release-notes-one-pager". Inspect the command and pinned source before running it.

Repository stars
82,073
Repository forks
9,485
Quality
77/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

77/100
Documentation26/30
Specificity14/25
Maintenance20/20
Trust signals17/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

mle-workflow by affaan-m

Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.

simpy by k-dense-ai

Build, inspect, test, and analyze bounded process-based discrete-event simulations with SimPy, including events, resources, interrupts, monitoring, replications, warm-up, and reproducible output analysis.

suede-code-grader by JasonColapietro

Give a blunt A-F ship grade for a code change across correctness, security, data, UX, verification, and deploy readiness. Use for a grade, not a findings review.

terragrunt by event4u-app

Use when working with Terragrunt — DRY multi-env configs, module dependencies, remote state orchestration — even when the user just says 'deploy this to staging and prod' without naming Terragrunt.

brand-landingpage by wshobson

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens —

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 2 min

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

Skill path
skills/release-notes-one-pager/SKILL.md
Commit SHA
89d6d4ef21ba
Repository license
Apache-2.0
Data collected