Agent skill for memory-coordinator - invoke with $agent-memory-coordinator
35
0%
Does it follow best practices?
Impact
95%
1.53xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-memory-coordinator/SKILL.mdNamespace and key naming conventions
Dollar-sign key separator
0%
100%
project$feature$agent key pattern
0%
100%
project/ namespace
100%
100%
coordination/ namespace
0%
50%
patterns/ namespace
0%
50%
TTL differentiation
100%
100%
Ephemeral task data TTL
100%
100%
Metadata / purpose documentation
100%
100%
Four-tier hierarchy
75%
100%
Cleanup / garbage collection
100%
100%
Namespace organisation by project$feature$agent
30%
100%
Caching strategy and security architecture
Encryption at rest
100%
100%
Access control lists
87%
100%
Audit logging
100%
100%
Hot data in fast storage
100%
100%
Cold data compressed
20%
100%
Deduplication
25%
100%
Sharding by namespace
40%
100%
Smart indexing
100%
100%
Garbage collection / cleanup
100%
100%
Namespace-level organisation
62%
100%
Data retention / compliance
100%
100%
TTL policy
100%
100%
Task orchestration memory integration
Stores task decomposition / phase plans
60%
60%
Execution state persistence
100%
100%
Results shared between stages via memory
100%
100%
Memory chains / linked entries
50%
100%
Dependency tracking
100%
100%
coordination/ namespace
0%
100%
Four-tier hierarchy used
20%
100%
Task-level ephemeral cleanup
100%
100%
Metadata / purpose on entries
62%
75%
Dollar-sign key naming
0%
100%
TTL for temporary data
25%
100%
f547cec
Table of Contents
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.