CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

update-ci-images

Long-running orchestration to rebuild every Positron CI image (ubuntu24_04, rocky_8, rocky_9, debian, openSUSE15_6, SLES15_6, and postgres — each as a multi-arch amd64+arm64 manifest) at one new tag. The tag names the Node, primary Python and primary R versions baked into the images (`<node>-py<python>-r<r>`). Bumps whichever of the three changed, repoints every consumer at the new tag, dispatches the build workflows on the PR branch with bounded concurrency, monitors the runs, auto-fixes failures and retries, and leaves the PR open for human review once all 7 builds are green.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally well-structured long-running orchestration skill: fully phased, with preflight validation, per-root-cause retry budgets, explicit escalation criteria, and verified bundle scripts invoked by path. The deductions are localized — mangled command prose in one Phase 0 bullet, unstated mechanics (state file, trailer convention), and inlined troubleshooting history that belongs in a reference file.

Suggestions

Fix the Phase 0 Python bullet: the `uv python list --all-versions | grep cpython-<python>-` command is currently interleaved with the 'primary must also differ from every other Python in the image' prose, making the executable command unreadable — split into the command plus a separate note.

Move the 'Known failure patterns' section into references/troubleshooting.md and reference it one level deep from Phase 4, keeping the loop-time decision rules (transient vs real, stop conditions) inline.

Make the Phase 2 state file concrete (exact scratchpad path and format) and state the repo's PR/commit trailer convention instead of only naming it.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely repo-specific operational knowledge Claude cannot know (image names, selector pins, failure signatures, stop conditions) — not padded explanation of known concepts. But there are trimmable spots: the 'Known failure patterns' section carries historical narrative (e.g. the terra/GDAL/bookworm history and 'The Debian image is now trixie'), and several pinned version numbers (pyenv 3.13.0, conda 3.12.10, R 4.4.2/4.4.1) are time-sensitive state inline in Phase 0. Fits 'Efficient; minor instances of over-explanation that could be trimmed' — not the every-token-earns-its-place level of a 5.

4 / 5

Actionability

Mostly copy-paste executable: exact `gh auth status`, `git -C "$REPO" switch -c update-images/<tag>`, curl HEAD-request checks, `bash <dir>/scripts/dispatch-job.sh <branch> <tag> [os]`, `gh api -X PATCH repos/<owner>/<repo>/pulls/<n> -f body=...`. Minor gaps keep it below 5: Phase 2's state file has no concrete path or mechanism ('Create a state file in the scratchpad'), 'Commit the end-of-message PR/commit trailer convention used in this repo' never states what that convention is, and the Phase 0 Python bullet is mangled — prose ('The primary must also differ from every other Python in the image...') is interleaved inside the `uv python list --all-versions ... | grep cpython-<python>-` command, so the executable command cannot be read cleanly.

4 / 5

Workflow Clarity

Phases 0–5 are an explicitly sequenced orchestration with validation up front ('Run and confirm all pass before changing anything', 'Verify each version that changes exists before you burn build minutes'), explicit feedback loops (Phase 4 diagnose → classify by failure signature → fix → re-dispatch), bounded retry budgets per root cause, unambiguous stop conditions ('fix_attempts reaches 3 for the same failure signature... OR transient_retries reaches 5'), and checklists (PR checklist boxes, TodoWrite list mirroring the 7 jobs). This matches the level-5 anchor including error-recovery feedback loops and checklists.

5 / 5

Progressive Disclosure

Executable logic is correctly externalized: all 7 referenced scripts (bump-node-version.sh, bump-interpreter-versions.sh, bump-selector-pins.sh, retag-consumers.sh, bump-ppm-snapshot.sh, dispatch-job.sh, wait-for-runs.sh) exist in scripts/ and are invoked by path rather than inlined, and the body is well-sectioned with clear headers. Minor gap: the ~45-line 'Known failure patterns' subsection is decision-support detail that could live in a references/ file one level deep, leaving the body a leaner orchestration overview — 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

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

A highly specific, action-dense description for a narrow, well-defined niche with essentially no conflict risk. Its one real weakness is the absence of any 'Use when...' or equivalent trigger guidance, which caps the completeness dimension.

Suggestions

Add an explicit trigger clause, e.g. 'Use when asked to rebuild/update the Positron CI images or bump the Node/Python/R versions baked into them' — even though the skill has disable-model-invocation: true, an explicit 'when' makes the description self-contained and would lift completeness.

Add natural entry-phrase synonyms users would actually say ('update the CI images', 'bump the image versions', 'retag the images') to broaden trigger-term coverage.

Trim the parenthetical image-name enumeration in the first sentence (or move the version-tag format detail after the actions) so the opening sentence leads with the core capability.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: "rebuild every Positron CI image (ubuntu24_04, rocky_8, rocky_9, debian, openSUSE15_6, SLES15_6, and postgres — each as a multi-arch amd64+arm64 manifest) at one new tag", "Bumps whichever of the three changed, repoints every consumer at the new tag, dispatches the build workflows... monitors the runs, auto-fixes failures and retries, and leaves the PR open for human review". It even specifies the tag format (`<node>-py<python>-r<r>`). This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' and exceeds the level-4 anchor only in completeness of coverage, not kind.

5 / 5

Completeness

The 'what' is answered clearly and in detail (rebuild all 7 multi-arch images at one new tag, bump versions, repoint consumers, dispatch, monitor, auto-fix, leave PR open), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3 ('Has a clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

Natural terms a user would say are present: "rebuild", "CI image", "Node, primary Python and primary R versions", "new tag", "build workflows". Coverage is good for this niche but a few natural entry phrases are missing (e.g. "update the images", "bump Python/R in the CI images", "retag"), and there is no explicit trigger phrasing at all — fits 'Good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of a 5, and is well above the sparse/generic keyword levels of 2–3.

4 / 5

Distinctiveness Conflict Risk

The description names a clear niche with distinct triggers: "Positron CI image", the seven specific image names, the explicit `<node>-py<python>-r<r>` tag format, and "leaves the PR open for human review once all 7 builds are green". No other plausible skill would collide with these triggers — minimal conflict risk, matching the level-5 anchor.

5 / 5

Total

17

/

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

posit-dev/positron

Path

.claude/skills/update-ci-images/SKILL.md

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.