Skip to content
mcp/skillhub

Agent Skill

Cognee Performance skill

cognee-performancetopoteretes/cognee.agents/skills/cognee-performance/SKILL.md

Use when cognee is slow, expensive, or hitting rate limits — speeding up or throttling ingestion (remember/cognify batching, chunk size, LLM and embedding rate limits, per-stage models), cutting read latency, estimating cost before ingesting, running work in the background, or planning how to scale a deployment.

33kApache-2.0

always on

70 tokname + description

once used

2,534 tokSKILL.md body

bundled files

0

repo stars

33kGitHub

Install the Cognee Performance skill

Skills CLI (Claude Code, Codex, Cursor and others)

npx skills add https://github.com/topoteretes/cognee --skill cognee-performance

Claude Code, by hand (all projects)

git clone --depth 1 https://github.com/topoteretes/cognee.git /tmp/cognee
mkdir -p ~/.claude/skills
cp -R /tmp/cognee/.agents/skills/cognee-performance ~/.claude/skills/cognee-performance

For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.

What it costs your context

Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.

WhenWhat loadsCost
Every sessionName and description70 tok
When the agent uses itThe SKILL.md instructions2,534 tok
Only if openedNo bundled files—

Until it is used, cognee-performance costs about 19× less than the median MCP server we measured (1,362 tokens on every turn). Installing all 23 skills from topoteretes/cognee would load 1,658 tokens of descriptions. Skills vs MCP study

Checks

Our checks found nothing to flag: it follows the Agent Skills specification's naming and size guidelines and doesn't pipe downloads into a shell.

Checked 2026-10-22 · method

What's inside

The headings of its SKILL.md. Read the full file on GitHub.

  • Tune cognee's performance
  • Use it
  • 1. Estimate before you ingest
  • 2. Ingestion knobs
  • 3. LLM throttling and models
  • 4. Embeddings
  • 5. Skip the LLM for extraction
  • 6. Read latency
  • 7. Several datasets at once
  • 8. Scaling a deployment
  • Pitfalls
  • How it works
  • Extending it

More skills from topoteretes/cognee

All skills in this repo
  1. cogneetopoteretes/cognee

    Use this skill whenever the user asks about Cognee, AI memory, persistent agent memory, self-improving agents, agents learning from feedback, 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", "find custom pydantic models", "isolate agentic behaviour", "add permission control to retrieval", "reduce context bloating".

    33k2750237 tok idle · 4,746 in use
  2. cognee-clitopoteretes/cognee

    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.

    33k42 tok idle · 2,209 in use
  3. cognee-communitytopoteretes/cognee

    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.

    33k106 tok idle · 1,055 in use
  4. cognee-custom-graph-modelstopoteretes/cognee

    Use when defining the shape of cognee's knowledge graph with graph_model= — writing DataPoint node classes, choosing identity and index fields so nodes merge and are searchable, declaring typed Edge fields and FromIdentity references, building a model from a JSON schema, or debugging duplicated nodes, missing edges, or InvalidReferenceTypeError.

    33k74 tok idle · 2,325 in use
  5. cognee-custom-pipelinestopoteretes/cognee

    Use when building your own cognee processing — writing custom tasks, chaining them into a pipeline with run_custom_pipeline or the lightweight run_pipeline (from cognee.pipelines import run_pipeline), storing custom DataPoints with add_data_points, running custom enrichment over the existing graph, checking pipeline run status, or debugging how data flows between tasks (batch_size, data_per_batch, ctx, Drop, enriches).

    33k88 tok idle · 2,423 in use
  6. cognee-dockertopoteretes/cognee

    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.

    33k60 tok idle · 915 in use
  7. cognee-forgettopoteretes/cognee

    Use when removing data from cognee memory with forget() in the SDK, HTTP API, or CLI — finding which dataset and document hold the content to delete (listing datasets and data items, reading raw content), choosing between deleting one document, a whole dataset, or only the graph/vector memory, and doing it safely.

    33k70 tok idle · 1,862 in use
  8. cognee-improve-sessionstopoteretes/cognee

    Use when working with cognee's session memory or improve() — storing conversation turns, agent traces and feedback with session_id, bridging sessions into the permanent graph, reading an ImproveResult, understanding why an improve stage was skipped, already_completed or lock_held, or tuning the IMPROVE_* settings.

    33k69 tok idle · 3,599 in use