Stats
Actions
Tags
From gingko
Use when Gingko memory misbehaves. Triggers on "gingko isn't working", "memory broken", "service unreachable", "no active session", "session-id is empty", "recall returns nothing", "gingko: command not found", "append-step failing", "wrong project id", "stale primer", or any user complaint about Gingko hooks/CLI/MCP failing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gingko:gingko-troubleshootingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
What to do when Gingko misbehaves. The lifecycle hooks (`SessionStart`, `SessionEnd`, `Stop`) are intentionally non-blocking — failure prints stderr but never halts the conversation.
What to do when Gingko misbehaves. The lifecycle hooks (SessionStart, SessionEnd, Stop) are intentionally non-blocking — failure prints stderr but never halts the conversation.
Symptom: gingko memory status exits nonzero, or every CLI subcommand prints [gingko] ... unreachable on stderr.
What to do: Don't block work on memory. The SessionStart bootstrap already tried and failed silently. Suggest these to the user:
gingko status # is the node running?
gingko service status # is the service unit healthy?
gingko service start # restart it
If the user previously ran gingko stop, the marker ~/.gingko/.service-stopped blocks auto-restart on session start — they must run gingko service start manually.
Symptom: gingko memory session-id prints empty. append-step is a silent no-op.
What to do: The SessionStart hook owns lifecycle. An empty session id means the hook failed or the service was down when it ran. Tell the user; do not call start-session yourself.
If the user wants to record something urgently, the escape hatch is mcp__plugin_gingko_gingko__start_session — flag it first.
Symptom: gingko memory recall "<query>" returns an empty list.
What to do: Do not infer "no prior work exists." Try a different anchor:
If three different queries return nothing, then conclude nothing relevant is recorded.
Symptom: gingko: command not found.
What to do: The bootstrap should have wired ~/.gingko/bin into shell PATH. For this shell, source it explicitly:
export PATH="$HOME/.gingko/bin:$PATH"
To force PATH re-wire on the next session start:
rm ~/.gingko/.path-installed
Symptom: Shell complains about unmatched quotes, or the recorded text is truncated mid-content.
What to do: Use single quotes for the body. Escape internal single quotes with '\''. If both quote styles are needed, fall back to the structured MCP tool:
mcp__plugin_gingko_gingko__append_step
session_id: "<from `gingko memory session-id`>"
observation: "<text with any quotes>"
action: "<text with any quotes>"
Symptom: session-primer returns content for a different project, or project-id doesn't match the expected git remote.
What to do: Project ID is derived from the origin remote URL. If the repo has multiple remotes or was recently re-pointed:
git remote -v
gingko memory project-id
Point origin at the correct remote, or use mcp__plugin_gingko_gingko__list_projects to see what's been indexed.
Symptom: Service install or PATH wire didn't run on session start despite expecting it to.
What to do: Markers under ~/.gingko/ gate one-time setup. Delete the relevant one to force re-run on the next session:
rm ~/.gingko/.install-version # re-run binary install
rm ~/.gingko/.path-installed # re-run PATH setup
rm ~/.gingko/.service-stopped # allow auto-start again
After any fix, confirm:
gingko memory status # exit 0 = reachable
gingko memory session-id # non-empty = session active
gingko memory project-id # matches expected git remote
npx claudepluginhub edlontech/edlon-agents-marketplace --plugin gingkoCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.