Skip to content
FunCoding

Search

Search docs, Skills and MCP

company-brain-follow-up-agent

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.

数据库与数据32k.agents/skills/company-brain-follow-up-agent/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/topoteretes/cognee/company-brain-follow-up-agent/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Company brain: agent for follow-up

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.

Steps

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.

  1. Run uv run python examples/cookbooks/company_brain/follow_up_agent/follow_up_agent.py --check.
    • Exit 0: go to step 2. [setup] SKIPPED: lines name optional sources that won't be used; mention them to the user, but they don't block the run.
    • 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.
  2. Run 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.
  3. The steps are everything after the [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.
  4. If a script fails, 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.

Rules

  • Gmail access is read-only.
  • With Slack set up, a run posts to the user's real channel, and every run reads the user's real calls, issues and mailbox and uses LLM credits, so run it only when the user asked for it.
  • Don't print the contents of credentials.json, token.json or .env.
  • A sample run forgets the cookbook's dataset 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.
  • Don't pass --ui unless the user asked to browse the graph: it keeps running until Ctrl+C.

Clean up

uv run cognee-cli forget --dataset follow_up_agent

Similar Skills

xlsx
anthropics/skills180k

xlsx

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

Databases & data

deprecation-and-migration
addyosmani/agent-skills103k

deprecation-and-migration

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.

Databases & data

host-observer
thedotmack/claude-mem98k

host-observer

Use this when fulfilling claude-mem observer jobs on Grok Bot: reply only skip_summary or one full observation XML, never prose.

Databases & data

babysit
thedotmack/claude-mem98k

babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

Databases & data

mem-search
thedotmack/claude-mem98k

mem-search

Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

Databases & data

Agent Cost Report
thedotmack/claude-mem98k

Agent Cost Report

Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.

Databases & data