CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Automated code review for pull requests using multiple specialized agents

80

1.50x
Quality

71%

Does it follow best practices?

Impact

99%

1.50x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

88%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 content is a highly actionable, well-sequenced workflow with concrete gh CLI commands and an explicit validation loop. It loses only minor points for some duplicated comment text and the absence of section headers to organize the steps, notes, and formatting rules.

Suggestions

Add section headers (e.g. '## Process', '## False positives', '## Inline comment format') to separate the numbered steps from the notes and formatting rules.

De-duplicate the 'No issues found' comment text, which appears in both step 7 and the Notes section.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no preamble on what a PR is), with only minor redundancy such as the 'No issues found' comment text appearing in both step 7 and the Notes section.

4 / 5

Actionability

Guidance is fully executable: it specifies agent models (haiku/sonnet/opus), exact gh CLI commands (gh pr view --comments, gh pr comment, gh pr review), suggestion-block rules, and the precise GitHub blob URL format for inline comments.

5 / 5

Workflow Clarity

Nine numbered steps are clearly sequenced with an explicit validation feedback loop: step 5 validates issues from step 4, step 6 filters unvalidated issues, and step 7 branches on whether issues remain.

5 / 5

Progressive Disclosure

No bundle files exist and the workflow is appropriately self-contained with no nested references, but the single body lacks section headers to delineate the steps, the false-positive list, and the comment-format spec.

4 / 5

Total

18

/

20

Passed

Description

53%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 clearly states what the skill does but omits any 'when to use' trigger guidance and only sparsely covers concrete actions, capping completeness and trigger quality at mid-scale. It is reasonably distinct as a niche PR-review skill.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to review a pull request, a PR, or a diff for bugs and CLAUDE.md compliance.'

List 2-3 concrete actions the skill performs (e.g. 'flags bugs, checks CLAUDE.md compliance, posts inline review comments') to lift specificity.

Include natural trigger synonyms such as 'PR', 'PR review', and 'diff review' for better trigger-term coverage.

DimensionReasoningScore

Specificity

Quotes the domain ('code review for pull requests') plus a mechanism ('multiple specialized agents'), but 'code review' is a single generic action and the multi-agent phrasing describes implementation rather than user-facing actions, so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clearly stated but there is no 'Use when...' or equivalent trigger clause, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural keywords 'code review' and 'pull requests' are present, but common synonyms a user would say like 'PR', 'PR review', or 'diff review' are missing.

3 / 5

Distinctiveness Conflict Risk

The PR-code-review niche with a multi-agent mechanism is mostly distinct, with only minor overlap risk against generic review skills.

4 / 5

Total

13

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
pipecat-ai/pipecat
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.