EXAMPLES.md
# recall worked examples
## 1. Hit on a past decision
User: "Did we ever decide how to cache sessions?"
Invocation:
```json
memory_smart_search { "query": "session caching decision", "limit": 10 }
```
Response:
```json
{
"results": [
{ "sessionId": "7f3a9c21", "type": "decision", "title": "Drop Redis for iii state store",
"narrative": "We decided to drop Redis and use the iii-engine state store for session caching.",
"importance": 8 }
]
}
```
Present:
> Yes. In session `7f3a9c21` you decided to drop Redis and use the iii-engine
> state store for session caching (importance 8).
## 2. Multiple results across sessions
User: "Recall anything about the rate limiter."
Invocation:
```json
memory_smart_search { "query": "rate limiter", "limit": 10 }
```
Response:
```json
{
"results": [
{ "sessionId": "b21d004e", "type": "code", "title": "limit.ts counts per-IP",
"narrative": "Rate limiter counts per-IP, not per-user.", "importance": 6 },
{ "sessionId": "c98f1100", "type": "conversation", "title": "Discussed sliding window",
"narrative": "Considered a sliding-window limiter, deferred.", "importance": 4 }
]
}
```
Present them grouped by session, leading with the per-IP code note.
## 3. No results
User: "Recall the GraphQL schema migration."
Invocation:
```json
memory_smart_search { "query": "graphql schema migration", "limit": 10 }
```
Response:
```json
{ "results": [] }
```
Present:
> No memories matched that. Try `schema change`, `graphql`, or `migration` as
> narrower terms, or `recap this week` to scan recent sessions.
SKILL.md
---
name: recall
description: Search agentmemory for past observations, sessions, and learnings about a topic using hybrid BM25 plus vector plus graph search. Use when the user says "recall", "what did we do about", "did we ever", "have we seen", or needs context from past sessions.
argument-hint: "[search query]"
user-invocable: true
---
The user wants to recall past context about: $ARGUMENTS
## Quick start
```json
memory_smart_search { "query": "jwt refresh token rotation", "limit": 10 }
```
Expected output:
```text
2 results across 2 sessions.
[importance 8] decision · "Rotate refresh tokens on every use" (session 7f3a9c21)
[importance 5] code · "limit.ts counts per-IP" (session b21d004e)
```
## Why
Only surface what the tool returned. Never fabricate an observation, a session
id, or an importance score. If nothing comes back, say so.
## Workflow
1. Call `memory_smart_search` with the user's text as `query` and `limit: 10`.
Pass `project` when the user scopes to a specific repo and `agentId` when
they request one agent's history.
Use `targetLayer: "memory"` for explicitly saved knowledge, or
`targetLayer: "observation"` for captured activity. Omit it for mixed search.
2. Search results are compact. Before quoting full content or describing
provenance, call `memory_smart_search` with the selected IDs as a
comma-separated `expandIds` string and the same project, agent, and layer
filters. If expansion fails or the record is no longer available, report
that limitation; a title alone is not the full fact.
3. Group expanded observations by session and show the returned type, title,
and narrative. Include provenance only when the response supplies it.
4. Lead with the high-signal observations (importance >= 7).
5. With `memory_recall`, inspect `matched_count`, `excluded_by_budget`, and
`content_truncated` before treating an empty or shortened response as absent
knowledge. Recover full content with `memory_smart_search` using `expandIds`
and the same project, agent, and layer filters. `minimum_budget` reports the
estimated budget needed for a minimal preview when the budget is too small.
6. If there are no matches, suggest 2-3 alternative search terms and stop. Do not guess.
## Anti-patterns
WRONG: results are empty, so you write "We probably discussed token expiry last
week" from assumption.
RIGHT: "No memories matched that query. Try `refresh token`, `session expiry`,
or `auth rotation`."
## Checklist
- Every observation shown came from the tool response.
- Results grouped by session, high-importance first.
- Empty results trigger alternative-term suggestions, not invention.
- No session id or score was paraphrased or rounded.
## See also
- `remember`: the write side; recall retrieves what it stores.
- `recap`, `handoff`, `session-history`: session-scoped views of the same data.
- `memory-discipline`: when to run this search unprompted.
## Troubleshooting
See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) if `memory_smart_search` is not available.
TROUBLESHOOTING.md
<!-- AUTOGEN:troubleshooting START - generated by scripts/skills/generate.ts, do not edit by hand -->
# Troubleshooting agentmemory skills
Recovery steps for separately installed skills. This document is generated into
each skill directory so native skill readers can open it without parent traversal.
## "MCP tool not available"
Missing tools can mean a stopped MCP process, a disconnected daemon, or an
explicitly reduced tool surface. Walk these in order:
1. Identify the host. In Claude Code, inspect `/plugin list` and `/mcp`.
In Hermes, inspect the configured memory provider and `mcp_servers` separately.
In OpenClaw, validate the host configuration and inspect its MCP servers and
native plugins separately. In Pi or OMP, inspect `/agentmemory-status` and the
MCP inventory separately; native save/search does not prove the broader tools
are connected. Do not run another host's setup commands.
2. Restart or reload the affected host connection after configuration changes.
3. Inspect the connected tool inventory. Hermes may namespace MCP tools; invoke
the actual advertised names and schemas. A native memory provider is not
proof that every MCP tool or shared skill is available.
4. Check `agentmemory status` and the daemon's `AGENTMEMORY_TOOLS` setting.
Codex's bundled bridge lists the daemon's enabled tools. The standalone shim
used by other hosts can fall back to seven basic tools with a separate store.
Do not claim full daemon functionality based on those seven tools.
5. If `agentmemory connect codex` and the Codex plugin are both enabled, choose
one MCP connection. Check `/hooks` before adding global hook fallbacks.
Hermes, OpenClaw, Pi and OMP connector installations bundle skills; other hosts
may install them separately. Check the host's skill inventory and open this file
from the installed skill directory. Test automatic capture with a real turn and
a recorded observation; tool connectivity alone does not establish lifecycle
capture.
An outage or timeout is not an empty search result. Report the failure. A write
may have committed before the response was lost; inspect state before retrying.
## REST fallback
When the MCP tools stay unavailable but the daemon is running, call the REST
API directly:
1. Set `AGENTMEMORY_URL` to the daemon base URL (default `http://localhost:3111`).
2. The REST API requires a bearer credential by default. Use the host's explicit
`AGENTMEMORY_SECRET`; for loopback URLs only, fall back to the secret in
`~/.agentmemory/.env` and then `~/.agentmemory/secret`. Load the value locally
without displaying it. Never send a local-file secret to a remote URL.
If `AGENTMEMORY_CREDENTIAL_MODE=explicit`, require the explicit host credential
and do not read local credential files.
Authenticated REST fallback requests require HTTPS for non-loopback
URLs; HTTP is allowed for loopback URLs (`localhost`, `127.0.0.0/8`, or `[::1]`).
Reject redirects on authenticated requests. Do not print or save the secret.
Endpoint map by skill:
| Skill | REST call |
| --------------- | --------------------------------------------------------------- |
| remember | `POST /agentmemory/remember` |
| recall | `POST /agentmemory/smart-search` |
| recap | `GET /agentmemory/sessions` + `POST /agentmemory/smart-search` |
| handoff | `GET /agentmemory/sessions` + `POST /agentmemory/smart-search` |
| session-history | `GET /agentmemory/sessions` |
| commit-context | `GET /agentmemory/session/by-commit?sha=<sha>` |
| commit-history | `GET /agentmemory/commits` (URL-encode every query param) |
The MCP host reads the plugin MCP configuration. Restart the daemon after
changing its configuration, then restart or reconnect the host MCP process after
changing its URL or explicit secret. The local bridge reads the credential files
for each request; it does not inherit other daemon `.env` settings.
<!-- AUTOGEN:troubleshooting END -->