CtrlK
BlogDocsLog inGet started
Tessl Logo

comment-writer

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

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

100%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 an exemplary simple skill: lean, actionable, with a clear formula and concrete examples covering the common comment types. No bundle files exist or are needed, and there are no destructive operations requiring validation loops.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a tight voice-rules table, a 3-line formula, three short examples, and one command, with no padding or explanation of concepts Claude already knows. It matches the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It gives a concrete comment formula plus three copy-paste-ready example comments covering the common cases (request change, approve with note, ask for split) and an executable gh command, matching the 'fully executable; copy-paste ready; specific examples cover common cases' anchor.

5 / 5

Workflow Clarity

This is a simple single-purpose skill (one action: write a comment) with an unambiguous 3-part formula structure; per the simple-skill exception such clarity scores 5, and there are no destructive or batch operations that would cap the score.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references and is organized into clear sections (When to Use, Voice Rules, Comment Formula, Examples, Commands); per the guideline, a simple skill with well-organized sections and no required references scores 5.

5 / 5

Total

20

/

20

Passed

Description

77%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 well-structured with strong trigger phrasing and a clear niche, but its action statement is thin: a single generic verb with no concrete sub-capabilities. Fleshing out what the skill actually produces would lift specificity.

Suggestions

Add 1-2 concrete actions or outputs after the main verb, e.g. 'Write warm, direct collaboration comments for PR reviews, issue replies, and async updates; drafts approve/request-change/ask-to-split responses.'

Include a couple of natural synonyms already used in the body (e.g. Discord, async updates) to round out trigger term coverage.

DimensionReasoningScore

Specificity

The description only offers one verb ("Write warm, direct collaboration comments") with no enumerated concrete actions or sub-tasks, matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires 1-2 specific actions.

2 / 5

Completeness

It explicitly answers both what ("Write warm, direct collaboration comments") and when ("Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments") with concrete trigger phrases, matching the top anchor exactly; it is not a 4 because the when-clause is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

"PR feedback, issue replies, reviews, Slack messages, or GitHub comments" gives good natural keyword coverage a user would actually say, with only minor synonyms missing (e.g. Discord, async updates), fitting the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (human-facing collaboration comments) with distinct triggers (PR/issue/Slack/GitHub) and minimal overlap risk, matching the 'clear niche with distinct triggers' anchor rather than the 4-anchor which still allows minor overlap.

5 / 5

Total

16

/

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
Gentleman-Programming/gentle-ai
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.