CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/harness/adapters/antigravity/skills/receiving-code-review/SKILL.md

The canonical home for this skill is receiving-code-review in phatblat/dotfiles

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is maximally token-efficient but is a hollow stub: its single instruction redirects to an absolute path outside the skill bundle that does not exist in this environment, leaving the skill with no actionable guidance, workflow, or bundled content of its own. As shipped, the skill cannot perform its stated function.

Suggestions

Inline the core guidance in SKILL.md (e.g., verify reviewer claims against the actual codebase, test suggestions before implementing, push back with evidence when feedback is technically wrong) rather than delegating everything to an external file.

Replace the machine-specific absolute path `~/.agents/skills/receiving-code-review/SKILL.md` with a bundle-relative reference (e.g., `references/process.md`) and include that file so the skill is self-contained and portable.

Add a short sequenced workflow with an explicit validation checkpoint (e.g., re-run tests after implementing each accepted suggestion) so the multi-step judgment process the description promises is actually present.

DimensionReasoningScore

Conciseness

The body is a single lean instruction line ("Load and follow the shared skill at `~/.agents/skills/receiving-code-review/SKILL.md`.") with no padding and no explanations of concepts Claude already knows; the one-line HTML generator comment is de minimis. Not 4 because there is no over-explanation to trim — every instructional token earns its place.

5 / 5

Actionability

The only guidance is a redirect to an absolute home-directory path that does not exist in this environment and is not part of the skill bundle, so the instruction cannot be executed as bundled and all task-specific steps are absent. Not 1 because the directive itself is concrete (a specific file path), not vague; not 3 because "some concrete guidance but incomplete" overstates a pointer whose target is unreachable and which conveys zero guidance on the actual task.

2 / 5

Workflow Clarity

The only sequence is an implicit "load then follow" — every step of the actual task (evaluate feedback, verify claims, decide, implement) is delegated to a missing external file, with no validation checkpoints anywhere. Not 1 because the body is coherent and contains one clear directive; not 3 because there are no listed steps for the skill's actual multi-step judgment task, only a hollow redirect.

2 / 5

Progressive Disclosure

The bundle contains no references/, scripts/, or assets/ directories, and the single reference ("~/.agents/skills/receiving-code-review/SKILL.md") is clearly signaled and one level deep but points outside the bundle to a machine-specific absolute path; the SKILL.md itself contains no overview content. Not 4 because "most content is appropriately placed" cannot hold when the bundle holds no content at all; not 2 because the reference is not buried and nothing is improperly inlined.

3 / 5

Total

12

/

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 strong: it has an explicit, multi-condition "Use when..." trigger clause, a clear statement of the required approach, and a distinctive niche that is unlikely to fire for the wrong skill. The only gaps are a few missing natural synonym triggers (e.g., "review comments", "PR feedback") and slightly abstract phrasing of the core action.

DimensionReasoningScore

Specificity

Phrases like "requires technical rigor and verification, not performative agreement or blind implementation" and "before implementing suggestions" list several specific behavioral directives for the code-review-feedback domain. Not 5 because "technical rigor" is somewhat abstract and concrete verification actions (e.g., check claimed APIs, run tests) are implied rather than enumerated.

4 / 5

Completeness

Explicitly answers "when" with concrete trigger phrases ("Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable") and "what" ("requires technical rigor and verification, not performative agreement or blind implementation"). Not 4 because the "when" clause is already highly explicit and specific, so the 4-anchor caveat ("'when' could be more explicit") does not apply.

5 / 5

Trigger Term Quality

"receiving code review feedback", "implementing suggestions", and "feedback seems unclear" are natural phrases users would say. Not 5 because common variations like "review comments", "PR feedback", or "addressing review comments" are missing; not 3 because coverage goes well beyond "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

"receiving code review feedback" and "before implementing suggestions" carve out a clear niche distinct from skills for giving or performing code reviews, with minimal conflict risk. The qualifiers "receiving" and "implementing" disambiguate the shared "code review" term, so the minor-overlap 4 anchor fits less well.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

phatblat/dotfiles

Path

.agents/harness/adapters/antigravity/skills/receiving-code-review/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.