CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-review

手动审查当前 Comet change 的实现差异,只报告正确性、安全和边界问题,不推进工作流。

56

Quality

63%

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 ./assets/skills-zh/comet-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable read-only review workflow with concrete commands, explicit stop/decision checkpoints, and a defined output format, all kept concise and well-organized.

DimensionReasoningScore

Conciseness

The body is lean procedural guidance that assumes Claude's competence — it directs read-only review actions and enumerates exact commands and files without padding or explaining concepts Claude already knows.

4 / 5

Actionability

It provides concrete executable commands ("comet status . --json", "comet state get <change-name> phase", "git status --short --untracked-files=all"), specific file paths to read, and a defined output format with severity levels, with only minor conditional gaps.

4 / 5

Workflow Clarity

A clear five-step sequence (locate → collect context → determine diff → review → output) with explicit decision checkpoints (stale selection stops, multiple changes prompt and stop, ambiguous baseline flagged "审查范围不完整") covers most validation needs for a read-only skill.

4 / 5

Progressive Disclosure

Content is organized into clearly headed sections with appropriately inline material; no bundle files exist so there are no references to mismanage, and the structure keeps navigation straightforward.

4 / 5

Total

16

/

20

Passed

Description

51%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 clearly states what the skill does and carves out a distinct read-only review niche, but it omits any "when to use" trigger and leans on technical jargon over natural user language.

Suggestions

Add an explicit 'Use when…' clause stating when a user should invoke this skill (e.g. 'Use when the user asks for a manual read-only review of a Comet change').

Include natural trigger phrases users would actually say, such as 'review', 'code review', or 'check my Comet change', alongside the technical terms.

Reword in third-person action voice and surface the key trigger keywords earlier in the description rather than burying them in domain-specific jargon.

DimensionReasoningScore

Specificity

The description names the domain (Comet change review) and several concrete actions — "只报告正确性、安全和边界问题" and "不推进工作流" — listing specific reportable issue types rather than vague abstractions.

4 / 5

Completeness

The "what" is clear (manual review of implementation differences, reporting only correctness/security/boundary issues), but there is no "when" clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

There is no "Use when…" trigger and the language is technical jargon ("Comet change", "实现差异") rather than natural phrases a user would actually say, leaving only minimal keyword coverage.

2 / 5

Distinctiveness Conflict Risk

The Comet-change niche and the explicit "不推进工作流" boundary make it mostly distinct from other skills, with only minor overlap risk against related verify/review skills.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rpamis/comet
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.