Company Context
Use Centaur's indexed company context together with direct Slack, Linear, Google Docs, Drive, Calendar, or Granola searches when answering internal company-history, prior-decision, project-context, meeting-context, roadmap/status, or cross-source memory questions. Indexed context includes Slack channels, user-visible Slack DMs, Google Docs, Google Calendar, Linear, and user-visible Granola notes. Use for questions like what was discussed, decided, planned, mentioned, or documented internally, especially when the user did not name one exact source.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Company Context when an AI agent needs a reusable SKILL.md workflow for this job: Use Centaur's indexed company context together with direct Slack, Linear, Google Docs, Drive, Calendar, or Granola searches when answering internal company-history, prior-decision, project-context, meeting-context, roadmap/status, or cross-source memory questions. Indexed context includes Slack channels, user-visible Slack DMs, Google Docs, Google Calendar, Linear, and user-visible Granola notes. Use for questions like what was discussed, decided, planned, mentioned, or documented internally, especially when the user did not name one exact source.
When not to use it
Skip Company Context when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/company-context # Save SKILL.md to ~/.claude/skills/company-context/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/company-context/SKILL.md. For a shared project, commit the folder at .claude/skills/company-context/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Company Context skill for this task: Use Company Context when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Company Context
Use `company_context` as the first retrieval step for internal historical context. Its `search` command queries indexed company memory across enabled sources such as Slack channels, Google Docs (`--source docs`), Google Calendar, Linear, and user-visible Granola notes (`--source granola`). It also has dedicated commands for user-visible Slack DMs and DM conversations. Always pair indexed results with the relevant direct source tools, then reconcile and collate both evidence sets before answering.
## Default Workflow
1. Search company context first:
```bash company_context search "QUERY" --limit 10 --json ```
For DM-specific questions, use the dedicated DM search surface:
```bash company_context search-dms "QUERY" --limit 10 --json company_context search-dm-conversations "PERSON OR QUERY" --limit 10 --json ```
2. Read promising documents before answering:
```bash company_context read "DOCUMENT_ID" --max-chars 8000 --related --json ```
3. Check live/source tools for the same query and relevant source filters. Do this even when indexed results look strong:
```bash slack search "QUERY" linear search "QUERY" gsuite drive list --query "QUERY" gsuite calendar events --query "QUERY" ```
Use the source-specific tools that match the question. For broad cross-source questions, check all likely sources.
4. For time-sensitive or "latest" asks, check index freshness:
```bash company_context latest-date company_context latest-date --source slack company_context latest-date --source docs --source-type google_doc company_context latest-date --source linear ```
`latest-date` always outputs JSON, so it does not accept a `--json` flag.
5. If results are weak, broaden or target source filters:
```bash company_context search "QUERY" --source slack --limit 10 --json company_context search "QUERY" --source docs --source-type google_doc --limit 10 --json company_context search "QUERY" --source google_calendar --limit 10 --json company_context search "QUERY" --source linear --limit 10 --json company_context search "QUERY" --source granola --limit 10 --json company_context search-dms "QUERY" --limit 10 --json ```
6. Collate indexed and live results before answering:
- Prefer direct live-tool evidence for current state, exact source objects, and canonical fields. - Prefer indexed context for historical recall, older discussions, and cross-source semantic matches. - Treat disagreement as a signal to explain the mismatch, including dates and source links when available. - Avoid claiming completeness unless the direct source tool or owning API supports that claim.
## When To Fall Back
Use extra direct-tool depth after the default indexed-plus-live pass when:
- The user asks for the current Slack thread, a specific Slack channel/message/file, or a direct source object that `company_context` did not return. - The user asks to create, update, comment on, or inspect an exact Linear issue/project. - The user gives an exact Google Doc, Drive, Calendar, or Linear URL/id. - `company_context` returns an auth, permission, connection, or malformed-response error. - The question requires a canonical exhaustive answer. Company context is indexed retrieval; use the owning API/database for definitive inventories or yes/no internal-history claims when the user asks for completeness.
## Answering Rules
- Lead with the answer and include the evidence source when it matters: source, source type, date, title, and URL/permalink if present. - Say how indexed context and live source-tool results agree, differ, or complement each other. - If freshness matters, use `latest-date` to inspect the indexed cutoff and direct source tools for live corroboration. - Do not copy long private documents or message dumps into the reply. Summarize narrowly and quote only short snippets when useful. - If no indexed context is found after reasonable query variants, say that plainly and name the live tools checked.
Intended uses
- Use Company Context when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.