topoteretes/cognee / .agents/skills/company-brain-company-qa
company-brain-company-qa
VerifiedBuild one company memory from a SQL database, a support ticket export and a folder of documents, linked into one graph by cognee, then answer questions that need several of those sources together. Use when someone wants to connect their company's database, tickets and docs, or asks who owns, decided or is handling something across them. Runs locally; reads the sources, writes only to cognee's memory.
Company brain: company Q&A
Runs the company brain cookbook in examples/cookbooks/company_brain/company_qa/. It
remembers a SQL database, a ticket export and a docs folder in the cognee dataset
company_qa, extracts them with one graph model so the same person, team or project
becomes one node, then answers a question across them. Setup, the scripts and what each
one does are in the cookbook's
README.md.
Run every command from the repo root.
Steps
- Work out the sources. Ask the user for the ones they want: a database URL (and tables),
one or more ticket export files (JSON or CSV), a docs folder. If they have none, or
want to see it work first, pass no sources: the run then uses the sample company (the
[setup]line says so). Tell the user the answer comes from sample data. - Run
uv run python examples/cookbooks/company_brain/company_qa/company_qa.py --checkwith the sources (--database URL [--tables a,b] --tickets FILE [FILE ...] --docs FOLDER), or none for the sample.- Exit 0: go to step 3.
- Exit 2: each
[setup] MISSING:line names one fix. Don't create credentials yourself. Tell the user which line to fix, using the README's "What it needs" table, and stop.
- Run the same command without
--check, adding the user's question as--ask "...". On the sample with no--ask, it asks a question that needs all three sample sources. - The answer is everything after
[ask] A:. Give it to the user. The[ingest]lines say which sources went in. - Later questions don't need the sources again:
uv run python examples/cookbooks/company_brain/company_qa/scripts/ask.py "...". - If a script fails,
company_qa.pyexits 1 with a line naming what went wrong. Run that script fromexamples/cookbooks/company_brain/company_qa/scripts/on its own to look closer.
Rules
- The sources are the user's company data. Don't quote them beyond what answers the
question, and don't print
.envor a database URL's password. - Every run uses LLM credits, so ingest only when the user asked for it.
- A sample run forgets the cookbook's dataset
company_qabefore 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. - Don't pass
--uiunless the user asked to browse the graph: it keeps running until Ctrl+C.
Clean up
uv run cognee-cli forget --dataset company_qa
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |