curl -fsSL https://api.cheatcodehq.com/install.sh | sh -s -- cognee --to allCopies 7 skills into each app's skills folder (Claude Code: ~/.claude/skills), after checking every file against topoteretes/cognee at commit c4cd8ce. Nothing else on your computer changes. To undo it, run the terminal command with --uninstall at the end; that also removes what the app added.
Then start a new session in your AI app and ask for the work in plain words; it picks the skill from its description. In Claude Code you can also type /cognee:cognee-cli.
See it in use
After installing, start a new session and say: Use the cognee-install skill to check my script app.py and settings.env and tell me why recall returns nothing.
What else it can do, and its limits
- 7 skills for developers who use cognee: install and a first remember and recall, the cognee-cli commands, the API server, Docker and docker compose
- Switching the language model or embedding provider (OpenAI, Azure, Gemini, Anthropic, Ollama, OpenRouter) and the databases behind it
- How users, roles and tenants get access to datasets, and the community adapters and connectors outside cognee core
- Guidance only: running cognee needs Python, a terminal and a model API key; the skills do not install or run anything themselves
- Without a terminal, as in this run, fixes are read from the files and stay untested until someone runs them
Sample input Recorded Oct 24, 2026 in Claude Code 2.1.308 with Sonnet 5.5. The video replays that session; nothing in it was acted or edited.
What's inside 7 skills
cognee-cliUse when the user wants to drive cognee from the terminal with cognee-cli — remember/recall/forget/improve memory commands, managing datasets and config, or database migrations.
Use when the user wants to drive cognee from the terminal with cognee-cli — remember/recall/forget/improve memory commands, managing datasets and config, or database migrations.
cognee-communityUse when the user needs something that ships outside cognee core — community database adapters (Qdrant, Milvus, Weaviate, Redis, Pinecone, FalkorDB, Memgraph, DuckDB, NetworkX, …), data-source connectors (Slack, Gmail, Notion, Confluence, Google Drive), custom tasks/pipelines/retrievers (Exa, ScrapeGraph, codify), Keywords AI observability — or wants to contribute a package to the cognee-community repo.
Use when the user needs something that ships outside cognee core — community database adapters (Qdrant, Milvus, Weaviate, Redis, Pinecone, FalkorDB, Memgraph, DuckDB, NetworkX, …), data-source connectors (Slack, Gmail, Notion, Confluence, Google Drive), custom tasks/pipelines/retrievers (Exa, ScrapeGraph, codify), Keywords AI observability — or wants to contribute a package to the cognee-community repo.
cognee-dockerUse when the user wants to run cognee with Docker or docker compose — trying it out from the prebuilt image, starting the API server in a container, or bringing up the full stack (UI, MCP, Postgres, Neo4j) with compose profiles.
Use when the user wants to run cognee with Docker or docker compose — trying it out from the prebuilt image, starting the API server in a container, or bringing up the full stack (UI, MCP, Postgres, Neo4j) with compose profiles.
cognee-installUse when the user wants to install cognee and run their first remember → recall flow with the Python SDK — fresh setup, virtual env, extras selection, or a minimal working example.
Use when the user wants to install cognee and run their first remember → recall flow with the Python SDK — fresh setup, virtual env, extras selection, or a minimal working example.
cognee-integrationsUse when the user wants to connect cognee to external services — switching LLM or embedding providers (OpenAI, Azure, Gemini, Anthropic, Ollama, OpenRouter), changing databases (Postgres, PGVector, Neo4j, Neptune, Turso), S3 storage, or the MCP server for IDE integration.
Use when the user wants to connect cognee to external services — switching LLM or embedding providers (OpenAI, Azure, Gemini, Anthropic, Ollama, OpenRouter), changing databases (Postgres, PGVector, Neo4j, Neptune, Turso), S3 storage, or the MCP server for IDE integration.
cognee-permissionsUse when working with cognee's permission system — understanding or changing how users, roles, and tenants get access to datasets, how ACL grants work, where permissions are enforced in add/cognify/search/delete, and how the grant records surface in the memory-provenance view.
Use when working with cognee's permission system — understanding or changing how users, roles, and tenants get access to datasets, how ACL grants work, where permissions are enforced in add/cognify/search/delete, and how the grant records surface in the memory-provenance view.
cognee-serverUse when the user wants to run the cognee API server (and optional UI) on their own machine — starting it, checking it's healthy, connecting the SDK or other clients to it, and choosing the right auth posture.
Use when the user wants to run the cognee API server (and optional UI) on their own machine — starting it, checking it's healthy, connecting the SDK or other clients to it, and choosing the right auth posture.
About
Something wrong with this listing, or it did not install? Tell us