From gingko
Use to search past Gingko memories before starting work, when the user says "what did we decide", "have we seen this", "look this up", "did we already", "again", "still", "back to", or when about to make an architectural call in a Gingko-enabled project (SessionStart prints "[gingko] primed session context"). Use any time prior sessions may already contain the answer.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gingko:gingko-recallThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gingko persists past sessions as a graph of semantic and episodic memories. Searching it is cheap; rediscovering things is not.
Gingko persists past sessions as a graph of semantic and episodic memories. Searching it is cheap; rediscovering things is not.
The gingko CLI auto-resolves project_id from the git remote.
gingko memory recall "<query>" # semantic search, natural language
gingko memory get-node <node_id> # drill into one memory + neighbors
gingko memory latest-memories-md 20 # skim recent learnings (markdown)
gingko memory latest-memories 30 # same, JSON
gingko memory session-primer # re-fetch the composed primer
gingko memory project-id # current project id
gingko memory status # exit 0 if service reachable
For structured results without shell escaping, the MCP equivalents are mcp__plugin_gingko_gingko__recall, get_node, latest_memories, get_session_primer.
Recall is semantic, not literal. Phrasing matters.
| Weak | Strong |
|---|---|
| "auth" | "auth middleware token refresh 401" |
| "the bug" | "Gingko.Memory.start_session rejects nil agent" |
| "tests" | "ExUnit test using Application.put_env" |
If the first query returns nothing useful, retry with a different anchor: file path, function name, error string, library name, or user-facing symptom phrasing. Empty recall ≠ "no prior work" — it can mean low semantic similarity for the words you chose. Try three different angles before concluding nothing relevant is recorded.
Each recall result has a node_id and a node_type (semantic or episodic). To reconstruct the why behind a decision, fetch the node and follow its graph neighbors:
gingko memory get-node node_abc123
Neighbors link related observations, the action that came from them, and the cluster they belong to. Traverse a step or two before concluding you've seen the full picture.
If you've re-entered a project and the primer wasn't loaded, or the conversation has drifted, skim recent learnings or refetch the primer:
gingko memory latest-memories-md 30
gingko memory session-primer
The primer composes: recall playbook, charter (if set), project summary, cluster index, recent memory tail.
gingko: command not found — bootstrap didn't wire PATH. Run export PATH="$HOME/.gingko/bin:$PATH" for this shell.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub edlontech/edlon-agents-marketplace --plugin gingko