topoteretes
- 30 skills
- 0 followers
- 105 repo stars
- last month last updated
- ▌ Local UI 2 · topoteretesUse when launching, checking, or reporting on the local Cognee UI/backend through cognee-cli -ui.
- ▌ Setup 2 · topoteretesUse when setting up, checking, or connecting Cognee through the cognee CLI from Codex.
- ▌ Memory 2 · topoteretesUse when Codex should remember, recall, search, improve, or forget information using Cognee.
- ▌ Cognee Sync 2 · topoteretesSync session cache entries into the permanent Cognee knowledge graph. Run this to make session memory searchable, or it runs automatically at session end.
- ▌ Codebase 2 · topoteretesUse when indexing a code repository into Cognee's code graph or querying it (callers, impact analysis, paths, endpoints) from Codex.
- ▌ Cognee Search 2 · topoteretesSearch 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.
- ▌ Cognee Remember 2 · topoteretesStore data permanently in the Cognee knowledge graph. Accepts a data category (user, project, or agent) to tag the data with the correct node_set for filtered retrieval.
- ▌ Cognee Forget 2 · topoteretesForget data stored in Cognee memory. Use when the user asks to forget, delete, or remove something from memory (e.g. "forget what we talked about tennis", "delete that from memory"). Finds the documents in the current dataset whose raw content matches what the user wants forgotten and deletes them.
- ▌ Cognee Switch Datasets 2 · topoteretesUse when the user wants to switch this Codex session to another Cognee dataset, see which datasets are available, or move memory capture to a different dataset. Syncs the current session first, then starts a fresh Cognee session bound to the chosen dataset.
- ▌ Cognee Falkor Setup · topoteretesUse when an agent must stand up the OpenClaw↔Cognee integration with FalkorDB as the vector + graph store. This skill is SELF-CONTAINED — it tells you to generate every file (Dockerfile, sitecustomize.py, docker-compose.yaml) from the exact contents below, build a custom Cognee image that loads the FalkorDB adapter, run Cognee + FalkorDB together, self-verify the adapter registered, and point the OpenClaw cognee plugin at it (including per-agent graphs). No other files in this directory are required.
- ▌ Setup · topoteretesUse when setting up, checking, or connecting Cognee through the cognee CLI from Antigravity.
- ▌ Memory · topoteretesUse when Antigravity should remember, recall, search, improve, or forget information using Cognee.
- ▌ Codebase · topoteretesUse when indexing a code repository into Cognee's code graph or querying it (callers, impact analysis, paths, endpoints) from Antigravity.
- ▌ Local UI · topoteretesUse when launching, checking, or reporting on the local Cognee UI/backend through cognee-cli -ui.
- ▌ Cognee Memory · topoteretes bundleAI knowledge engine - a memory system in 6 lines of code. remember/recall/forget/improve loop, vector + graph search, OpenClaw plugin supported.
- ▌ Cognee Code · topoteretesIndex a code repository into Cognee's code graph and query it deterministically (callers, impact analysis, paths, endpoints). Use for structural code questions, "index this repo", and checking what a re-index changed.
- ▌ Cognee Sync · topoteretesSync session cache entries into the permanent Cognee knowledge graph. Run this to make session memory searchable, or it runs automatically at session end.
- ▌ Cognee Forget · topoteretesForget data stored in Cognee memory. Use when the user asks to forget, delete, or remove something from memory (e.g. "forget what we talked about tennis", "delete that from memory"). Finds the documents in the current dataset whose raw content matches what the user wants forgotten and deletes them.
- ▌ Cognee Search · topoteretesSearch 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.
- ▌ Cognee Remember · topoteretesStore data permanently in the Cognee knowledge graph. Accepts a data category (user, project, or agent) to tag the data with the correct node_set for filtered retrieval.
- ▌ Cognee Switch Datasets · topoteretesSwitch 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.
- ▌
- ▌ Cognee · topoteretes bundleUse this skill whenever the user asks about Cognee, AI memory, persistent agent memory, self-improving agents, agents learning from feednack, knowledge graphs, graph-based RAG, long-term memory for agents, short-term memory for agents, personalization, personas, temporal search, temporal knowledge graphs, ontology-based extraction, ontology grounding, feedback, Cypher search, natural-language graph search, chunk search, RAG search, cross-session memory, session feedback, feedback loops, session based memory, redis based memory, knowledge promotion. Also use when the user describes the workflow such as: "turn documents into a knowledge graph", "build memory from files", "search my graph", "extract entities and relations", "sync data into a graph", "update graph memory", "store memories for an agent", "help my agent learn over time", "visualize a knowledge graph built from documents", "let the agent learn", "adaptive agents", "personalized agents", "session based personalization", "find important ontologies", "
- ▌ Cognee Integrations · topoteretesUse 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 Permissions · topoteretesUse 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 Community · topoteretesUse 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 Install · topoteretesUse 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 Docker · topoteretesUse 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 Server · topoteretesUse 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.
- ▌ Cognee CLI · topoteretesUse 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.