comet-tweak

Comet 预设 —— 处理可收敛为单一 OpenSpec change 的轻量或中等变更。

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./assets/skills-zh/comet-tweak/SKILL.md

Quality

Content

73%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 content is a well-sequenced, highly actionable workflow with strong validation checkpoints and feedback loops, scoring high on actionability and workflow clarity. The main weakness is moderate redundancy across the escalation and delta-spec rules that could be tightened.

Suggestions

De-duplicate the 'delta spec is not an upgrade reason' rule and escalation conditions, stating them once in 升级判定 and linking from the build phase instead of repeating verbatim.

Consider moving the lengthy 升级判定 escalation criteria into its own reference file (e.g. escalation.md) and summarizing inline, to further trim the SKILL.md body.

Tighten repeated Skill-tool load phrasing (the '立即执行…禁止跳过此步骤' pattern recurs per phase) into a single stated convention referenced by each phase.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (direct commands, no beginner-concept padding), but several points are restated — notably the 'delta spec is not an upgrade reason' rule (~4 times) and escalation conditions (inline in build and again in 升级判定).	3 / 5
Actionability	It provides concrete, copy-paste-ready bash commands (comet state init/select/check, comet guard ... --apply, comet state transition ... preset-escalate) and explicit Skill-tool load instructions, with only minor placeholder gaps.	4 / 5
Workflow Clarity	The 4-phase open→build→verify→archive sequence has explicit validation checkpoints (guard transitions, BLOCKED bound_branch handling, verify_result:pass gate before archive), feedback loops (systematic-debugging/debug-gate on failures), and a defined escalation decision point.	5 / 5
Progressive Disclosure	Content is well sectioned into phases and supporting sections, with one-level-deep, clearly-signaled references to comet-classic/reference/*.md files; no local bundle files exist, and a modest amount of escalation detail is inlined rather than referenced.	4 / 5
	Total	16 / 20 Passed

Description

32%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 identifies a clear niche but is hampered by a generic action verb, jargon-heavy triggers, and a total absence of explicit 'Use when' guidance. It would benefit from naming concrete phase actions and adding a trigger clause.

Suggestions

Name the concrete actions the workflow performs, e.g. '快速开启、构建、验证并归档可收敛为单一 OpenSpec change 的轻量或中等变更'.

Add an explicit 'Use when...' trigger clause with natural phrases a user would actually say (e.g. 'Use when making a config tweak, doc/prompt edit, or small-to-medium spec-driven change that fits one OpenSpec change').

Replace pure jargon with at least one user-facing synonym (e.g. pair 'Comet 预设' with 'tweak workflow').

Dimension	Reasoning	Score
Specificity	It names the domain ('Comet 预设', 'OpenSpec change') but the only action verb is the generic '处理' (handle), with no concrete actions like open/build/verify/archive enumerated.	2 / 5
Completeness	It gives a moderately clear 'what' (handle lightweight/medium changes that converge to a single OpenSpec change) but entirely lacks any 'Use when...' trigger clause, so the 'when' is absent.	2 / 5
Trigger Term Quality	The terms are domain jargon ('Comet 预设', '可收敛为单一 OpenSpec change', '轻量或中等变更') rather than natural phrases a user would say; only one or two generic keywords appear.	2 / 5
Distinctiveness Conflict Risk	The Comet/OpenSpec-change niche is specific and distinct from generic skills, with only minor overlap risk against sibling Comet presets.	4 / 5
	Total	10 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: assets/skills-zh/comet-tweak/SKILL.md
Commit: 99fd749

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.