CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-reviewing-pr

This skill should be used when the user says "reviewing pr", "arness reviewing pr", "review PR", "review pull request", "check PR comments", "PR feedback", "address PR feedback", "fix PR issues", "what did the reviewer say", "handle review comments", "review PR 123", "arn-reviewing-pr", "PR review", "check review", or wants to validate PR review comments, categorize findings, and fix or defer issues. Chains back to arn-implementing if substantial fixes are needed.

66

Quality

80%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/arn-code/skills/arn-reviewing-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

This is a well-structured orchestration skill with clear workflow sequencing and appropriate delegation to sub-skills. Its main weakness is some redundancy in explaining its own role and duplicating error conditions between the workflow steps and the error handling section. The actionability is adequate for an orchestration wrapper but relies heavily on delegated skills for concrete execution.

Suggestions

Remove the redundant error handling section entries that are already covered in the workflow steps (platform not configured, no PR for branch) to improve conciseness.

Trim the introductory paragraph — the second sentence ('This skill is a thin orchestration wrapper...') restates what the first paragraph already implies and could be condensed into a single line.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some redundant explanations (e.g., restating that it's a 'thin orchestration wrapper' and explaining what it does/doesn't do). The error handling section partially duplicates information already covered in the workflow steps (e.g., platform not configured, no PR for current branch).

2 / 3

Actionability

The skill provides a clear workflow with specific steps and concrete invocation syntax, but it's primarily an orchestration wrapper that delegates to another skill. The actual commands are limited to `git push` and skill invocations. The AskUserQuestion interaction pattern is well-specified with concrete options, but there's no executable code beyond the git push.

2 / 3

Workflow Clarity

The workflow is clearly sequenced (Step 0 → Step 1 → Step 2 → Step 3) with explicit decision points and branching logic. Each step has clear conditions and outcomes, the completion handoff covers all cases (fixes applied vs. no fixes), and error handling is comprehensive with specific recovery actions for each failure mode.

3 / 3

Progressive Disclosure

The skill appropriately delegates detailed review logic to `arn-code-review-pr` and references `step-0-fast-path.md` for configuration. It maintains a clear overview structure without inlining content that belongs elsewhere. References are one level deep and clearly signaled.

3 / 3

Total

10

/

12

Passed

Description

89%

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 excels at trigger term coverage and completeness, providing an extensive list of natural phrases and clearly stating both what the skill does and when to use it. Its main weakness is that the capability description ('validate PR review comments, categorize findings, and fix or defer issues') could be more specific about the concrete actions performed. The heavy reliance on listing trigger phrases makes it functional but somewhat verbose.

Suggestions

Expand the capability description with more concrete actions, e.g., 'Fetches PR review comments from GitHub, categorizes them by severity, applies code fixes for actionable feedback, and posts resolution responses.'

DimensionReasoningScore

Specificity

The description mentions some actions like 'validate PR review comments, categorize findings, and fix or defer issues' and 'chains back to arn-implementing if substantial fixes are needed,' but these are somewhat vague and not comprehensively detailed. It doesn't describe concrete steps like fetching comments, applying code fixes, or posting responses.

2 / 3

Completeness

The description explicitly answers both 'what' (validate PR review comments, categorize findings, fix or defer issues) and 'when' (with a comprehensive list of trigger phrases and the explicit statement 'This skill should be used when...'). Both dimensions are clearly addressed.

3 / 3

Trigger Term Quality

The description includes an extensive list of natural trigger phrases users would say: 'review PR', 'review pull request', 'check PR comments', 'PR feedback', 'address PR feedback', 'fix PR issues', 'what did the reviewer say', 'handle review comments', etc. These cover many natural variations well.

3 / 3

Distinctiveness Conflict Risk

The skill is clearly scoped to PR review handling with very specific trigger terms. It also clarifies its relationship to 'arn-implementing' for substantial fixes, which helps distinguish it from a general implementation skill. The niche of reviewing and addressing PR feedback is distinct.

3 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
AppsVortex/arness
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.