skillboardUpdated every 6 hours
skillboardRelease 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.
Produce a single-page release notes document in HTML.
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.
assets/template.html.references/layouts.md.DESIGN.md and map it to the six :root variables.Copy assets/template.html to project index.html.
Update:
<title>#added, #fixed, #upgrade-note)href destination, or omit the topnav CTA entirely if no real destination existsid attributesInside <main id="content">, compose this section order:
id="added").id="fixed").id="breaking-changes").id="known-issues").id="upgrade-note").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.
If the user does not provide details, do not invent them. Write explicit placeholders:
No summary provided.No additions providedNo fixes providedNoneNone reportedNo upgrade actions required based on provided informationIf release version or date is missing, use — and label the field rather than guessing.
Run references/checklist.md. Every P0 must pass.
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>.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/release-notes-one-pager · pinned to the source commit
# Run from your project root
git clone https://github.com/nexu-io/open-design.git .skillboard-tmp
git -C .skillboard-tmp checkout 9881cff70e02be86c2a58130af512011ba23d4af
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/release-notes-one-pager" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/nexu-io/open-design.git .skillboard-tmp
git -C .skillboard-tmp checkout 9881cff70e02be86c2a58130af512011ba23d4af
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/release-notes-one-pager" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/release-notes-one-pager
Scanner static-checks@0.1.0 · commit 9881cff70e02. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.