release-notes-one-pager
Skill6 starsChanged 6 months agoApache-2.0View on GitHub
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.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- davidanthonyn/claude-skillsword for word, first seen Oct 20, 2026
- jpoindexter/theft-kitword for word, first seen May 20, 2026
Other versions2 projects use a version of this.
Word for word · 2
- jpoindexter/theft-kit★ 1100% same
- davidanthonyn/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository169 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apps/AGENTS.mdAGENTS.md
- design-templates/AGENTS.mdAGENTS.md
- e2e/AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- packages/AGENTS.mdAGENTS.md
- plugins/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- tools/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- od-contributeSkill
- 8-bit-orbit-video-templateSkill
- ad-creativeSkill
- after-hours-editorial-templateSkill
- agent-browserSkill
- ai-music-albumSkill
- algorithmic-artSkill
- apple-higSkill
- article-magazineSkill
- artifacts-builderSkill
- brainstormingSkill
- brand-extractSkill
- brand-guidelinesSkill
- brandkitSkill
- industrial-brutalist-uiSkill
- canvas-designSkill
- card-twitterSkill
- card-xiaohongshuSkill
- color-expertSkill
- competitive-ads-extractorSkill
- copywritingSkill
- creative-directorSkill
- d3-visualizationSkill
- data-reportSkill
- deck-guizang-editorialSkill
- deck-open-slide-canvasSkill
- deck-swiss-internationalSkill
- design-briefSkill
- design-consultationSkill
- design-mdSkill
- design-reviewSkill
- digits-fintech-swiss-templateSkill
- doc-kami-parchmentSkill
- docSkill
- docxSkill
- domain-name-brainstormerSkill
- ecommerce-image-workflowSkill
- editorial-burgundy-principles-templateSkill
- emilkowalski-motionSkill
- enhance-promptSkill
- export-download-debuggingSkill
- fal-3dSkill
- fal-generateSkill
- fal-image-editSkill
- fal-kling-o3Skill
- fal-lip-syncSkill
- fal-realtimeSkill
- fal-restoreSkill
- fal-trainSkill
- fal-tryonSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Do not write CSS from scratch unless the user explicitly asks for a bespoke structure.
- Very specific: line 52
Read active DESIGN.md and map it to the six :root variables.
- Very specific: line 63
ensure the topnav link targets exist by adding matching section id attributes
- Distinctive: line 81
If the user does not provide details, do not invent them.
- Very specific: line 90
If release version or date is missing, use — and label the field rather than guessing.
- Very specific: line 94
Run references/checklist.md.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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>.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

