CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autofix

Apply approved fixes for unresolved CodeRabbit review comments, Codex P1-P3 findings, PR feedback, and code review issues with validation evidence. Use when asked to address review comments, fix review findings, clear unresolved comments, or autofix PR feedback.

Quality

85%

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

71%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 lean, highly directive skill body with a well-sequenced workflow, explicit validation gates, and strong safety boundaries for untrusted review text. Its main defects are cross-section rule duplication, the absence of literal commands and an explicit retry loop, and three Progressive Disclosure references that point to nonexistent files.

Suggestions

Remove or fix the three broken references to Infrastructure/references/... paths that do not exist in the bundle; either add those files to the bundle or drop the pointers.

State the untrusted-review-text rule once (e.g., in Constraints) and reference it from other sections instead of restating it in Philosophy, Execution Boundaries, and Anti-Patterns.

Add an explicit validation retry loop ("if a check fails: fix, then re-run the same command; only proceed when it passes") and at least one literal inventory command (e.g., the CodeRabbit CLI invocation or gh api call) to make guidance copy-paste executable.

DimensionReasoningScore

Conciseness

The body is dense and purely directive with no explanations of concepts Claude already knows, but the untrusted-review-text rule is restated roughly four times (Philosophy, Constraints, Execution Boundaries, Anti-Patterns) and the account-for-every-item rule appears in five sections — duplication that could be trimmed.

4 / 5

Actionability

Concrete instruction-level guidance throughout: exact normalization taxonomies ("CRITICAL, HIGH, MEDIUM, LOW, or TRIVIAL"; "security-tagged items are at least HIGH"), tool-preference ordering ("CodeRabbit CLI/plugin first; use GitHub review APIs only as fallback"), and explicit stop conditions. Not 5 because no literal, copy-paste-ready commands (e.g., actual CLI invocations) are given.

4 / 5

Workflow Clarity

A clear 11-step sequenced workflow with explicit validation checkpoints ("Stop if review generation is still in progress", "Run the smallest command or test that exercises changed behavior", "fail fast on failed gates") and a Failure mode section. Not 5 because no explicit validate-fix-re-validate retry loop is stated for failed checks.

4 / 5

Progressive Disclosure

Sections are well-organized and the four references/ files (discovery-interview.md, contract.yaml, evals.yaml, task-profile.json) exist one level deep and are clearly signaled, but three referenced paths — Infrastructure/references/openai-cookbook-expert-lens-pack.md, Infrastructure/references/openai-cookbook-skill-expertise-map.md, and Infrastructure/references/deferred-skill-context/agent-ops-autofix/ — do not exist in the bundle, leaving broken navigation targets.

3 / 5

Total

15

/

20

Passed

Description

91%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 strong description: concrete third-person action statement with explicit multi-verb trigger guidance and tool-specific scoping. The only weaknesses are a somewhat single-action verb set and mildly generic trailing scope terms that slightly raise conflict risk.

DimensionReasoningScore

Specificity

The description lists several specific actions and targets ("Apply approved fixes for unresolved CodeRabbit review comments, Codex P1-P3 findings, PR feedback ... with validation evidence") with named severity scopes, but the action coverage is narrower than anchor 5's multiple distinct operations.

4 / 5

Completeness

It explicitly answers both "what" (first sentence: apply approved fixes for enumerated finding types with validation evidence) and "when" ("Use when asked to address review comments, fix review findings, clear unresolved comments, or autofix PR feedback") with concrete trigger phrases, matching the anchor 5 pattern exactly.

5 / 5

Trigger Term Quality

Trigger phrases "address review comments", "fix review findings", "clear unresolved comments", and "autofix PR feedback" provide comprehensive natural-verb synonym coverage, reinforced by product names (CodeRabbit, Codex) users would actually say.

5 / 5

Distinctiveness Conflict Risk

CodeRabbit/Codex-specific remediation is a mostly distinct niche, but the trailing generic terms "PR feedback" and "code review issues" create minor overlap risk with general review/fix skills; not 5 because those broad phrases weaken the otherwise clear niche.

4 / 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

jscraik/Agent-Skills

Path

Skills/agent-ops/autofix/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.