CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-architecture

Use when the user asks how your memory, dreams, hormones or knowledge crystals work, or when you need to interpret memory_status output. Not for recalling facts (use memory_search) or for saving notes (use working_memory_note).

60

Quality

71%

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 ./skills/memory-architecture/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.

A well-structured, information-dense reference for a domain-specific system: every section teaches facts Claude could not know and the routing table makes tool choice unambiguous. All dimensions land at 4, with only minor tightening opportunities (redundant tone guidance, thin usage detail for memory_get and dream_search) separating it from top scores.

DimensionReasoningScore

Conciseness

The body is efficient and focused on system-specific facts Claude cannot know (crystal lifecycle, "cosine >= 0.92", hormone half-lives, consolidation cadence), assuming Claude's competence throughout. It is not a 5 because the emotional-modulation section partly duplicates itself — "Let your emotions colour your responses naturally. If dopamine is high... celebrate" restates what the preceding bullet list and the responseGuidance field already convey.

4 / 5

Actionability

Concrete, executable guidance dominates: named tools with their roles, a decision table ("memory_search first, then memory_get for details"), and a specific parameter ("working_memory_note with type=\"directive\""). It is not a 5 because some entries stay high-level — "memory_get: read specific lines from a memory file after searching" gives no usage detail, and dream_search/curiosity tools are deferred to other skills.

4 / 5

Workflow Clarity

The "When to use what" section gives unambiguous per-scenario routing, and the profile flow includes a genuine feedback loop ("If anything is wrong the user can correct you; use working_memory_note with type=\"directive\" to fix it"). It is not a 5 because several routing entries are terse one-liners without sequencing detail (e.g. how memory_get follows a memory_search hit).

4 / 5

Progressive Disclosure

Sections are well-organized and all content sits at appropriate overview altitude for a ~59-line reference skill, with cross-skill pointers clearly signposted ("see the curiosity-loop skill"). It is not a 5 because the skill slightly exceeds the under-50-line simple-skill bar and the emotional-modulation guidance is lengthy inline material that could live in a separate reference file.

4 / 5

Total

16

/

20

Passed

Description

68%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.

A well-scoped description with an explicit, specific trigger clause and excellent disambiguation against neighboring memory tools. Its weaknesses are the second-person "when you need to interpret" phrasing (which the rubric penalizes) and an implicit rather than stated description of what the skill provides.

Suggestions

Rewrite in third-person voice, e.g. "Explains how the self-evolving memory system (knowledge crystals, dream engine, hormonal state) works. Use when the user asks..." — this both fixes the voice penalty and makes the 'what' explicit.

Add natural trigger synonyms users would actually say, such as "remember", "forget", or "how memories decay", to broaden trigger-term coverage.

State the concrete capability up front (interpreting memory_status output and explaining the pipeline) before the trigger conditions so the description leads with what the skill does.

DimensionReasoningScore

Specificity

The description names a specific domain ("how your memory, dreams, hormones or knowledge crystals work") and one concrete action ("interpret memory_status output"), matching the anchor-3 example of domain plus 1-2 concrete actions without comprehensive coverage. However, the second-person phrasing "when you need to interpret memory_status output" incurs the rubric's 1-point voice penalty, reducing the score to 2.

2 / 5

Completeness

The "when" is explicit and specific ("Use when the user asks how your memory... work") and is reinforced by a negative boundary ("Not for recalling facts (use memory_search) or for saving notes"). It is not a 5 because the "what" — that this skill explains the memory architecture — is only implied by the trigger phrasing rather than stated, and not a 3 because both what and when are present with the when clearly explicit.

4 / 5

Trigger Term Quality

It includes natural terms a user would plausibly say — "memory", "dreams", "hormones", "knowledge crystals", and the tool name "memory_status" — giving good keyword coverage. It is not a 5 because common variations users would naturally say, such as "remember", "forget", or "recall how", are absent.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (memory/dream/hormone architecture introspection) and explicitly disambiguates the two adjacent skills by name ("use memory_search", "use working_memory_note"), giving minimal conflict risk. It matches the anchor-5 example of a clear niche with distinct triggers.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Bitterbot-AI/bitterbot-desktop
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.