CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-review-response

Use when a reviewer, CI bot, or another AI leaves feedback to address

58

Quality

67%

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 ./.claude/skills/skill-review-response/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

The body is well-structured and highly actionable, with clear sequenced workflows, validation checkpoints, and a useful decision table. Its only weakness is the speculative multi-provider section, which adds some unnecessary token weight.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence (no primer on what code review is), but the "Multi-Provider Review Context" section's provider stereotyping is speculative padding that could be tightened, keeping it just below fully efficient.

2 / 3

Actionability

It gives concrete, copy-paste-ready guidance: a 6-step response pattern, a decision table with explicit IF YES/IF NO branches, and a fill-in push-back template with a worked example, which is highly actionable for an instruction-only skill.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints ("Run verification", "verify each change"), feedback loops for error recovery (re-review rounds with fewer issues), and a checklist table for complex evaluation.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the content is well-organized into clearly headed sections with no nested references, and the only external pointer (skill-verification-gate) is a one-level cross-skill reference appropriately signaled.

3 / 3

Total

11

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 provides a clear trigger context but is weak on stating concrete capabilities, leaning on the implied action "to address". Trigger terms are relevant but missing common variations like "code review" and "PR comments".

Suggestions

Add an explicit capability statement, e.g. "Evaluate, verify, and respond to code review feedback" before the "Use when" clause so both what and when are clearly answered.

Include common trigger variations such as "code review", "PR comments", and "changes-requested" to improve natural keyword coverage.

Replace the vague "feedback to address" with a concrete action verb to lift specificity from naming the domain to listing specific actions.

DimensionReasoningScore

Specificity

The description names the domain ("a reviewer, CI bot, or another AI leaves feedback") but the only action is the vague "to address", with no concrete capabilities listed such as verifying, evaluating, or pushing back, so it stops at naming domain and an implied action rather than multiple specific actions.

2 / 3

Completeness

It has an explicit "Use when" trigger clause but the "what does this do" half is only implied via "feedback to address" rather than stated as a concrete capability, so it does not clearly answer both what and when.

2 / 3

Trigger Term Quality

It includes relevant terms a user might say ("reviewer", "CI bot", "feedback") but misses common variations like "code review", "PR comments", or "changes requested", so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The niche (addressing feedback from reviewers/CI bots/AI) is fairly specific, but the broad "another AI" phrasing and narrow trigger terms could still overlap with other review-related skills.

2 / 3

Total

8

/

12

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nyldn/claude-octopus
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.