CtrlK
BlogDocsLog inGet started
Tessl Logo

context-memory

Multi-threaded conversation memory organized by topic instead of by date. Enables seamless context switching, compaction resilience, and sub-agent tracking — all file-based, no code changes to OpenClaw. Use when you want your agent to maintain separate conversation threads per project/topic, survive context compaction without losing the thread, track sub-agent spawns with model/task/duration, and output a structured conversation-map.json for visualization clients.

66

Quality

79%

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 ./clawd/skills/context-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 well-structured, concrete, and actionable, with clear sequenced workflows and filled format examples for an instruction-only memory skill. It could be tightened slightly and its validation checkpoints made more explicit, but it does not pad with concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is largely efficient with concrete file-format templates and examples, and avoids explaining concepts Claude already knows; minor restatement in the Integration and Token Efficiency sections keeps it just above the 'mostly efficient' midpoint rather than at 5.

4 / 5

Actionability

Provides concrete executable commands ('bash scripts/bootstrap.sh', 'mkdir -p memory/contexts/<name>/artifacts'), a concrete ID scheme (ctx-{DD}-{seq}), and filled file-format examples; minor gaps come from per-message steps being prose rather than copy-paste blocks.

4 / 5

Workflow Clarity

Multi-step processes (On Every Message, On Session Start/After Compaction, On Compaction) are clearly sequenced with implicit checkpoints (context-change detection, session-state write, COMPACTION log); not a 5 because validation is somewhat implicit rather than explicit verify-before-proceed loops.

4 / 5

Progressive Disclosure

Clear section structure with a real, well-signaled one-level reference to scripts/bootstrap.sh (verified present); all detailed file-format specs are inlined in SKILL.md, which is reasonable for a single-purpose skill but leaves minor organization gaps versus full content splitting.

4 / 5

Total

16

/

20

Passed

Description

83%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 clearly answers both what the skill does and when to use it with concrete trigger scenarios. It is distinguishable from generic memory skills, with only minor overlap and a slightly artifact-centric framing of triggers.

DimensionReasoningScore

Specificity

Lists several specific concrete capabilities ('organized by topic instead of by date', 'seamless context switching, compaction resilience, and sub-agent tracking', 'track sub-agent spawns with model/task/duration', 'output a structured conversation-map.json') with only minor gaps, fitting the 'several specific actions' anchor.

4 / 5

Completeness

Explicitly answers both what ('Multi-threaded conversation memory organized by topic instead of by date') and when via a concrete 'Use when you want your agent to...' clause enumerating four distinct trigger scenarios, matching the 'clearly and explicitly answers both' anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users might voice ('separate conversation threads per project/topic', 'survive context compaction', 'track sub-agent spawns') with good coverage; not a 5 because it lacks broader synonyms and 'conversation-map.json' is an artifact name rather than a user trigger.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (topic-based multi-threaded memory with sub-agent tracking and a visualization artifact) that is mostly distinct from generic memory skills, with only minor overlap risk; not a 5 because it still broadly concerns 'memory' which many skills touch.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
stukennedy/openclaw-starter-kit
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.