CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-manage

Unified memory management - CLAUDE.md updates and documentation generation with interactive routing. Triggers on "memory manage", "update claude", "update memory", "generate docs", "更新记忆", "生成文档".

63

Quality

75%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/memory-manage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 router skill that clearly defines how to parse user input, interactively assess needs, and dispatch to specialized phase documents. The actionability is strong with concrete AskUserQuestion payloads and routing tables. The main weakness is moderate verbosity—the ASCII diagram and some repeated information could be trimmed—but overall the content is functional and well-organized.

DimensionReasoningScore

Conciseness

The ASCII architecture diagram and interactive flow details are somewhat verbose, but most content is functional. The bilingual (Chinese/English) labels add some overhead but serve a real purpose for the target audience. Some tables could be tighter.

2 / 3

Actionability

Provides concrete routing rules with priority order, specific AskUserQuestion payloads with exact option structures, direct dispatch examples with input→output mappings, and precise parameter tables. The guidance is specific and executable.

3 / 3

Workflow Clarity

Clear 3-step sequence (Parse → Interactive Assessment → Execute) with explicit routing logic, decision trees for each branch, and error handling table. The flow from ambiguous input through interactive questions to phase execution is well-defined with validation (route before execute, user confirmation per sub-command).

3 / 3

Progressive Disclosure

Excellent progressive disclosure: SKILL.md serves as a router/overview, with all execution logic delegated to clearly referenced phase documents (phases/01-05). References are one level deep, well-signaled in a table, and explicitly marked as read-on-demand. However, no bundle files were provided to verify the referenced paths exist.

3 / 3

Total

11

/

12

Passed

Description

64%

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 its domain (memory management and CLAUDE.md updates) and provides explicit trigger terms in multiple languages, which is a strength. However, it lacks specificity about what concrete actions it performs beyond vague categories, and the absence of a clear 'Use when...' clause with contextual guidance weakens its completeness. The term 'unified' and 'interactive routing' feel like internal jargon rather than user-facing clarity.

Suggestions

Add a 'Use when...' clause that explains the scenarios in which this skill should be selected, e.g., 'Use when the user wants to persist information across sessions, update project-level instructions in CLAUDE.md, or auto-generate documentation from code.'

Replace vague terms like 'unified memory management' and 'interactive routing' with concrete actions, e.g., 'Adds, updates, or removes entries in CLAUDE.md; generates README or API documentation from project files.'

Narrow the scope of 'documentation generation' to distinguish it from general doc-writing skills, e.g., specifying it generates docs specifically tied to memory/context persistence.

DimensionReasoningScore

Specificity

Names the domain (memory management, CLAUDE.md updates, documentation generation) and mentions 'interactive routing', but doesn't list specific concrete actions beyond general categories. What does 'unified memory management' actually do in practice?

2 / 3

Completeness

The 'what' is partially covered (memory management, CLAUDE.md updates, doc generation), and trigger terms are listed, but there's no explicit 'Use when...' clause explaining the conditions under which Claude should select this skill. The trigger terms serve as partial 'when' guidance but don't fully explain the use cases.

2 / 3

Trigger Term Quality

Explicitly lists multiple natural trigger terms including 'memory manage', 'update claude', 'update memory', 'generate docs', and even Chinese equivalents '更新记忆', '生成文档'. These are terms users would naturally say.

3 / 3

Distinctiveness Conflict Risk

The mention of CLAUDE.md and memory management gives it some distinctiveness, but 'documentation generation' is very broad and could overlap with many other documentation-related skills. The specific trigger terms help reduce conflict somewhat.

2 / 3

Total

9

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

10

/

11

Passed

Repository
catlog22/Claude-Code-Workflow
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.