CtrlK
BlogDocsLog inGet started
Tessl Logo

remember

Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, actionable, and well-structured with a clear sequenced workflow and explicit validation checkpoints gated on user approval. Progressive disclosure is appropriately handled for a self-contained instruction skill.

DimensionReasoningScore

Conciseness

The ~50-line body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; every section earns its place, including the success-criteria checkpoints.

3 / 3

Actionability

It names specific files (OPENSPACE.md, OPENSPACE.local.md, MEMORY.md), the memory_read tool, a concrete destination table with examples, and an explicit report structure — fully actionable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

A clear 4-step sequence (Gather → Classify → Identify cleanup → Present report) is given, each with explicit success criteria as validation checkpoints, and the Rules gate destructive changes on explicit user approval.

3 / 3

Progressive Disclosure

No bundle files are needed and the single under-50-line file is well-organized into Goal, Steps, and Rules sections, satisfying the simple-skill exception for progressive disclosure.

3 / 3

Total

12

/

12

Passed

Description

67%

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 and distinct, clearly stating concrete actions and named destinations. Its main weakness is the absence of an explicit 'Use when...' trigger clause and limited natural-language trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when reviewing or cleaning up memory, or when proposing changes to OPENSPACE.md / OPENSPACE.local.md.'

Broaden trigger terms to include natural user phrasings such as 'memory cleanup', 'organize memory', or 'review memory'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Review auto-memory entries', 'propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics', 'detect duplicates, stale facts, conflicts, and ambiguous entries') with named destinations, matching the highest anchor.

3 / 3

Completeness

It clearly states what the skill does but never provides an explicit 'Use when...' trigger clause, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant keywords exist ('memory', 'duplicates', 'conflicts', 'stale facts') but it lacks common natural phrasings a user would actually say (e.g. 'clean up memory', 'organize memory'), so coverage is partial rather than broad.

2 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (memory review/promotion to specific OpenSpace files) with distinct triggers and named destinations, making it unlikely to fire for the wrong skill.

3 / 3

Total

10

/

12

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
HKUDS/OpenSpace
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.