CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

requesting-code-review

Pre-commit review: security scan, quality gates, auto-fix.

55

Quality

69%

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 ./skills/software-development/requesting-code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 strongly actionable, well-sequenced verification pipeline with excellent validation and feedback loops; its workflow clarity is exemplary. The main costs are token weight from security basics Claude already knows and the absence of any reference-file split for the language-specific tool matrix.

Suggestions

Move the per-language test/lint command matrix and the 'Common Patterns to Flag' reference into a references/ file (e.g. references/tool-commands.md), keeping only the detection logic inline.

Cut or compress the bad/good code examples for SQL injection, shell injection, and XSS — Claude already knows these patterns; a one-line mention in the scan list suffices.

Trim the 'Integration with Other Skills' section to one line per skill to reduce token spend without losing navigation.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands and prompts, but the 'Reference: Common Patterns to Flag' section spends ~20 lines on SQL injection, shell injection, and XSS basics Claude already knows, and a few sections (integration notes, pitfalls) could be tightened — matching 'mostly efficient with some unnecessary explanation'.

3 / 5

Actionability

Nearly everything is executable: copy-paste bash for diffing, secret/injection grep scans, per-language test and lint commands, and fully drafted delegate_task prompts. Minor gaps (placeholder markers like '[INSERT GIT DIFF]' and 'specific_file.py') keep it just below the fully-copy-paste anchor 5.

4 / 5

Workflow Clarity

Steps 1-8 are clearly sequenced with explicit validation checkpoints (baseline test comparison, fail-closed reviewer JSON rules, lint gates), a feedback loop capped at 2 fix-and-reverify cycles with escalation on failure, and an 8-item self-review checklist — matching the top anchor exactly.

5 / 5

Progressive Disclosure

No bundle files exist and sections are well-headed, but ~50 lines (the per-language test/lint command matrix and the common-patterns reference) clearly belong in separate reference files rather than inline in a ~270-line SKILL.md, matching the 'content that should be separate is inline' anchor.

3 / 5

Total

15

/

20

Passed

Description

58%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 compact and names a clear pre-commit verification niche with three concrete capabilities, but it omits any 'Use when...' trigger guidance and lacks the natural user phrasings that would let it fire reliably. Adding an explicit when-to-use clause with common trigger phrases would lift its two weakest dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user says commit, push, ship, or asks to review/verify changes before committing.'

Include natural synonyms and phrasings users actually say ('before committing', 'before push', 'check my diff') alongside the technical terms.

Distinguish from sibling review skills inline, e.g. 'verifies your own changes pre-commit (not PR review)'.

DimensionReasoningScore

Specificity

Names the pre-commit domain and three concrete actions ('security scan', 'quality gates', 'auto-fix'), but 'quality gates' is somewhat generic and coverage of the pipeline (reviewer subagent, regression checks) is incomplete, so it falls just short of the comprehensive anchor 5 and clearly above anchor 3.

4 / 5

Completeness

The 'what' is stated clearly, but there is no 'Use when...' clause or any equivalent explicit trigger guidance; per the judging guidelines a missing 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords exist ('Pre-commit', 'review', 'security scan', 'auto-fix') but natural user phrasings like 'before committing', 'before I push', 'check my changes', or 'review my diff' are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The 'Pre-commit' timing pin plus scan/auto-fix actions carve a mostly distinct niche, but the bare word 'review' creates minor overlap risk with PR-review and commit-message skills rather than the minimal-conflict profile of anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

skills/software-development/requesting-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.