Release
Pipelex/pipelex
Cut a release of pipelex, which ships the pipelex and pipelex-api packages and the pipelex/pipelex-api Docker image under one version: the gates, the migration-ledger cross-check, the CHANGELOG.md…
Curate noteworthy Docker launches from documentation pull requests merged during a requested period.
Install Curate Whats New
$ npx skills add docker/docs --skill curate-whats-new -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install docker/docs curate-whats-new --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/curate-whats-new .claude/skills/curate-whats-new && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "curate-whats-new" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/curate-whats-new into .claude/skills/curate-whats-new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "curate-whats-new", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/docker/docs/tree/main/.agents/skills/curate-whats-newType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add docker/docs --skill curate-whats-new -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install docker/docs curate-whats-new --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/curate-whats-new .agents/skills/curate-whats-new && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "curate-whats-new" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/curate-whats-new into .agents/skills/curate-whats-new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "curate-whats-new", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add docker/docs --skill curate-whats-new -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install docker/docs curate-whats-new --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/curate-whats-new .cursor/skills/curate-whats-new && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "curate-whats-new" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/curate-whats-new into .cursor/skills/curate-whats-new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "curate-whats-new", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/docker/docs.git --path .agents/skills/curate-whats-new--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add docker/docs --skill curate-whats-new -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install docker/docs curate-whats-new --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/curate-whats-new .gemini/skills/curate-whats-new && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "curate-whats-new" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/curate-whats-new into .gemini/skills/curate-whats-new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "curate-whats-new", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install docker/docs curate-whats-newInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add docker/docs --skill curate-whats-new -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/curate-whats-new .github/skills/curate-whats-new && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "curate-whats-new" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/curate-whats-new into .github/skills/curate-whats-new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "curate-whats-new", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add docker/docs --skill curate-whats-new -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install docker/docs curate-whats-new --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/curate-whats-new .opencode/skills/curate-whats-new && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "curate-whats-new" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/curate-whats-new into .opencode/skills/curate-whats-new/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "curate-whats-new", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
curate-whats-new- GitHub stars
- 4.7k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 688 words
- Files
- 2
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Curate noteworthy Docker launches from documentation pull requests merged during a requested period.
- Works in 8 steps: Read data/whats-new.json. → Determine the review mode from the request → List PRs in the range that applies to… → …
- Reviewing data/whats-new.json
- SKILL.md covers Exclusions, Select highlights and Procedure
- Calls gh
What it does
Curate Whats New is an agent skill from docker/docs, published by the product's own GitHub organization. Curate noteworthy Docker launches from documentation pull requests merged during a requested period. Use when generating or reviewing data/whats-new.json, preparing the Docker Docs What's new timeline, or deciding which documented releases merit Docker-wide highlights.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Changelog and release notes, Containers and Pull requests. It works with Docker. The repository describes itself as: Source repo for Docker's Documentation. The licence is Apache-2.0.
When your agent uses it
- Reviewing data/whats-new.json
- Preparing the Docker Docs Whats new timeline
- Deciding which documented releases merit Docker-wide highlights
Example prompts
- “/curate-whats-new”
Requirements
- Docker
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Read data/whats-new.json.
- Determine the review mode from the request
- List PRs in the range that applies to the review mode
- Inspect the diff and resulting pages for every plausible new candidate.
- Decide what qualifies using only evidence in the merged documentation.
- Remove existing items published before the requested publication window.
- Replace period_start, period_end, and items in
- Report the curation outcome in the response
What it can do on your machine
Read from SKILL.md and the folder at commit 8582516. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Curate Whats New loads about 1.3k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 688 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from docker/docs at commit 8582516, republished under its Apache-2.0 licence (© docker). 688 words, ~1,295 tokens.
Download SKILL.mdSave it as
.claude/skills/curate-whats-new/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- curate-whats-new
- description
- Curate noteworthy Docker launches from documentation pull requests merged during a requested period. Use when generating or reviewing data/whats-new.json, preparing the Docker Docs What's new timeline, or deciding which documented releases merit Docker-wide highlights.
Curate What's New
Treat merged documentation as evidence that a capability shipped, but do not treat a documentation change as news by itself.
Include an item only when the merged documentation directly shows all of the following:
- A released user-facing feature, material enhancement, or broader availability milestone that was not available before the period
- A substantial capability or workflow, not new syntax or a small control within an existing workflow
- Enough Docker-wide editorial significance to merit proactively telling users about it outside product release notes
- A useful published page and a factual title and description
Apply a high bar. The result is a curated launch archive, not a complete changelog. A specialized feature can qualify when its user impact is substantial. A quiet period can produce few or no items.
Exclusions
Exclude documentation maintenance; fixes; rewrites; guidance for old behavior; routine release or generated-content syncs; limitations, prerequisites, and workarounds; narrow flags, settings, command variants, protocols, and compatibility changes; incremental UI, safety, permissions, or observability improvements; and lower-level Engine, Build, networking, or storage changes. These qualify only when they are part of an independently newsworthy product-level launch.
Judge the user outcome, not PR size, product popularity, labels, changed lines, a dedicated page, or the existence of a new API or command.
Select highlights
Include every qualifying launch; do not impose a quota. Mark the five most
important as featured: true, or all items when fewer than five qualify. Rank
by the magnitude and distinctness of the user outcome and the value of helping
its audience discover it. Breadth can matter, but a major capability for a
specialized audience can outrank a smaller change for a broad audience. Recency
and product variety are not ranking goals.
Create one item per launch and combine PRs that document the same launch. Preserve existing copy while it remains accurate and qualifies. Change featured status only when the relative importance of the candidate set changes.
Show full SKILL.md (381 more words)Show less
Procedure
Read
data/whats-new.json.Determine the review mode from the request:
- If the request does not specify a publication window, end it on the previous UTC day and start it 29 days earlier.
- For an incremental review, list PRs merged from the day after the supplied
checkpoint through the end of the publication window. Retain existing
items inside the publication window without re-reviewing their source PRs.
If the request does not supply a checkpoint, use the existing
period_endfromdata/whats-new.json. - For a full review, inspect every PR merged in the supplied publication window.
List PRs in the range that applies to the review mode:
console $ gh pr list --repo docker/docs --state merged --search 'merged:START..END' --limit 200If an incremental search returns no PRs, skip candidate inspection and only remove expired items.
Inspect the diff and resulting pages for every plausible new candidate.
Decide what qualifies using only evidence in the merged documentation.
Remove existing items published before the requested publication window. Add newly qualifying launches, combine related PRs, and reconsider featured status across the resulting list. Do not replace or rewrite retained items merely because they were not part of the incremental candidate range.
Replace
period_start,period_end, anditemsindata/whats-new.json. Sort items bypublisheddate, newest first.Report the curation outcome in the response:
- Enumerate every newly selected entry by product, title, and source PRs.
- Summarize retained and expired entries by count. Identify any retained entry whose content or sources changed.
- Explain only the most relevant plausible exclusions. Do not enumerate routine maintenance PRs that were never credible candidates.
If the request includes creating a pull request, use the same report in the PR
body with ## Summary, ## Selected entries, and ## Curation notes
sections. Put each selected entry on one Markdown bullet and reference PRs as
#NNNN rather than full same-repository links. Do not hard-wrap bullets. Do
not create .pr-body.md or another handoff file unless the request explicitly
asks for one.
Each item must contain product, title, description, url, published,
source_prs, and featured. Use the canonical product name, a published
internal URL, the merge date in YYYY-MM-DD format, and source PR numbers.
Write factual, restrained copy. Avoid superlatives, promotional language, and
claims about ease or importance. Do not modify tracked files other than
data/whats-new.json.
© docker, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/curate-whats-new of docker/docs.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 8582516
Compare with similar skills
Curate Whats New next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Curate Whats New this skilldocker/docs | 4.7k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| ReleasePipelex/pipelex | 941 | — | ~4.8k | Automated safety check: Notes | Custom licence | |
| CI Act Runchewiebug/GCViewer | 4.6k | — | ~2.4k | Automated safety check: Notes | Custom licence | |
| Review PRmicrosoft/vscode-containers | 141 | — | ~900 | Automated safety check: Pass | Custom licence | |
| Project Docs Maintainerswimmwatch/cloakbrowser-mcp | 164 | — | ~569 | Automated safety check: Pass | MIT | |
| Prepare Releasejpicklyk/task-orchestrator | 207 | — | ~5.3k | Automated safety check: Pass | MIT |
Similar skills
CI Act Run
chewiebug/GCViewer
Run the full build-and-deploy.yaml workflow locally via act + Docker.
- Official
Review PR
microsoft/vscode-containers
Review a specific vscode-containers pull request on demand from the CLI (or any interactive agent), the way a Container Tools maintainer would.
Project Docs Maintainer
swimmwatch/cloakbrowser-mcp
Maintain, organize, consolidate, or audit the cloakbrowser-mcp documentation set only when the user explicitly requests project documentation maintenance or an authorized public change requires it.
Prepare Release
jpicklyk/task-orchestrator
End-to-end release automation — reads commits since last tag, infers semver bump, drafts changelog, creates release PR, merges it, waits for CI green, tags, and monitors the Docker build to…
- Official
Code Review
Azure/Azurite
Review Azurite pull requests with service-aware checks for Blob, Queue, and Table behavior, API compatibility, tests, and release notes.
More from docker/docs
All 13 skills in this repo- Official
Agent Readiness Audit
docker/docs
Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility.
- Official
Migrate Content Ia
docker/docs
Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…
- Official
Write
docker/docs
Write or edit reader-facing technical prose for immediate comprehension.
- Official
Create Lab Guide
docker/docs
Clone a dockersamples Labspace repo, extract learning objectives and module structure from labspace.yaml, and produce a Hugo guide page under content/guides/ with correct frontmatter…
- Official
Fix Issue
docker/docs
Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR.
- Official
Maintain PR
docker/docs
Maintain and follow up on a single Docker documentation pull request that you own or are responsible for updating.
Related
Works with
Categories
Questions about Curate Whats New
What does Curate Whats New do?
Curate noteworthy Docker launches from documentation pull requests merged during a requested period. Curate Whats New is an agent skill from docker/docs, published by the product's own GitHub organization. Curate noteworthy Docker launches from documentation pull requests merged during a requested period.
When should I use Curate Whats New?
Curate Whats New fits situations like: reviewing data/whats-new.json; preparing the Docker Docs Whats new timeline; deciding which documented releases merit Docker-wide highlights.
How do I install Curate Whats New in Claude Code?
Run `npx skills add docker/docs --skill curate-whats-new -a claude-code`. Or copy the skill folder (.agents/skills/curate-whats-new in docker/docs) into .claude/skills/curate-whats-new in your project. Claude Code loads it when a task matches its description.
How do I install Curate Whats New in Codex?
Run `npx skills add docker/docs --skill curate-whats-new -a codex`. Or copy the skill folder (.agents/skills/curate-whats-new in docker/docs) into .agents/skills/curate-whats-new in your project. Codex loads it when a task matches its description.
Can I use Curate Whats New in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add docker/docs --skill curate-whats-new -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/curate-whats-new, .gemini/skills/curate-whats-new, .github/skills/curate-whats-new and .opencode/skills/curate-whats-new in your project.
What does Curate Whats New need to run?
Going by SKILL.md and its folder, Curate Whats New needs the command-line tools its instructions call (gh). Our summary lists: Docker.
Does Curate Whats New access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Curate Whats New safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Curate Whats New use?
Curate Whats New is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Curate Whats New use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Curate Whats New?
Skills that share tags, products or a category with Curate Whats New: Release (Pipelex/pipelex, 941 stars), CI Act Run (chewiebug/GCViewer, 4.6k stars), Review PR (microsoft/vscode-containers, 141 stars) and Project Docs Maintainer (swimmwatch/cloakbrowser-mcp, 164 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Curate Whats New?
docker (a GitHub organization, an official publisher) maintains it in docker/docs, which has 4,667 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 8, 2026.
Source: docker/docs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.