CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-any

通过 Comet Creator 创建或升级 Comet Classic workflow Skill。不用于一般 Skill 的编写、整理或评审。

55

Quality

61%

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-any/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 skill body delivers a strongly sequenced, validation-rich workflow with concrete CLI commands and a worked example, but step 7 is verbose and the reference section names files that are neither linked nor present in the local bundle.

Suggestions

Format the 参考资料 entries as markdown links and confirm the referenced files exist in the skill's own references/ directory (or note they are generated at runtime), so progressive disclosure is clearly navigable.

Break the dense step 7 into sub-steps or move the wave/lane DAG orchestration detail into a referenced file, keeping the main workflow lean.

Trim the repeated enforcement-term lists (guarded/handoff-guarded/evidence-only/advisory appears in both step 4 and 硬性规则) to a single canonical statement.

DimensionReasoningScore

Conciseness

The body is dense and appropriately defines Comet-specific terms Claude would not know, but step 7's long orchestration narrative and the repeated enforcement lists could be tightened, fitting the 'mostly efficient but could be tightened' anchor.

3 / 5

Actionability

Provides concrete, flag-complete CLI commands (comet creator guide/init/authoring-plan/authoring-record/generate, comet publish review) plus a copy-paste JSON plan example, but placeholders and the descriptive wave/lane narrative leave minor gaps versus fully copy-paste-ready execution.

4 / 5

Workflow Clarity

Ten clearly sequenced steps with explicit validation checkpoints (confirmation page, pause on ambiguity, eval-hash freshness, readiness Blockers/Warnings), error-recovery handling (BLOCKED/NEEDS_CONTEXT rejection, failure blocks ready), and a hard-rules checklist, matching the top anchor including feedback loops.

5 / 5

Progressive Disclosure

The body is well sectioned and lists five one-level-deep references, but the referenced paths (comet-any/reference/...) are not present in the actual bundle (no references/ dir) and are shown as plain backtick paths rather than clearly signaled links, fitting the 'references present but not clearly signaled' anchor.

3 / 5

Total

15

/

20

Passed

Description

53%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 states a clear purpose and a strong negative scope boundary, making it highly distinct, but it stops short of an explicit positive trigger clause and offers only two concrete actions with no keyword synonyms.

Suggestions

Add an explicit positive 'Use when...' clause (e.g. 'Use when the user wants to create or upgrade a Comet Classic workflow Skill'), since the current 'when' is only a negative exclusion.

Expand the action list beyond create/upgrade (e.g. propose, verify, publish-preview) and add natural synonyms/variants users might say to lift specificity and trigger coverage.

Consider naming the concrete deliverable (a verifiable Comet-native Skill Bundle) so the 'what' is more tangible at a glance.

DimensionReasoningScore

Specificity

Names the domain ("Comet Classic workflow Skill") and two concrete actions ("创建或升级" / create or upgrade), matching the anchor for domain plus 1-2 actions, but coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (create/upgrade Comet workflow Skills via Comet Creator), but the only 'when' guidance is a negative exclusion ("不用于一般 Skill 的编写、整理或评审") with no explicit positive 'Use when...' trigger, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Contains relevant terms (Comet Creator, Comet Classic, workflow Skill, 创建, 升级) but relies on niche jargon with no synonyms or natural user variations, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Carves a clear specialized niche and explicitly disambiguates from general Skill authoring/review skills, giving minimal conflict risk; just below 5 because it lacks the explicit 'Use when...' trigger phrasing of the top anchor.

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.

Validation16 / 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.