CtrlK
BlogDocsLog inGet started
Tessl Logo

local-review-codex

Run the CI Codex PR review locally against this branch's unpushed work (committed + uncommitted) before pushing. Same policy, model, and reasoning effort as the codex-pr-review GitHub action.

69

Quality

83%

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%

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

The body is a tight, actionable, well-sequenced guide that assumes Claude's competence and gives concrete commands plus fallbacks. No dimension is weak; the only minor improvement space is adding an explicit verify/decision checkpoint in the relay step.

DimensionReasoningScore

Conciseness

Lean prose that assumes Claude's knowledge of git, codex, and CI workflows; every section (Prerequisites, Run, Relaying) earns its place without explaining basics, matching the lean-and-efficient anchor.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands (bash run.sh, the version pin, npm install --global @openai/codex@0.144.1, git merge-base usage) and concrete fallback behavior.

3 / 3

Workflow Clarity

Clear Prerequisites -> Run -> Relaying sequence with explicit handling notes (pipefail/sh, origin/main fallback, read-only sandbox); as a read-only review skill with no destructive or batch ops, the simple-skill scoring note allows a 3.

3 / 3

Progressive Disclosure

Well-organized sections with no bundle files needed; external references (REVIEW.md, the workflow YAML) are real and clearly signaled, satisfying the simple-skill allowance for a 3.

3 / 3

Total

12

/

12

Passed

Description

67%

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 and distinct, clearly scoping a local pre-push Codex review with concrete actions and a well-defined niche. It loses points on completeness for lacking an explicit "Use when..." trigger and on trigger-term quality for missing the most natural user phrasings.

Suggestions

Add an explicit "Use when ..." clause (e.g., 'Use before git push on a non-trivial change, or when you want a CI-equivalent Codex review locally.') to lift completeness.

Include natural user phrasings like "review my changes/PR before pushing" alongside the existing trigger terms.

Front-load the trigger context so the when-to-use condition reads as explicit guidance rather than a consequence of the action.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Run the CI Codex PR review locally", "committed + uncommitted", "before pushing", and pins policy/model/effort — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

The "what" is explicit but "when" is only implied via "before pushing" with no "Use when..." clause, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

Has relevant keywords ("PR review", "before pushing", "Codex", "GitHub action") but misses common natural phrasings a user would say like "review my changes" or "review my PR", so it stops at some-relevant-keywords.

2 / 3

Distinctiveness Conflict Risk

Clear niche (local Codex pre-push review with stated CI correspondence) unlikely to trigger for other skills, matching the clear-niche-with-distinct-triggers anchor.

3 / 3

Total

10

/

12

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
windmill-labs/windmill
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.