memory

Persistent memory system for preferences, facts, and notes

Quality

56%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/memory/SKILL.md

Quality

Discovery

32%

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 the core domain (memory/persistence) and lists what types of information it handles, but lacks concrete action verbs and completely omits trigger guidance. Without a 'Use when...' clause, Claude cannot reliably determine when to select this skill over others, significantly limiting its utility in a multi-skill environment.

Suggestions

Add a 'Use when...' clause with natural trigger phrases like 'remember this', 'save for later', 'recall what I told you', 'store this information'

Include specific action verbs describing capabilities: 'Stores, retrieves, and updates persistent memories including preferences, facts, and notes'

Add file extension or format triggers if applicable (e.g., 'memory files', '.mem') to improve distinctiveness

Dimension	Reasoning	Score
Specificity	Names the domain ('memory system') and some general categories ('preferences, facts, and notes'), but doesn't list concrete actions like 'store', 'retrieve', 'update', or 'delete' memories.	2 / 3
Completeness	Describes what it is (a memory system) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant terms ('memory', 'preferences', 'facts', 'notes') but misses common user phrases like 'remember this', 'save for later', 'recall', 'don't forget', or 'store information'.	2 / 3
Distinctiveness Conflict Risk	'Persistent memory system' is somewhat specific to memory/storage functionality, but 'notes' could overlap with note-taking skills and 'preferences' could conflict with settings/configuration skills.	2 / 3
	Total	7 / 12 Passed

Implementation

79%

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

This is a well-structured API reference with excellent actionability and conciseness. The code examples are complete and executable, and the content respects Claude's intelligence. However, it could improve by adding validation steps for destructive operations and potentially splitting the detailed API reference into separate files for better progressive disclosure.

Suggestions

Add explicit confirmation/validation guidance for destructive operations like '/forget all' (e.g., 'Always confirm with user before executing forgetAll')

Consider splitting into SKILL.md (quick start + chat commands) and API_REFERENCE.md (detailed TypeScript API) for better progressive disclosure

Add a brief workflow example showing when to use semantic search vs direct key lookup for common use cases

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, presenting API reference material without explaining concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context.	3 / 3
Actionability	Provides fully executable TypeScript code examples that are copy-paste ready, with concrete chat commands and complete API method signatures including all parameters and options.	3 / 3
Workflow Clarity	While individual operations are clear, there's no guidance on workflow sequences (e.g., when to use semantic search vs direct recall) and the destructive '/forget all' operation lacks validation/confirmation steps or warnings about irreversibility.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but this is a lengthy API reference (150+ lines) that could benefit from splitting into separate files (e.g., BACKENDS.md, EXAMPLES.md) with the main skill providing a quick-start overview.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

Reviewed: 29 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.