Trellis Session Insight

This skill teaches an AI how to call trellis mem — the project's cross-session memory feedstock — and when reaching for it is the right move.

It is intentionally a capability skill, not a workflow. There is no fixed output file, no required write-back step, no "always run after finish-work" rule. What to do with what mem returns is a judgement call made in the moment of the conversation. The skill exists so the AI knows the capability is there and can decide.

What trellis mem is

A local CLI that indexes the user's past Claude Code, Codex, Devin CLI, Grok, OpenCode, Pi Agent, and ZCode conversation logs and lets you list, search, slice by Trellis task boundaries, and dump cleaned dialogue from them. Claude and Codex use ~/.claude/projects/ and ~/.codex/sessions/. Devin CLI (Cognition terminal agent, not trellis init --devin Desktop) uses ~/.local/share/devin/cli/sessions.db. Grok uses ~/.grok/sessions/. OpenCode uses ~/.local/share/opencode/opencode.db (zero-dependency SQLite reader). Pi uses its default or environment-configured session root, global ~/.pi/agent/settings.json, and the scoped project's .pi/settings.json; relative sessionDir values resolve from the settings file directory. Project-local Pi settings require project-scoped lookup through the current cwd or --cwd. ZCode uses ~/.zcode/cli/db/db.sqlite.

Nothing in mem is uploaded. All reads are local.

When to reach for it

The bar is "would a senior teammate ask 'didn't we already talk about this?'" — those are the moments. Some concrete patterns: