CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-tweak

Comet preset path: Non-bug small changes (tweak). Skip brainstorming and full plan, directly open → lightweight build → light verify → archive. Applicable for copy, configuration, documentation or prompt local optimization.

63

Quality

74%

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 ./eval/local/skills/benchmarks/039-release/comet-classic-039-tweak/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is a well-sequenced, highly actionable preset workflow with explicit phase guards, validation gates, and upgrade/degradation rules. Its main weakness is moderate repetition of the execution chain and boilerplate imperative phrasing that inflates token cost without adding clarity.

Suggestions

State the 'open → lightweight build → light verify → archive' execution chain once up front and remove the later repetitions to save tokens.

Consolidate the repeated 'Immediately execute: Use the Skill tool to load X. Skipping this step is prohibited.' pattern into a single stated convention referenced by each phase.

Consider moving the Upgrade Conditions table and Continuous Execution Mode detail into a referenced file to slim the inline body while keeping the overview navigable.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but repeats the execution chain ('open → lightweight build → light verify → archive') and the 'Skipping this step is prohibited' / 'Immediately execute' phrasing several times, which could be tightened.

3 / 5

Actionability

Provides concrete, executable guidance — specific bash commands, named skills to load via the Skill tool, artifact filenames, and a commit-message format — with only minor gaps around externally-delegated protocols.

4 / 5

Workflow Clarity

Clear four-phase sequence with explicit validation checkpoints (phase guards, verify_result:pass before archive), feedback loops (systematic-debugging + debug-gate.md on failures), and checklists (applicable conditions, upgrade-conditions table, exit conditions).

5 / 5

Progressive Disclosure

Well-organized with clear section headers and clearly-signaled one-level references (comet/reference/dirty-worktree.md, debug-gate.md, decision-point.md, auto-transition.md); no local bundle files exist, and some dense inline content keeps it just short of a 5.

4 / 5

Total

16

/

20

Passed

Description

75%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 is concise and concrete, naming the tweak preset path, its skipped phases, and the four-phase execution chain alongside explicit applicability scenarios. It is strong on specificity and triggers but uses 'Applicable for' instead of a canonical 'Use when' trigger clause.

Suggestions

Replace 'Applicable for ...' with an explicit 'Use when ...' trigger clause (e.g., 'Use when making non-bug small changes such as copy, configuration, documentation, or prompt local optimization').

Add a couple of natural synonyms/file cues to broaden trigger coverage (e.g., 'typo fix', 'config tweak', 'doc edit').

Briefly distinguish from the parent /comet workflow in the description itself to reduce sibling-skill conflict risk.

DimensionReasoningScore

Specificity

Lists several concrete workflow actions ('Skip brainstorming and full plan', 'directly open → lightweight build → light verify → archive') rather than vague language, with minor gaps in what each phase entails.

4 / 5

Completeness

Answers both what (the preset path and its four-phase chain) and when ('Applicable for copy, configuration, documentation or prompt local optimization'), but the trigger is phrased as 'Applicable for' rather than an explicit 'Use when' clause and could be slightly more explicit.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('tweak', 'non-bug small changes', 'copy', 'configuration', 'documentation', 'prompt local optimization'); solid coverage though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche ('Comet preset path' for non-bug small changes) with distinct triggers, carrying only minor overlap risk with sibling comet skills.

4 / 5

Total

16

/

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.