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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

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.

The skill body is a strong, actionable workflow with concrete commands, explicit validation checkpoints, and good organization; its main weakness is cross-section repetition of the same governing rules that could be consolidated.

Suggestions

Consolidate the 'clarify all unclear items before implementing any' rule to a single canonical statement and reference it rather than restating it in the checklist, tone guidelines, mistakes table, and red flags.

De-duplicate the YAGNI check between Step 3 and the Response Tone Guidelines section.

Consider moving the Common Mistakes table and Red Flags into a bundled reference file to keep SKILL.md a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and never pads with concepts Claude already knows, but key rules are restated across sections (the 'clarify all before implementing' rule appears in Step 2, the checklist, the tone guidelines, the mistakes table, and the red flags; the YAGNI check appears twice), offering real tightening opportunities.	3 / 5
Actionability	Concrete, copy-paste-ready commands and templates are provided throughout (gh pr view, grep -r, npm test/lint/format, git push, a TodoWrite template, and a final summary template), covering the common cases fully.	5 / 5
Workflow Clarity	Steps 0-6 are clearly sequenced with explicit validation checkpoints (STOP if any item unclear, test/commit each fix individually, run tests/lint/format before pushing), feedback loops, and supporting checklists for this batch operation.	5 / 5
Progressive Disclosure	The body is well-organized into clear sections with a signaled one-level cross-skill reference (finishing-a-development-branch/SKILL.md); no bundle files exist, and the content is reasonably overview-level, though the tone/mistakes/red-flags material could potentially be externalized.	4 / 5
	Total	17 / 20 Passed

Description

68%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 has a strong, explicit trigger clause and a distinctive niche, but it expresses the skill's behavior as a stance against bad habits rather than enumerating the concrete actions the skill performs.

Suggestions

Add 2-3 concrete positive actions the skill performs (e.g., 'Fetch PR comments, verify each suggestion against the codebase, implement fixes in order, re-test, and push').

Reduce the negative framing ('not performative agreement or blind implementation') in favor of stating what the skill does do.

Include a couple of trigger synonyms such as 'PR comments' or 'reviewer notes' for broader natural-language coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('receiving code review feedback') but frames actions negatively ('requires technical rigor and verification, not performative agreement or blind implementation') rather than listing concrete positive actions like fetch/verify/implement/test.	2 / 5
Completeness	Both an explicit 'Use when...' trigger and a behavioral 'what' (requires technical rigor and verification) are present; the 'what' is attitudinal rather than a concrete action list, keeping it just below a 5.	4 / 5
Trigger Term Quality	Natural user phrases like 'code review feedback', 'implementing suggestions', and 'feedback seems unclear or technically questionable' are present and genuine, though a few synonymous variations are missing.	4 / 5
Distinctiveness Conflict Risk	'Receiving code review feedback, before implementing suggestions' is a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.	5 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: f02e424

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.