CtrlK
BlogDocsLog inGet started
Tessl Logo

comment-checker

Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.

64

Quality

76%

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 ./plugins/omo/components/comment-checker/skills/comment-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 model of conciseness with well-organized structure and clear, actionable scope boundaries; its only weakness is that the 'fix or explain' decision branch lacks guidance on when each response is appropriate.

Suggestions

Clarify when Codex should fix versus explain a flagged comment (e.g. fix when the comment is inaccurate or stale; explain when the comment is intentional and correct).

Optionally include a one-line example of the blocking feedback Codex receives so the trigger condition is unambiguous in practice.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, never explaining what hooks, patches, or MCP tools are, and every line (registered tools, blocking feedback, scope bullets) earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

It gives concrete, actionable guidance for an instruction-only skill — listing exact triggering tools and the directive to 'fix or explain the flagged comment before moving on' — but offers no example of what a 'fix' versus an 'explain' looks like, a minor gap.

4 / 5

Workflow Clarity

As a single-purpose skill the workflow is unambiguous (warning -> fix or explain -> proceed), but the 'fix OR explain' branch gives no criteria for choosing between them, leaving a minor sequencing gap rather than a fully explicit decision path.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well-organized with a clear intro and a '## Scope' section of focused bullets, satisfying the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

18

/

20

Passed

Description

66%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 has a clear, explicit trigger clause and a distinct, low-conflict niche, but its stated capabilities ('understand or respond') are generic and the 'what' blends into the 'when' rather than standing on its own.

Suggestions

Replace the generic verbs 'understand or respond to' with concrete actions the skill performs, e.g. 'Fix or explain flagged comments reported by comment-checker after edit-like patches'.

Add natural-language synonyms users might say, such as 'comment warnings' or 'lint feedback', alongside 'comment-checker feedback' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The domain is named precisely ('automatic comment-checker feedback emitted after an edit-like PostToolUse hook'), but the stated actions ('understand or respond to') are minimal and generic rather than a list of concrete capabilities, matching the anchor that names the domain with 1-2 concrete actions.

3 / 5

Completeness

An explicit 'Use when...' clause provides a concrete trigger (after an edit-like PostToolUse hook), and the 'what' is present ('understand or respond to comment-checker feedback') but blended and slightly vague, matching the anchor where both what and when exist yet the what could be more explicit.

4 / 5

Trigger Term Quality

It includes relevant terms a plugin user would say ('comment-checker feedback', 'edit') but leans on technical jargon ('PostToolUse hook') and omits common synonyms or variations like 'comment warnings' or 'lint feedback', fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The trigger is narrowly scoped to comment-checker feedback after edit-like PostToolUse hooks, forming a clear niche with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

15

/

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
code-yeongyu/lazycodex
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.