CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

receiving-code-review

Code review requires technical evaluation, not emotional performance.

Quality

56%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/receiving-code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a strong, actionable behavioral skill: concrete response templates, explicit verification checkpoints, and clear handling of pushback and correction. Its main weaknesses are duplicated examples/rules across sections and verification steps that are named but not operationally defined.

Suggestions

Deduplicate: keep the "Fix 1-6" example and the ✅/❌ phrasing tables in one place (Real Examples) and reference them from other sections instead of restating them.

Make verification operational: replace "Test each fix individually" and "Verify no regressions" with concrete steps (e.g., which test command to run, what to check before moving to the next item).

DimensionReasoningScore

Conciseness

The body is mostly tight and directive, but there is real duplication: the "Fix 1-6 / understand 1,2,3,6, unclear on 4,5" example appears nearly verbatim in both "Handling Unclear Feedback" and "Real Examples", and the no-performative-agreement rule is restated in four places (Forbidden Responses, Acknowledging Correct Feedback, Common Mistakes, The Bottom Line). Fits anchor 3 ('could be tightened'); not 4 because of this repeated material, not 2 because most sections earn their tokens.

3 / 5

Actionability

Guidance is concrete throughout: copy-paste-ready ✅/❌ response phrasings, a 5-point external-reviewer verification checklist, a concrete YAGNI grep procedure, and an executable `gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies` command. Fits anchor 4 ('mostly executable guidance with minor gaps'); not 5 because some directives remain abstract (e.g., "Test each fix individually" without specifying how to test).

4 / 5

Workflow Clarity

There is an explicit 6-step response sequence (READ→UNDERSTAND→VERIFY→EVALUATE→RESPOND→IMPLEMENT), explicit stop checkpoints ("STOP - do not implement anything yet"), an implementation order with "Test each fix individually / Verify no regressions", and an error-recovery section ("Gracefully Correcting Your Pushback"). Between anchors 4 and 5; verification steps are named but not concretely defined (no test command or re-check loop after a regression is found), so 4 is the best fit.

4 / 5

Progressive Disclosure

No bundle files exist and the body references none; the skill is self-contained behavioral guidance with well-organized, clearly headed sections. Fits anchor 4 ('good structure; most content appropriately placed; minor organization gaps'); not 5 because at ~220 lines the Real Examples and Common Mistakes sections could arguably live in a separate reference file.

4 / 5

Total

15

/

20

Passed

Description

25%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 a memorable principle statement but fails as a skill description: it names no concrete capabilities, includes no trigger guidance, and would collide with other code-review-related skills. A user (or Claude) reading only this line could not tell what the skill does or when to invoke it.

Suggestions

State concrete capabilities, e.g., "Verifies code review feedback against the codebase, responds without performative agreement, and pushes back with technical reasoning when suggestions are wrong."

Add an explicit trigger clause, e.g., "Use when receiving code review feedback, PR review comments, or review requests from a human partner or external reviewers."

Differentiate from review-performing skills by making the reception/response angle explicit in the first sentence, e.g., "Receiving code review feedback: ..." rather than the generic "Code review requires...".

DimensionReasoningScore

Specificity

"Code review requires technical evaluation, not emotional performance" names the domain but lists no concrete actions or capabilities — it is a stance statement, not a capability description. It is above anchor 1 because the domain is specific, but below anchor 3 because no concrete actions (e.g., verifying feedback against the codebase, responding without performative agreement) are named.

2 / 5

Completeness

The 'what' is vague (a principle about how to behave, not what the skill does) and the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3. Matches anchor 2 ('Has a vague what and no when') exactly; not 3 because the 'what' is not a clear action list.

2 / 5

Trigger Term Quality

"code review" is the only natural keyword; the phrases a user would actually say when needing this skill ("review feedback", "address review comments", "PR comments") are all missing. Fits anchor 2 (one or two keywords, missing the natural phrases users say); not 3 because even common synonyms and variations are absent.

2 / 5

Distinctiveness Conflict Risk

"Code review" is the trigger domain of many other skills (performing reviews, security review, simplification), and nothing in the description signals that this skill is about receiving and responding to feedback rather than conducting reviews. High overlap risk with many similar skills matches anchor 2; not 3 because there is no differentiating signal at all.

2 / 5

Total

8

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/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.