Setup

Skill jerlifish/slimecontext/skills/setup

Configure slimecontext — show the current setup if one exists, choose the notes-root directory, initialize it, and optionally register the notes location in the global CLAUDE.md. Invoked with /slime:setup.From its SKILL.md

Install

npx -y skills add jerlifish/slimecontext --skill setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.0 KB, as published. Nobody here has run it

slime:setup

Set up slimecontext for this user, or show them what they already have. Read ${CLAUDE_PLUGIN_ROOT}/references/format.md first — it defines every file this skill creates.

1. Show current setup (if any)

Check ~/.claude/slime.json (e.g. cat ~/.claude/slime.json).

If it exists and its root directory exists, this user is already set up. Read <root>/.slimecontext and show a compact summary:

notes root path
projects (names + note counts from nodes)
how many recent sessions, and the 3 most recent (topic · date)
whether the global CLAUDE.md line is present (grep -i slimecontext ~/.claude/CLAUDE.md)

Then use AskUserQuestion: keep as is (recommended), re-point to a different root, or — only if the CLAUDE.md line is missing — add the global CLAUDE.md line (see step 3). If they keep as is, jump to the tips (step 4) and finish.

If the pointer exists but its root directory is gone (moved/unsynced drive), say so plainly and treat this as a fresh setup — but ask before overwriting the pointer.

2. Choose and initialize the notes root

Ask where notes should live. Before asking, look for likely cloud-synced folders so you can offer real paths, e.g.:

ls -d ~/Google\ Drive* ~/Library/CloudStorage/GoogleDrive-* ~/Dropbox ~/OneDrive 2>/dev/null

AskUserQuestion with concrete options: a synced-folder path if one was found (e.g. <drive>/slimecontext — recommended, see tips for why), a plain ~/slimecontext, and the user can always type their own via "Other".

Then:

mkdir -p the chosen root.
If <root>/.slimecontext already exists (they pointed at an existing notes root — e.g. same Drive folder from another machine), keep it untouched and say you're reusing it.
Otherwise write a skeleton <root>/.slimecontext:

{
  "version": 1,
  "updated": "<now, ISO 8601>",
  "projects": {},
  "recent_sessions": [],
  "nodes": {}
}

Write ~/.claude/slime.json (create ~/.claude/ if needed):

{ "root": "<absolute root path>" }

3. Offer the global CLAUDE.md line

Ask (AskUserQuestion) whether to add ONE line to ~/.claude/CLAUDE.md. Explain the benefit in a sentence: every future Claude session — even without invoking slime — will know the notes exist and can pull matching context by tag, like a lightweight RAG layer.

If yes, and grep -i slimecontext ~/.claude/CLAUDE.md finds nothing (keep this idempotent — never add a second copy), append exactly one line:

Project context notes (slimecontext) live at <root> — check <root>/.slimecontext for a tag index of condensed per-project notes; when the current repo matches a project there, load its relevant context.md files for background, and suggest /slime:bootstrap to resume or /slime:save to record progress.

Substitute <root> with the absolute root path (it appears twice). Create ~/.claude/CLAUDE.md if it doesn't exist. If they decline, respect it and mention they can re-run /slime:setup to add it later.

4. Show tips

Finish with a short tips block:

Keep notes out of the repo. Point the root at a Google-Drive-synced (or Dropbox/OneDrive) folder instead of inside a git repo — notes accumulate forever and will bloat a repo, and a synced folder gives you cross-machine access and versioning for free.
The loop: start a session → /slime:bootstrap to resume with the right context → work → /slime:save to fold decisions, direction, and next steps back into the notes.
Notes stay lean on their own — save applies a detail curve when notes get long, and /slime:tidy compresses a whole project on demand. /slime:status shows what's saved at any time.
You'll get a nudge to save before Claude compacts a long conversation.