- name
Turn your latest Granola call into next steps (owner, team, due date, and the Linear issue that already tracks each one) and post them to Slack, using cognee memory of your calls, Linear issues and Gm
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add topoteretes/cognee --skill company-brain-follow-up-agent -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add topoteretes/cognee --skill company-brain-follow-up-agent -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add topoteretes/cognee --skill company-brain-follow-up-agent -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add topoteretes/cognee --skill company-brain-follow-up-agent -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/topoteretes/cognee/tree/HEAD/.agents/skills/company-brain-follow-up-agentFrom the publisher
Runs the follow-up agent cookbook in examples/cookbooks/company_brain/follow_up_agent/.
It remembers your Granola calls, Linear issues and Gmail inbox in the cognee dataset
follow_up_agent, then works out the next steps of your latest call and posts them to
Slack, or prints them. Setup, the scripts and what each one does are in the cookbook's
README.md.
Run every command from the repo root.
With none of Granola, Linear and Gmail set up, the commands below run on sample calls,
issues and email (the [setup] line says so), follow up a fictional call and never post to
Slack; only LLM_API_KEY is needed. Tell the user the steps come from sample data. Add
--sample to use the sample even when their accounts are set up.
uv run python examples/cookbooks/company_brain/follow_up_agent/follow_up_agent.py --check.
[setup] SKIPPED: lines name optional sources that won't be
used; mention them to the user, but they don't block the run.[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.uv run python examples/cookbooks/company_brain/follow_up_agent/follow_up_agent.py.
Add --days N if the user named a time range, and --no-linear / --no-email if they
don't want a source used.[follow_up] Posted to Slack: or [follow_up] Steps
line. Give them to the user, say which call they come from (the [follow_up] Call:
line), which sources went in (the [ingest_*] lines), and whether they were posted.follow_up_agent.py exits 1 with a line naming what went wrong. Run
that script from examples/cookbooks/company_brain/follow_up_agent/scripts/ on its own
to look closer.credentials.json, token.json or .env.follow_up_agent before it ingests (the [clear]
line). On the user's own data, pass --clear only when they asked to start over: it
forgets everything the dataset holds.--ui unless the user asked to browse the graph: it keeps running until
Ctrl+C.uv run cognee-cli forget --dataset follow_up_agent
© 2026 Skills Rack.
---name: company-brain-follow-up-agentdescription: Turn your latest Granola call into next steps (owner, team, due date, and the Linear issue that already tracks…---# .agents/skills/company-brain-follow-up-agent/SKILL.mdOverview
Turn your latest Granola call into next steps (owner, team, due date, and the Linear issue that already tracks each one) and post them to Slack, using cognee memory of your calls, Linear issues and Gmail inbox. Use when someone asks for the next steps or action items of their latest call. Runs locally; reads Gmail read-only; posts to Slack only when Slack is set up.
FAQ
Download .agents/skills/company-brain-follow-up-agent/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/topoteretes/cognee.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.