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

80%

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 ./.agency/plugins/nori/skills/receiving-code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-sequenced process skill with explicit validation checkpoints and feedback loops throughout. Its weaknesses are redundancy — the same rules (clarify-first, YAGNI, verify-first) restated across four sections plus a duplicative checklist — and an external skill reference whose path cannot be verified within this bundle.

Suggestions

Consolidate the clarify-before-implement rule, YAGNI check, and verification requirements into the process steps, and cut the Quick Reference Checklist and Red Flags sections that restate them.

Remove the duplicated YAGNI paragraph in Response Tone Guidelines, keeping the full version in Step 3 only.

Make the finishing-a-development-branch reference verifiable (relative path within the bundle or inline the two steps it points to).

DimensionReasoningScore

Conciseness

The body is imperative and free of concept explanations Claude already knows, but the same rules repeat across sections: the clarify-before-implement rule appears in Step 2, the Quick Reference Checklist, Response Tone Guidelines, and Red Flags; the YAGNI check appears nearly verbatim in Step 3 and again in Response Tone Guidelines; the Quick Reference Checklist largely restates the process steps. Not 2: language is terse and no padding about known concepts; not 4: the cross-section duplication is substantial and consolidatable.

3 / 5

Actionability

Guidance is copy-paste ready throughout: concrete commands (`gh pr view --json number -q .number`, `gh pr view [PR-NUMBER] --comments`, `grep -r "endpointName" .`, `npm test`, `npm run lint:*-types`, `npm run format`, `npm run lint`, `git diff --stat`, `git push`), a TodoWrite template, and concrete example dialogues covering the common cases (clarify-vs-implement, YAGNI pushback, admitting error). The external finishing-a-development-branch reference is supplementary since the actual commands are inlined. Not 4: no gaps in executable coverage for the common cases.

5 / 5

Workflow Clarity

The sequence (todo → fetch → clarify → implement in priority order → test/lint/format → push → summarize) is explicit with validation checkpoints and feedback loops: "If ANY item is unclear, STOP", "Test individually", "If tests fail, fix before proceeding", plus implementation ordering and checklists. This matches the anchor's explicit-validation, error-recovery, and checklist criteria for the batch (multi-item feedback) nature of the operation. Not 4: checkpoints are not merely present but explicit with failure paths for each.

5 / 5

Progressive Disclosure

Sections are well-organized (Overview, Steps 0-6, Quick Reference, Tone Guidelines, Common Mistakes table, Red Flags) and the one external reference is clearly signaled and supplementary. Not 5: no bundle files exist to verify `.agency/plugins/nori/skills/finishing-a-development-branch/SKILL.md` resolves, and there is notable content duplication across sections that consolidation/restructuring would address; not 3: navigation is easy and content placement is appropriate for a process skill.

4 / 5

Total

17

/

20

Passed

Description

70%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 solid description with an explicit, well-qualified 'Use when' trigger and a distinct receiving-feedback niche. Its main weakness is that the 'what' is expressed as behavioral requirements ("technical rigor and verification") rather than the concrete actions the skill actually walks through.

Suggestions

Replace the abstract closing clause with 2-3 concrete actions, e.g. 'Verifies suggestions against the codebase, clarifies unclear items before implementing, tests each fix, and pushes updates'.

Add common trigger synonyms such as 'review comments' or 'PR feedback' to broaden natural keyword coverage.

State the full workflow outcome (fetch → verify → implement → re-test → push) so the 'what' is explicit rather than implied by tone guidance.

DimensionReasoningScore

Specificity

The description names the domain ("receiving code review feedback, before implementing suggestions") and 1-2 actions (verify, implement), but the closing clause "requires technical rigor and verification, not performative agreement or blind implementation" is abstract behavioral framing rather than concrete actions like fetching comments, clarifying, or re-testing. Not 4: no list of several specific actions; not 2: domain and actions are genuinely named.

3 / 5

Completeness

The 'when' is explicit and specific ("Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable"), and a 'what' is present via "requires technical rigor and verification". Not 5: the 'what' describes manner rather than the concrete actions the skill performs (fetch, clarify, implement, re-test, push); not 3: both what and when are explicitly stated.

4 / 5

Trigger Term Quality

"code review feedback", "implementing suggestions", "seems unclear", "technically questionable" are natural phrases a user would say when needing this skill. Not 5: misses common variations like "review comments", "PR feedback", or "address review comments"; not 3: the core natural trigger phrase is present and well-qualified.

4 / 5

Distinctiveness Conflict Risk

"Receiving code review feedback... before implementing suggestions" carves out a distinct niche (receiving/responding vs. giving reviews) with specific trigger conditions. Not 5: minor overlap risk with code-review and PR-workflow skills; not 3: the receiving-vs-giving framing and conditions make confusion unlikely.

4 / 5

Total

15

/

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

microsoft/FluidFramework

Path

.agency/plugins/nori/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.