CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

comet-hotfix

使用 Classic 预设流程修复局部缺陷。在用户明确调用 /comet-hotfix、选择 hotfix,或恢复 workflow: hotfix 时使用。

Quality

79%

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

Quality

Content

67%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.

A densely procedural skill with genuinely executable command templates and a well-checkpointed escalation/approval workflow. Its main weaknesses are redundant repetition of the state-continuation rules, extremely long run-on sentences that hurt readability, and a referenced local file (reference/compat.md) that does not exist in the bundle.

Suggestions

Consolidate the continuation/nextAction reuse rules (currently repeated in the section intro, the step preamble, and the closing paragraph) into a single statement; state the cold-recovery exception once instead of three times.

Break the numbered SDK steps into shorter sub-steps (especially step 1 and step 2, which are single run-on sentences covering 5+ commands) so the open → build → verify → archive sequence and its checkpoints are scannable.

Fix or remove the broken local reference: the body instructs loading [Compat 操作](reference/compat.md) but no reference/ directory exists in the skill bundle; either ship the file or point to its actual location.

DimensionReasoningScore

Conciseness

The body contains no concept explanations Claude already knows and no padding, but the continuation/nextAction routing rules are repeated across three separate paragraphs (「优先复用当前有效结果中的 agent.continuation / data.nextAction」 appears in the intro, step preamble, and closing paragraph), and the cold-recovery condition is restated multiple times. It is mostly efficient but could be tightened by consolidating these rules into one place.

3 / 5

Actionability

Commands are concrete, copy-paste-ready templates with real flags (e.g. `comet state init <name> hotfix --isolation <selected-isolation>`, `comet guard <change-name> open --apply --approval-hash <approvalHash>`, `comet state decide-escalation <change-name> --proposal-hash <proposalHash> --choice <continue|upgrade>`). Minor gaps remain: critical procedures (缺陷复现、根因消除、升级判定) are deferred to external SDK reference sections, and placeholders like `<checks-json-file>` are never specified, keeping it below fully-executable.

4 / 5

Workflow Clarity

The open → build → verify → archive sequence is enumerated in numbered steps with explicit checkpoints: preview + approval-hash before apply, mandatory re-preview after artifact changes, escalation proposal/decision gates, reproduce-and-save-evidence before fixing, and explicit 'do not redo when results unclear' recovery rules. It falls short of 5 because the checkpoints are buried in very long run-on sentences that make the sequence hard to follow, and verify/archive validation is delegated to other skills rather than restated.

4 / 5

Progressive Disclosure

References are clearly signaled one level deep with named sections (e.g. [阶段入口与恢复](../comet-classic/reference/sdk-methods.md#阶段入口与恢复), [Compat 操作](reference/compat.md)), and detail is appropriately split out of the overview. However, the local bundle contains no reference files — `reference/compat.md` is absent from the skill directory — so at least one referenced path is unverifiable/broken here, and the cross-skill `../comet-*` paths cannot be validated from this bundle.

4 / 5

Total

15

/

20

Passed

Description

82%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.

A strong description: it states what the skill does, gives three explicit and concrete trigger conditions, and is deliberately scoped to explicit invocation, which keeps conflict risk low. The only weakness is that the capability side is thin — a single generic action ('fix local defects via the preset process') with no enumerated concrete actions.

DimensionReasoningScore

Specificity

「使用 Classic 预设流程修复局部缺陷」 names the domain (local defect repair) and a single action (run the Classic preset process), matching the 'domain plus 1-2 concrete actions' anchor. It does not list several specific actions (not 4) but goes beyond a bare domain claim like 'Processes PDF files' (not 2).

3 / 5

Completeness

Both questions are answered explicitly: the what is「使用 Classic 预设流程修复局部缺陷」and the when lists three concrete trigger conditions (explicit /comet-hotfix invocation, hotfix selection, workflow: hotfix resume). This matches the 5 anchor's pattern of clear what + explicit when with concrete trigger phrases; the 4 anchor's caveat (when only weakly specified) does not apply.

5 / 5

Trigger Term Quality

Triggers「调用 /comet-hotfix」「选择 hotfix」「恢复 workflow: hotfix」 give three natural, distinct invocation phrasings with good coverage. Common variations users might say (e.g. 缺陷修复, bug 修复, patch) are missing, so it falls just below the comprehensive-synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The description triggers only on explicit signals (/comet-hotfix, hotfix selection, workflow: hotfix resume), giving it a clear niche with minimal overlap risk against sibling skills like /comet-classic. It is far from generic, so the lower overlap-risk anchors do not fit.

5 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 possibly missing (reference/compat.md), 6 suspicious

Warning

Total

15

/

16

Passed

Repository

rpamis/comet

Path

assets/skills-zh/comet-hotfix/SKILL.md

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.