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.
日本語の概要は準備中です。原文の説明を表示しています。
topoteretes/cognee3.2万2026年10月10日 更新
無料GitHub で公開
personalized-email
Draft a reply to your newest Gmail email that knows what you discussed in your Granola meetings, what you promised the sender, and how you write, using cognee memory. Use when someone asks to answer or reply to their latest email in their own tone. Runs locally; reads Gmail read-only; the draft is printed, never sent.
含まれるファイル（1）
- SKILL.md2.7 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Personalized email
Runs the personalized email cookbook in examples/cookbooks/personalized_email/. It
remembers your Granola meeting notes and your Gmail inbox and sent mail in the cognee
dataset personalized_email, then drafts a reply to the newest inbox email. Setup, the
scripts and what each one does are in the cookbook's
README.md.
Run every command from the repo root.
Steps
With neither Gmail nor Granola set up, the commands below run on a sample mailbox (the
[setup] line says so) and draft a reply to a fictional email; only LLM_API_KEY is
needed. Tell the user the reply is to sample data. Add --sample to use the sample even
when their accounts are set up.
- Run
uv run python examples/cookbooks/personalized_email/personalized_email.py --check.- Exit 0: go to step 2.
- Exit 2: each
[setup] MISSING:line names one fix. Don't create credentials yourself. Tell the user exactly which line to fix, using the README's "What it needs" table, and stop. If only the Granola line is missing, ask whether to run with--no-granolainstead.
- Run
uv run python examples/cookbooks/personalized_email/personalized_email.py. Add--days Nif the user named a time range for meetings, and--no-granolaif they don't want Granola used. - The draft is everything after the line
[draft] Reply:. Give it to the user, and say which email it answers (the[draft] Answering:line) and which sources went in (the[ingest_granola]and[ingest_email]lines). The draft is never sent: hand it to the user to send. - If a script fails,
personalized_email.pyexits 1 with a line naming what went wrong. Run that script fromexamples/cookbooks/personalized_email/scripts/on its own to look closer.
Rules
- Gmail access is read-only and nothing is sent.
- Don't print the contents of
credentials.json,token.jsonor.env. - A sample run forgets the cookbook's dataset
personalized_emailbefore it ingests (the[clear]line). On the user's own data, pass--clearonly when they asked to start over: it forgets everything the dataset holds. - Ingesting reads the user's real meetings and mailbox, and every run uses LLM credits, so run it only when the user asked for it.
Clean up
uv run cognee-cli forget --dataset personalized_email
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
topoteretes/cognee3.2万2026年10月10日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
topoteretes/cognee3.2万2026年10月10日 更新
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 extraction/enrichment over the existing graph with memify, checking pipeline run status, or debugging how data flows between tasks (batch_size, data_per_batch, ctx, Drop, enriches).
日本語の概要は準備中です。原文の説明を表示しています。
topoteretes/cognee3.2万2026年10月10日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
topoteretes/cognee3.2万2026年10月10日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
topoteretes/cognee3.2万2026年10月10日 更新