CtrlK
BlogDocsLog inGet started
Tessl Logo

respond-to-review

Use when pull request review comments, requested changes, or reviewer questions need to be investigated, addressed, or answered.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 tight, highly actionable workflow that respects Claude's competence and includes validation checkpoints. The only gap is an explicit 'if checks fail, fix and re-run' feedback loop.

Suggestions

Add an explicit error-recovery step, e.g. 'If regression or repository checks fail, fix the root cause and re-run before reporting.'

Optionally note how to surface disagreements with reviewers concretely (e.g. reply format or evidence expected) to strengthen the response-drafting step.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Provides concrete, specific guidance (collect file/line/author/thread status; inspect callers/tests/diff; classify into four buckets; smallest root-cause fix; run regression and repo checks) despite being instruction-only.

5 / 5

Workflow Clarity

Clear 5-step sequence with checkpoints (inspect before acting, re-read final diff, call out unrun checks), but lacks an explicit error-recovery feedback loop for when checks fail.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, and well-organized with clear sections and numbered steps.

5 / 5

Total

19

/

20

Passed

Description

82%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 concise, uses an explicit 'Use when' trigger, and carves out a distinctive PR-review niche. The only weakness is that the action verbs are somewhat generic.

DimensionReasoningScore

Specificity

Names the PR-review domain and three verbs ('investigated, addressed, or answered') but the actions are generic rather than a comprehensive concrete action list.

3 / 5

Completeness

Explicit 'Use when...' trigger and a clear statement of what is done (investigate/address/answer review feedback) with concrete trigger phrases.

5 / 5

Trigger Term Quality

'pull request review comments, requested changes, reviewer questions' are natural phrases users say, though common synonyms like 'code review' or 'PR feedback' are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear PR-review niche with distinct triggers ('requested changes', 'reviewer questions') and minimal overlap with other skills.

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
eloqdata/eloqkv
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.