CtrlK
BlogDocsLog inGet started
Tessl Logo

curate-whats-new

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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a tightly written, highly actionable curation skill with a clear sequenced procedure and concrete command/file guidance. The main gap is the absence of an explicit output-validation checkpoint in the workflow.

Suggestions

Add an explicit validation step in the Procedure (e.g., confirm data/whats-new.json is valid JSON and that required fields are present on every item) before reporting, which would also satisfy the batch-operation feedback-loop expectation.

Consider moving the detailed Exclusions catalog into a short reference file (e.g., references/exclusions.md) and summarizing the principle inline, to reduce body length and improve progressive disclosure.

Clarify in step 6 how to detect and handle an existing retained item whose source PRs have been amended or re-merged, since the current instruction only says to reconsider featured status.

DimensionReasoningScore

Conciseness

The body is dense, directive prose with no explanation of concepts Claude already knows (no definition of Docker, PRs, or changelogs); every line states a curation rule or criterion that earns its place.

5 / 5

Actionability

It gives a concrete copy-ready command ("gh pr list --repo docker/docs --state merged --search 'merged:START..END' --limit 200"), a specific file to read and write, exact required item fields, and explicit output-format rules.

5 / 5

Workflow Clarity

An 8-step procedure with explicit review-mode branching and an empty-result fallback sequences the work clearly, and step 8's report acts as a review checkpoint; however there is no explicit validation that the rewritten JSON is well-formed before finishing.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with clear section headers (Exclusions, Select highlights, Procedure) and no nested references, but at ~95 lines it is longer than the simple-skill threshold and the exclusion criteria are dense enough that a split reference could help.

4 / 5

Total

18

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, explicit about both capability and trigger conditions, and occupies a clearly distinct niche. Its only weakness is that the "what" centers on a single curated action rather than multiple concrete actions.

DimensionReasoningScore

Specificity

"Curate noteworthy Docker launches from documentation pull requests merged during a requested period" names a concrete, precisely bounded action, though it is essentially a single action rather than several, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

It explicitly answers both what ("Curate noteworthy Docker launches from documentation pull requests merged during a requested period") and when ("Use when generating or reviewing data/whats-new.json..."), with concrete trigger phrases.

5 / 5

Trigger Term Quality

"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" covers several natural niche phrases, with a few common variations (e.g. "changelog") absent.

4 / 5

Distinctiveness Conflict Risk

The Docker Docs What's new / whats-new.json niche is narrow with distinct triggers, making collision with unrelated skills unlikely.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
docker/docs
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.