[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CY9XS5AP54FH7BS06ADC2Z":3,"skill-same:01M7CY9XS5AP54FH7BS06ADC2Z":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CY9XS5AP54FH7BS06ADC2Z","cognee-docker",null,"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.","GG-QandV\u002Fclone_cognee","GG-QandV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F220055168?v=4","01M7CY9H49G02Z6F9P4PYKFXRM","Yevhenii N","01M7CY9H5AR4XHN42K520M67C4",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FGG-QandV\u002Fclone_cognee\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcognee-docker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cognee-docker\ndescription: 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.\n---\n\n# Start cognee from the Docker image\n\n## Fastest path: prebuilt image, one file\n\nFor a local try-out, do NOT clone or build anything. Follow\n`docs\u002Fminimal-docker-compose.md`: save this as `docker-compose.yml` in an\nempty directory:\n\n```yaml\nservices:\n  cognee:\n    image: cognee\u002Fcognee:main\n    ports:\n      - \"8000:8000\"\n    environment:\n      LLM_API_KEY: ${LLM_API_KEY:?set LLM_API_KEY to your OpenAI API key}\n      # Single-user try-out: no auth, shared local databases.\n      ENABLE_BACKEND_ACCESS_CONTROL: \"false\"\n```\n\nThen:\n\n```bash\nexport LLM_API_KEY=\"sk-...\"   # OpenAI key (default LLM + embedding provider)\ndocker compose up\ncurl http:\u002F\u002Flocalhost:8000\u002Fhealth\n```\n\nInteractive API reference: http:\u002F\u002Flocalhost:8000\u002Fdocs. First requests:\n\n```bash\necho \"Cognee turns documents into AI memory.\" > note.txt\n# remember = ingest + build the graph in one call (multipart form)\ncurl -X POST http:\u002F\u002Flocalhost:8000\u002Fapi\u002Fv1\u002Fremember -F \"data=@note.txt\" -F \"datasetName=main_dataset\"\n# recall = query it (JSON)\ncurl -X POST http:\u002F\u002Flocalhost:8000\u002Fapi\u002Fv1\u002Frecall -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"What does Cognee do?\", \"datasets\": [\"main_dataset\"]}'\n```\n\n`\u002Fapi\u002Fv1\u002Frecall` takes the question as `query`. It defaults `search_type` to\n`GRAPH_COMPLETION` for backward compatibility — pass `\"search_type\": null` to\nopt into auto-routing (the SDK `recall()` default). The difference is real:\n`{\"query\": \"Why does X?\"}` answers with `GRAPH_COMPLETION`, while the same\nquery with `\"search_type\": null` routes to `GRAPH_COMPLETION_COT`.\n\nRequest DTOs accept both `snake_case` and `camelCase` for every field\n(`alias_generator=to_camel` + `populate_by_name` in `cognee\u002Fapi\u002FDTO.py`), so\n`search_type` and `searchType` are equally valid.\n\nThe legacy `\u002Fapi\u002Fv1\u002Fadd` + `\u002Fapi\u002Fv1\u002Fcognify` + `\u002Fapi\u002Fv1\u002Fsearch` endpoints still\nexist and are what `remember`\u002F`recall` call underneath; use them only when you\nneed a single stage on its own. `\u002Fapi\u002Fv1\u002Fimprove` and `\u002Fapi\u002Fv1\u002Fforget` complete\nthe memory API.\n\nData lives inside the container by default. To persist it, set\n`DATA_ROOT_DIRECTORY=\u002Fcognee-data\u002Fdata` and\n`SYSTEM_ROOT_DIRECTORY=\u002Fcognee-data\u002Fsystem` and mount a named volume at\n`\u002Fcognee-data` (full example in `docs\u002Fminimal-docker-compose.md`).\n\n## Full stack from the repo\n\nThe repository's `docker-compose.yml` builds from source and adds opt-in\nprofiles. From the repo root (needs a `.env` with at least `LLM_API_KEY`;\ncopy `.env.template`):\n\n```bash\ndocker compose up                                  # API server only, port 8000\ndocker compose --profile ui up                     # + frontend on port 3000\ndocker compose --profile mcp up                    # + MCP server on port 8001\ndocker compose --profile postgres --profile neo4j up   # + databases\n```\n\nPostgres profile: pgvector\u002Fpg17, user\u002Fpassword\u002Fdb `cognee`\u002F`cognee`\u002F`cognee_db`\non 5432. Neo4j profile: `neo4j`\u002F`pleaseletmein` on 7474\u002F7687. When cognee runs\nin a container and the database on the host, use `DB_HOST=host.docker.internal`.\n\n## Gotchas\n\n- With `ENABLE_BACKEND_ACCESS_CONTROL` unset (defaults to true), every API\n  call requires authentication — the single-user try-out sets it to `false`.\n- The image defaults to OpenAI for both LLM and embeddings; configuring only\n  one of them leaves the other on OpenAI, so keep a valid OpenAI key or\n  configure both (see the cognee-integrations skill).\n","# Start cognee from the Docker image\n\n## Fastest path: prebuilt image, one file\n\nFor a local try-out, do NOT clone or build anything. Follow\n`docs\u002Fminimal-docker-compose.md`: save this as `docker-compose.yml` in an\nempty directory:\n\n```yaml\nservices:\n  cognee:\n    image: cognee\u002Fcognee:main\n    ports:\n      - \"8000:8000\"\n    environment:\n      LLM_API_KEY: ${LLM_API_KEY:?set LLM_API_KEY to your OpenAI API key}\n      # Single-user try-out: no auth, shared local databases.\n      ENABLE_BACKEND_ACCESS_CONTROL: \"false\"\n```\n\nThen:\n\n```bash\nexport LLM_API_KEY=\"sk-...\"   # OpenAI key (default LLM + embedding provider)\ndocker compose up\ncurl http:\u002F\u002Flocalhost:8000\u002Fhealth\n```\n\nInteractive API reference: http:\u002F\u002Flocalhost:8000\u002Fdocs. First requests:\n\n```bash\necho \"Cognee turns documents into AI memory.\" > note.txt\n# remember = ingest + build the graph in one call (multipart form)\ncurl -X POST http:\u002F\u002Flocalhost:8000\u002Fapi\u002Fv1\u002Fremember -F \"data=@note.txt\" -F \"datasetName=main_dataset\"\n# recall = query it (JSON)\ncurl -X POST http:\u002F\u002Flocalhost:8000\u002Fapi\u002Fv1\u002Frecall -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"What does Cognee do?\", \"datasets\": [\"main_dataset\"]}'\n```\n\n`\u002Fapi\u002Fv1\u002Frecall` takes the question as `query`. It defaults `search_type` to\n`GRAPH_COMPLETION` for backward compatibility — pass `\"search_type\": null` to\nopt into auto-routing (the SDK `recall()` default). The difference is real:\n`{\"query\": \"Why does X?\"}` answers with `GRAPH_COMPLETION`, while the same\nquery with `\"search_type\": null` routes to `GRAPH_COMPLETION_COT`.\n\nRequest DTOs accept both `snake_case` and `camelCase` for every field\n(`alias_generator=to_camel` + `populate_by_name` in `cognee\u002Fapi\u002FDTO.py`), so\n`search_type` and `searchType` are equally valid.\n\nThe legacy `\u002Fapi\u002Fv1\u002Fadd` + `\u002Fapi\u002Fv1\u002Fcognify` + `\u002Fapi\u002Fv1\u002Fsearch` endpoints still\nexist and are what `remember`\u002F`recall` call underneath; use them only when you\nneed a single stage on its own. `\u002Fapi\u002Fv1\u002Fimprove` and `\u002Fapi\u002Fv1\u002Fforget` complete\nthe memory API.\n\nData lives inside the container by default. To persist it, set\n`DATA_ROOT_DIRECTORY=\u002Fcognee-data\u002Fdata` and\n`SYSTEM_ROOT_DIRECTORY=\u002Fcognee-data\u002Fsystem` and mount a named volume at\n`\u002Fcognee-data` (full example in `docs\u002Fminimal-docker-compose.md`).\n\n## Full stack from the repo\n\nThe repository's `docker-compose.yml` builds from source and adds opt-in\nprofiles. From the repo root (needs a `.env` with at least `LLM_API_KEY`;\ncopy `.env.template`):\n\n```bash\ndocker compose up                                  # API server only, port 8000\ndocker compose --profile ui up                     # + frontend on port 3000\ndocker compose --profile mcp up                    # + MCP server on port 8001\ndocker compose --profile postgres --profile neo4j up   # + databases\n```\n\nPostgres profile: pgvector\u002Fpg17, user\u002Fpassword\u002Fdb `cognee`\u002F`cognee`\u002F`cognee_db`\non 5432. Neo4j profile: `neo4j`\u002F`pleaseletmein` on 7474\u002F7687. When cognee runs\nin a container and the database on the host, use `DB_HOST=host.docker.internal`.\n\n## Gotchas\n\n- With `ENABLE_BACKEND_ACCESS_CONTROL` unset (defaults to true), every API\n  call requires authentication — the single-user try-out sets it to `false`.\n- The image defaults to OpenAI for both LLM and embeddings; configuring only\n  one of them leaves the other on OpenAI, so keep a valid OpenAI key or\n  configure both (see the cognee-integrations skill).\n",{"name":5,"description":7},"main","d3c91e153685d31a8df7acf5f8b28647a774ff33",".claude\u002Fskills\u002Fcognee-docker","https:\u002F\u002Fgithub.com\u002FGG-QandV\u002Fclone_cognee","https:\u002F\u002Fgithub.com\u002FGG-QandV","https:\u002F\u002Fkeysingate.com\u002F","2026-09-17 18:52:29",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GG-QandV\u002Fclone_cognee --skill cognee-docker",{"tool":37,"command":38},"bunx","bunx skills add GG-QandV\u002Fclone_cognee --skill cognee-docker",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GG-QandV\u002Fclone_cognee --skill cognee-docker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGG-QandV\u002Fclone_cognee\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcognee-docker\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7CYBGRTBNN40SCW8A70NPYC","skill-feedback-writer","Use to identify missing instructions in another skill based on its output.","https:\u002F\u002Fgithub.com\u002FGG-QandV\u002Fclone_cognee\u002Fblob\u002Fmain\u002Fexamples\u002Fdemos\u002Ffeedback\u002Fskill_feedback_loop\u002Fskills\u002Fskill-feedback-writer\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7CYBF54ZRAADPJAAZ27QM7D","pr-comment-evaluator","Use to judge whether a PR review comment sounds polite.","https:\u002F\u002Fgithub.com\u002FGG-QandV\u002Fclone_cognee\u002Fblob\u002Fmain\u002Fexamples\u002Fdemos\u002Ffeedback\u002Fskill_feedback_loop\u002Fskills\u002Fpr-comment-evaluator\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7CYBDRNDMBX4N85SHXXM6X3","diff-risk-explainer","Use to briefly explain small code diffs.","https:\u002F\u002Fgithub.com\u002FGG-QandV\u002Fclone_cognee\u002Fblob\u002Fmain\u002Fexamples\u002Fdemos\u002Ffeedback\u002Fskill_feedback_loop\u002Fskills\u002Fdiff-risk-explainer\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CYATY5MQ0WE9D9WZZ15FA2","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\".","https:\u002F\u002Fgithub.com\u002FGG-QandV\u002Fclone_cognee\u002Fblob\u002Fmain\u002Fcognee\u002Fskill.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CYANBAR44V6KV0Y3V9CXDB","cognee-server","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.","https:\u002F\u002Fgithub.com\u002FGG-QandV\u002Fclone_cognee\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcognee-server\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CYAEP5XHRND568JR5E9YSK","cognee-permissions","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\u002Fcognify\u002Fsearch\u002Fdelete, and how the grant records surface in the memory-provenance view.","https:\u002F\u002Fgithub.com\u002FGG-QandV\u002Fclone_cognee\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcognee-permissions\u002FSKILL.md",[],[]]