CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-openai-memory

Add memory capabilities to your agent. Use when: (1) User asks about 'memory', 'state', 'remember', 'conversation history', (2) Want to persist conversations or user preferences, (3) Adding checkpointing or long-term storage.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

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.

A well-structured, highly actionable template guide with executable code, config, and testing commands organized into clear sections. The single weakness is mild verbosity in the conceptual 'How Sessions Work' introduction that could be tightened.

Suggestions

Trim the 'How Sessions Work' conceptual explanation and drop the sentence 'This eliminates the need to manually manage conversation state between runs' to assume Claude's competence and lift conciseness to 3.

DimensionReasoningScore

Conciseness

The body is mostly lean code, config, and tables, but the 'How Sessions Work' section explains generic session mechanics and 'This eliminates the need to manually manage conversation state between runs' is explanatory padding that assumes less of Claude's competence, fitting the score-2 anchor rather than the fully lean score-3 anchor.

2 / 3

Actionability

Executable Python, YAML, and curl blocks are concrete and copy-paste ready (e.g., the AsyncDatabricksSession construction, databricks.yml resource, and curl invocations), matching the score-3 anchor for fully executable guidance.

3 / 3

Workflow Clarity

The guide is clearly sequenced (Prerequisites → Configuration Files → Testing → Troubleshooting) with concrete commands at each stage; no destructive or batch operations are present that would require validation feedback loops, so the simple-skill allowance applies and clarity is unambiguous.

3 / 3

Progressive Disclosure

No bundle files exist, and the body is a self-contained, well-organized set of clearly signaled sections with no nested references, satisfying the score-3 anchor for well-organized content with easy navigation.

3 / 3

Total

11

/

12

Passed

Description

90%

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 strong description with explicit 'Use when' triggers and good natural keyword coverage. Its only weakness is specificity: it states one action ('Add memory capabilities') rather than enumerating several concrete capabilities.

Suggestions

Expand the 'what' clause to list multiple concrete capabilities (e.g., 'persist conversation history, store user preferences, and add checkpointing to your agent') to lift specificity from 2 to 3.

DimensionReasoningScore

Specificity

"Add memory capabilities to your agent" names the domain and a single action but does not list multiple concrete actions (compare the score-3 anchor 'extract text, fill forms, merge documents'), so it is not comprehensive enough for a 3.

2 / 3

Completeness

It explicitly answers both what ("Add memory capabilities to your agent") and when ("Use when: (1) ... (2) ... (3) ..."), with explicit triggers, matching the score-3 anchor; it is not the 2 anchor because the 'when' is explicit rather than implied.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered — 'memory', 'state', 'remember', 'conversation history', 'persist conversations', 'user preferences', 'checkpointing', 'long-term storage' — matching the score-3 anchor for good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

The agent conversation-state/checkpointing niche with specific triggers is clearly distinguishable from other skills and unlikely to fire for the wrong skill; it is not the 2 anchor because the triggers are specific rather than broadly overlapping.

3 / 3

Total

11

/

12

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
databricks/app-templates
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.