CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Review code changes in dotnet/runtime for correctness, performance, and consistency with project conventions. Use when reviewing PRs or code changes.

66

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 ./.github/skills/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 well-structured, highly actionable review-process skill with clear sequencing, explicit validation gates and feedback loops, and clean one-level-deep references to external instruction files. It is token-efficient and avoids explaining basic concepts, with only minor repetition and reliance on external repo files keeping it from maximum marks.

DimensionReasoningScore

Conciseness

The body is dense and largely assumes Claude's competence, with little padding or explanation of basic concepts; a few sections are somewhat repetitive (the API-approval procedure is re-stated in Steps 1 and 4) which keeps it just short of fully lean.

4 / 5

Actionability

It gives concrete, executable guidance (specific git commands like 'git log --oneline -20 -- <file>', explicit file paths to load, an exact output format with verbatim templates); it lacks runnable code because this is a process/instruction skill, but the guidance is specific and actionable.

4 / 5

Workflow Clarity

A clearly sequenced multi-step process (Steps 0-5) with explicit validation checkpoints (independent assessment before reading PR narrative, blocking API-approval gate, devil's-advocate check, verdict-consistency rules and error-recovery/timeout handling) provides robust feedback loops for a review workflow.

5 / 5

Progressive Disclosure

SKILL.md is an overview that signals one-level-deep references to concrete files (pr-assessment.md, api-approval-check.md, and per-area .github/instructions/*.instructions.md) with clear guidance on when to load each; no nested/deep references, though the detailed rules themselves live in external repo files rather than a local bundle, so structure is good but not perfectly self-contained.

4 / 5

Total

17

/

20

Passed

Description

78%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, third-person description that names a clear niche, concrete capability dimensions, and an explicit 'Use when' trigger. It is concise and distinguishable; the main room for improvement is broadening the trigger-term coverage with synonyms.

Suggestions

Add synonyms a user might naturally say, e.g. 'Use when reviewing PRs, pull requests, diffs, or code changes in dotnet/runtime.'

Optionally name 1-2 more concrete review actions (e.g. 'verifies new public API approval, flags blocking issues') to lift specificity toward 5.

DimensionReasoningScore

Specificity

Names the domain (dotnet/runtime code review) and three concrete action dimensions ("correctness, performance, and consistency with project conventions"), but stays at a capability-level rather than enumerating several specific actions like 'flag blocking bugs' or 'verify API approval'.

4 / 5

Completeness

It clearly states what the skill does ('Review code changes...for correctness, performance, and consistency') and provides an explicit 'Use when reviewing PRs or code changes' trigger, but the 'when' clause is fairly compact and could name more triggering situations.

4 / 5

Trigger Term Quality

Natural trigger phrases 'reviewing PRs' and 'code changes' are exactly what a user would say; it lacks synonyms/extensions like 'pull request', 'diff', or 'review this PR' that would round it out to comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The dotnet/runtime-specific niche plus 'reviewing PRs or code changes' trigger makes it highly distinct and unlikely to fire for unrelated skills, with minimal overlap risk.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/runtime
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.