Menu
Use when setting up, checking, or connecting Cognee through the cognee CLI from Codex.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/topoteretes/cognee-integrations --skill setupThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Search Cognee memory. Session memory is automatically searched on every prompt via hooks. Use this skill explicitly for permanent knowledge graph search, filtered category search, or when you need more results than the automatic lookup provides.
Use when Codex should remember, recall, search, improve, or forget information using Cognee.
Switch this session to another Cognee dataset. Lists the datasets you can write to, lets you pick one, syncs the current session into its dataset, then starts a fresh Cognee session bound to the chosen dataset. All later saves and recalls target the new dataset and the status line shows it.
Based on SOC occupation classification
Showing SKILL.md
| name | setup |
| description | Use when setting up, checking, or connecting Cognee through the cognee CLI from Codex. |
Use this skill when the user asks to configure Cognee, check whether Cognee is ready, connect to a local or cloud Cognee instance, or inspect CLI capability.
uv run cognee-cli ... as the primary interface..env, config files, shell history, or command output.Start with the local command surface:
uv run cognee-cli --help
uv run cognee-cli --version
If dependencies are missing, use the repository command:
uv sync --dev --all-extras --reinstall
Inspect configuration without exposing values:
uv run cognee-cli config list
Use config get <KEY> only for non-secret settings. For secret-like keys,
report whether the key appears configured rather than showing the value.
For a local backend:
uv run cognee-cli serve --url http://localhost:8000
For a hosted instance with an API key, do not paste the key into the transcript. Use an environment variable or an already configured credential.
For the plugin itself, durable configuration (COGNEE_BASE_URL,
COGNEE_API_KEY, LLM_API_KEY, ...) belongs in ~/.cognee/.env — a one-time
setup file shared with the Claude Code plugin, loaded at session start. Shell
exports still override it per terminal. Guide the user to edit that file
rather than exporting in every shell; never echo its secret values.
The file may hold both modes' variables at once: with nothing exported, cloud
wins (COGNEE_BASE_URL routes the connection). To pin one terminal to a mode,
the user exports COGNEE_BACKEND=local or COGNEE_BACKEND=cloud before
launching — that beats the URL rule, and unset COGNEE_BASE_URL is NOT a way
to go local (the file re-injects the URL on the next launch).
To disconnect:
uv run cognee-cli serve --logout
When the user wants concurrent or multi-agent use, prefer a running Cognee API server and pass:
uv run cognee-cli --api-url http://localhost:8000 <command>
For isolated session history and permissions, include:
uv run cognee-cli --user-id <uuid> <command>