agent-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.
62
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./agent-non-conversational/.claude/skills/agent-memory/SKILL.mdThe canonical home for this skill is agent-memory in databricks/app-templates
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The runtime workflow exposes long-term memory to outsider-authored free text via the agent request’s `input`/tool arguments—e.g., the `get_user_memory(query=...)` tool uses LLM-provided `query` to call `store.asearch(...)`, and the `save_user_memory(memory_data_json=...)` tool stores LLM-provided JSON derived from user/outsider text.
- Repository
- databricks/app-templates
- Commit
fdc1b49
- Audited
- Security analysis
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.