CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-memory

Use when Comet must decide whether a bounded semantic review packet contains a personal memory worth creating, updating, forgetting, or skipping.

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./assets/skills/comet-memory/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 an efficient, highly actionable instruction-only skill with a clear decision order and exact output-shape rules. Minor gaps are the repeated skip-rule emphasis and the absence of a full non-skip action example.

Suggestions

Add one complete create or update action JSON example so all action shapes are demonstrated, not just skip.

Consolidate the repeated 'return exactly one skip' guidance into a single canonical statement to improve token efficiency.

Provide a brief validation/retry note (e.g., what the reviewer returns on a transient failure) to close the workflow_clarity feedback-loop gap.

DimensionReasoningScore

Conciseness

The body is dense and rule-driven without explaining concepts Claude already knows, but the 'return exactly one skip' rule is restated across several sections and could be tightened.

4 / 5

Actionability

Exact field names, allowed enum values, and two JSON examples give mostly executable guidance; a full create/update action shape example is the main gap.

4 / 5

Workflow Clarity

A numbered six-step decision order is clearly sequenced with budget/scope constraints and Runtime re-validation acting as checkpoints, lacking only an explicit fix-retry loop.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Input boundary, Decision order, Examples, Fixed output, Common mistakes) with no nested references; no bundle files exist, so structure stands alone, but it slightly exceeds the simple-skill line count.

4 / 5

Total

16

/

20

Passed

Description

67%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 specific, third-person, and provides an explicit 'Use when...' trigger covering both what and when. It is held back from a 5 by jargon-heavy trigger phrasing that users would not naturally say.

Suggestions

Add natural-language trigger terms a user might actually say (e.g., 'remember this', 'forget that preference', 'save this habit') alongside the packet jargon.

Include common synonyms or surface phrasings to broaden natural keyword coverage for the trigger_term_quality dimension.

DimensionReasoningScore

Specificity

Names the domain (personal memory review) and four concrete actions ('creating, updating, forgetting, or skipping'), giving several specific actions with only minor coverage gaps.

4 / 5

Completeness

An explicit 'Use when...' clause answers both what (decide whether a memory is worth creating/updating/forgetting/skipping) and when, though the when clause leans on internal packet terminology.

4 / 5

Trigger Term Quality

Keywords like 'personal memory' and 'review packet' are relevant but 'bounded semantic review packet' is system jargon rather than natural user phrasing, and common synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The Comet-specific bounded memory-review niche with explicit create/update/forget/skip triggers is mostly distinct with only minor overlap risk against general memory skills.

4 / 5

Total

15

/

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.