CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-fe/demo-pr-review

Use when reviewing or approving a pull request

80

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a high-quality skill that is concise, actionable, and well-structured. It provides specific security patterns to match, a clear inline comment format with examples at different severity levels, a worked end-to-end example, and an explicit validation checkpoint in the workflow. The content respects Claude's intelligence while adding genuine value through concrete, non-obvious guidance.

DimensionReasoningScore

Conciseness

Every section earns its place. The skill doesn't explain what a PR is or how diffs work—it assumes Claude's competence and focuses on specific, non-obvious guidance like concrete security patterns (sk-, AKIA), inline comment format, and the worked example. No padding or unnecessary context.

3 / 3

Actionability

Provides a concrete inline comment format with two severity-level examples, a worked example showing a diff and the expected review output, specific security red flags with actual code patterns to match, and a clear three-option decision framework (APPROVE/REQUEST_CHANGES/COMMENT). Fully actionable and copy-paste ready.

3 / 3

Workflow Clarity

The 7-step review process is clearly sequenced with an explicit validation checkpoint at step 6 ('Confirm that every changed file has been reviewed and every flagged issue has been recorded before proceeding'). This feedback loop prevents premature summary writing, which is the key destructive/irreversible action in a review workflow.

3 / 3

Progressive Disclosure

For a standalone skill with no bundle files, the content is well-organized into logical sections (What to Check, Review Process, Inline Comment Format, Worked Example, Output Format) that are appropriately sized. No section is bloated, and the structure supports easy scanning. No external references are needed for this scope.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly articulates what the skill does (reviews PR diffs across multiple quality dimensions, leaves inline comments, provides a decision) and when to use it (with two explicit 'Use when' clauses covering both general scenarios and specific user phrases). The description is comprehensive yet concise, uses third-person voice throughout, and includes strong natural trigger terms that cover common variations of how users request code reviews.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: reviews diffs for correctness, code quality, test coverage, security vulnerabilities, and performance issues; leaves inline comments on specific lines; concludes with APPROVE, REQUEST_CHANGES, or COMMENT decision.

3 / 3

Completeness

Clearly answers both 'what' (reviews diffs for correctness, quality, security, etc.; leaves inline comments; provides a decision) and 'when' with two explicit 'Use when' clauses listing specific trigger phrases and scenarios.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'pull request', 'code review', 'PR', 'merge request', 'PR feedback', 'review this PR', 'check these changes', 'approve a pull request', 'review the diff'. Covers multiple natural phrasings and synonyms.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to pull request / code review workflows with distinct triggers like 'PR', 'pull request', 'merge request', 'approve', and specific outputs (APPROVE/REQUEST_CHANGES/COMMENT). Unlikely to conflict with general coding or documentation skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents