CtrlK
BlogDocsLog inGet started
Tessl Logo

memory

Use memory-as-tool to add and search memories throughout the Codex session.

56

Quality

62%

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 ./apps/oracle-agent-memory/codex-plugin/skills/memory/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a well-structured, actionable instruction-only skill with a clear decision boundary and a sequenced quick-pass workflow. Its main weakness is redundancy in the 'search by default' guidance, which is stated three times and could be consolidated for token efficiency.

Suggestions

Consolidate the redundant search-by-default guidance (lines 16, 23, and 25) into a single rule plus the bulleted trigger list.

Add a one-line example search call or sample query to make the quick-pass step concrete.

Give the Updating Memory section the same numbered-step treatment as the Quick Memory pass for a consistent workflow shape.

DimensionReasoningScore

Conciseness

Mostly efficient but the search-by-default guidance is repeated three times ('Search Memory early for most non-trivial repository work', 'run at least one quick Memory search before substantial exploration', 'If unsure, do a quick Memory search') and the trigger bullet list overlaps heavily with line 23's blanket rule. Consolidating these would tighten the body; the repetition keeps it below 4.

3 / 5

Actionability

Concrete, executable guidance throughout ('Extract a few task-relevant keywords', 'Call search with a concise query', 'If there are no relevant hits, stop', explicit criteria for good memories and what not to store). Minor gap: no example search query or add-call payload; per the scoring notes an instruction-only skill without code is acceptable when the guidance is actionable, which it is.

4 / 5

Workflow Clarity

The Quick Memory pass is a clear 4-step sequence with an explicit stop condition ('If there are no relevant hits, stop') and a verification checkpoint ('verify drift-prone facts against the repo'). Not 5 because the Updating Memory section offers prose bullets rather than an equivalent sequenced workflow.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is well organized into clear sections (boundary, quick pass, updating). Under the simple-skill guidance this qualifies for 5.

5 / 5

Total

16

/

20

Passed

Description

53%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 clearly states what the skill does (add and search memories via a memory tool) and is reasonably distinct, but it entirely lacks 'when to use' guidance and natural trigger phrases. Adding an explicit 'Use when...' clause with concrete triggers would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to remember, recall, or reference prior decisions, preferences, or earlier project context.'

Include natural user phrasings and synonyms (e.g. 'remember this', 'what did we decide', 'prior context', 'memory recall') to improve trigger-term coverage.

Briefly enumerate the memory capabilities (search by keyword, add durable facts, capture lessons learned) to strengthen specificity.

DimensionReasoningScore

Specificity

Names the domain ('memory-as-tool') and two concrete actions ('add and search memories'), matching the 1-2-concrete-actions anchor; it does not list several specific actions or cover what memories contain, so it falls short of 4.

3 / 5

Completeness

Has a clear 'what' (add and search memories) but no 'Use when...' clause or equivalent explicit trigger guidance; 'throughout the Codex session' only weakly implies when. Per the guideline, the missing trigger guidance caps this at 3, and it is above 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

Contains some relevant keywords ('memory', 'add', 'search', 'memories') but misses common variations and the natural phrases a user would actually say ('remember this', 'recall what we did', 'prior context'), so coverage is not good enough for 4.

3 / 5

Distinctiveness Conflict Risk

'memory-as-tool' carves a mostly distinct niche (persistent tool-based memory) with only minor overlap risk against closely related context/memory skills; it lacks the explicitly distinct trigger phrases needed for 5.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
oracle-devrel/oracle-ai-developer-hub
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.