Skip to content
cccskills
FreePublished on GitHub

cognee-how-it-works

Explain what the Cognee plugin captures, recalls, stores and sends, where its data and logs live, and how to inspect or turn off each behavior; check its local or cloud connection and settings.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Explain the installed plugin

Read ${CLAUDE_PLUGIN_ROOT}/README.md, especially “What this plugin runs, stores and sends”, “Automatic capture controls”, and “Logs and state”. Those shipped instructions describe this installed version. Run "${CLAUDE_PLUGIN_ROOT}/scripts/cognee-doctor.sh" --json when the user asks about their connection or settings. Do not expose keys or raw private memory in an answer.

Explain the paths relevant to the question:

  • Prompts, answers, and selected tool traces are captured by hooks, with credential redaction and sensitive-file exclusions. COGNEE_CAPTURE=false opts out.
  • Cloud calls go to COGNEE_BASE_URL using COGNEE_API_KEY; local mode uses a local server. Cloud credit status comes from the Cognee platform API.
  • Recall injects selected memory into Claude's context. The injection budget drops whole entries and the session ledger avoids repeating cloud memory until context is cleared or compacted.
  • Local logs and markers live in ~/.cognee-plugin/claude-code/. Server memory stays until explicitly deleted. cognee-report measures observed outcomes.
  • Cloud setup manages native auto-memory only when there is no explicit user choice; COGNEE_DISABLE_AUTO_MEMORY=false restores the plugin-owned setting.

Distinguish an accepted capture, a landed graph improve, and recalled context. Consult the installed README for background retries/cache behavior before claiming it is available. Explain limitations directly when telemetry cannot establish an outcome.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when indexing a code repository into Cognee's code graph or querying it (callers, impact analysis, paths, endpoints) from Antigravity.

The English summary is being prepared. Showing the original description.

topoteretes/cognee-integrations101Updated Oct 19, 2026

Use when indexing a code repository into Cognee's code graph or querying it (callers, impact analysis, paths, endpoints) from Codex.

The English summary is being prepared. Showing the original description.

topoteretes/cognee-integrations101Updated Oct 19, 2026

Explain a repository's architecture (modules, routes, storage, services), find risky hotspots, draw a Mermaid diagram of the code graph, or review how far a change reaches, from Cognee's code graph.

The English summary is being prepared. Showing the original description.

topoteretes/cognee-integrations101Updated Oct 19, 2026

Index a repository (local path or git URL) into Cognee's code graph and answer exact structural queries with no LLM calls: callers, dependencies, impact of changing a symbol, call paths, endpoints, re-index changes.

The English summary is being prepared. Showing the original description.

topoteretes/cognee-integrations101Updated Oct 19, 2026

A multi-day digest of the user's own coding-agent sessions — sessions per day and project, most-edited files, and every lesson Cognee distilled into the knowledge graph in that window. Use only when the user explicitly asks for a weekly digest, a retro, a recap or report of their recent sessions, or asks for the `cognee-digest` skill by name. Not for questions about code or the current task.

The English summary is being prepared. Showing the original description.

topoteretes/cognee-integrations101Updated Oct 19, 2026

A digest of a week or more of the user's own coding-agent sessions (default 7 days): sessions per day and project, most-edited files and the lessons Cognee learned, written up as shipped, decided and still open.

The English summary is being prepared. Showing the original description.

topoteretes/cognee-integrations101Updated Oct 19, 2026

See all skills by topoteretes

Report a problem with this skill