CtrlK
BlogDocsLog inGet started
Tessl Logo

update-v8-version

Update Codex's pinned `v8` / `rusty_v8` versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update `rusty_v8` artifacts, prepare or validate a V8 release candidate, check `v8-canary`, or diagnose why a V8 version update no longer builds.

80

Quality

100%

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

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

A concise, fully actionable skill body with a clearly sequenced workflow, explicit validation checkpoints, and a recovery feedback loop. It points to the in-repo source of truth rather than duplicating it and is well organized for a single-purpose skill.

DimensionReasoningScore

Conciseness

Lean and efficient — assumes Claude's competence, references the in-repo README as source of truth rather than re-explaining the release process, and every section earns its place with no padding.

5 / 5

Actionability

Provides concrete, copy-paste-ready commands (the python3 checksum-helper invocations and unittest discovery) plus explicit file paths for every surface to inspect, covering the common cases.

5 / 5

Workflow Clarity

A clearly numbered core workflow with an explicit validation checkpoint (step 4 validates the release-candidate path) and a separate failure path with a feedback loop (re-run focused validation, return to normal workflow when green).

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external bundle files — the body is a well-organized overview split into Core Workflow / Failure Path / Reporting sections, satisfying the simple-skill exception.

5 / 5

Total

20

/

20

Passed

Description

100%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, well-structured description that clearly states both capabilities and trigger conditions in third person. It reads naturally as something a user would say and is tightly scoped to a distinct niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Update Codex's pinned v8 / rusty_v8 versions', 'validate the release-candidate path', 'investigate failed V8 canary or artifact builds' — covering the full workflow comprehensively.

5 / 5

Completeness

Explicitly answers both 'what' (the three actions above) and 'when' via a clear 'Use when...' clause enumerating concrete trigger scenarios.

5 / 5

Trigger Term Quality

Includes natural user phrasings and synonyms — 'bump V8', 'update rusty_v8 artifacts', 'prepare or validate a V8 release candidate', 'check v8-canary', 'diagnose why a V8 version update no longer builds'.

5 / 5

Distinctiveness Conflict Risk

A very specific niche — Codex's pinned V8/rusty_v8 version management — with distinct triggers unlikely to fire for unrelated skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/codex
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.