observations · git:20261015.b3cb7c0 · 2026-10-15 · sha256 4e29ab1161085205

observations git:20261015.b3cb7c0A

Immutable. This exact content never changes and is served at /api/v1/blob/4e29ab1161085205.

---
name: observations
description: List recent captured session observations (the summarized voyage logs). Use when the user wants to see what Captain Memo has logged from past sessions.
---

# Captain Memo — recent observations

When the user invokes this skill, they want a quick view of recent session observations — the structured "voyage logs" the summarizer writes from a session's tool events.

## What to do

1. Parse the user's argument as `--limit N` (default 20). If they typed `/captain-memo:observations 50`, treat 50 as the limit.
2. Run:

```bash
captain-memo observation list --limit <LIMIT>
```

The CLI sends the worker's secret for you: there is no token to handle. If `captain-memo` is not on PATH, use the shim and checkout fallbacks described in the `doctor` skill. With no CLI at all (a plugin-only install), call the MCP tool `search_observations` with a query instead; it has no plain "recent" listing.

3. Pass the output back as it is. It is one line per observation, newest first, then a row count.

## Output format

```
Recent observations
---
2026-05-07T14:32:10  [bugfix    ]  Fix off-by-one in pagination loop
2026-05-07T14:18:44  [feature   ]  Add retry to the embed call on HTTP 429
(2 rows)
```

The timestamp is UTC. For a hit worth reading in full, `search_observations` or `search_all` returns its `doc_id` and `get_full` opens it.

## If empty

Say something like:
> "No observations yet. Tool events are summarised shortly after each turn, so an empty list usually means no session has run since installing, or no summarizer is live — `captain-memo stats` shows which one is live, `captain-memo doctor` says why it is not."