← Plugin catalog
Productivity

Company Knowledge

OpenAI v0.1.7

Find decisions, documents, and project context across connected sources

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Interactive
  • Read

Not specified in the available declarations: limitations, pricing & account requirements.

Onboarding example

Summarize the latest updates on this project across messages, docs, and code
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 19, 2026.

Description

From the marketplace listing

Company Knowledge helps you find decisions, documents, owners, and recent project updates across your company's connected sources. Ask a question and get a concise answer with citations so you can review where the information came from. Use it to catch up on a project, find the right document, understand why a decision was made, or identify who owns the next step. Depending on your workspace setup, sources can include Slack, Microsoft Teams, Google Drive, SharePoint, Notion, GitHub, Linear, email, calendars, and meeting notes.

Language: English · Automatically detected from descriptions.

What changed

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin packageNo download link
company-knowledgeNo download link
Skill instructions
company-knowledge21 KB

View saved version →

---
name: company-knowledge
description: "Search company knowledge across connected workplace tools with direct connector fanout, evidence merging, and inline citations. Use for source-backed questions about internal projects, status, decisions, owners, docs, chat, GitHub, code, email, or meetings."
---

# Company Knowledge

Company Knowledge makes connected workplace sources feel like one citeable knowledge surface:

1. decide which connected sources are useful,
2. fan out bounded first-pass searches directly through connector tools,
3. merge and deduplicate evidence in the model,
4. answer with inline citations and source coverage.

Treat `@Company Knowledge`, `$company-knowledge`, or an explicit request to search company knowledge as routing the turn to this plugin.

This workflow deliberately avoids a custom MCP planner or merge server. Use direct connector fanout for the first pass. Use subagents only for a later deep-dive after the first merged evidence pack exposes a specific gap.

## Source Preflight

Before searching, identify the source lanes that are available in the current session. Use the plugin-associated apps and any already loaded connector tools as the source of truth. Do not claim that an unavailable connector was searched. If a likely source lane is not already callable, use `tool_search` to discover and load that connector family before marking it unavailable. Treat "only a profile/user lookup is available" as insufficient for Slack, Teams, Gmail, or calendar evidence; message/thread/document search must be available before the lane can satisfy source-backed questions.

The plugin declares these optional source families:

- Slack and Teams for recent discussion, informal decisions, feedback, and ownership signals.
- Google Drive, SharePoint, and Notion for canonical docs, plans, runbooks, policies, and wiki pages.
- GitHub and Linear for implementation state, issues, pull requests, milestones, and code ownership.
- Gmail, Outlook Email, Google Calendar, Outlook Calendar, and ChatGPT Meetings for email threads, meeting context, attendees, pre-reads, and formal follow-up.

Build a complete connector inventory before selecting search lanes. Include all plugin-associated apps, all already exposed connector tool families, and any additional connected apps returned by a host-level connector inventory. Treat the declared families above as an expected set, not an allowlist. Classify each connector internally as:

- `searchable_connected`: connected and exposes content search or read tools;
- `connected_insufficient`: connected, but exposes only profile lookup or other tools that cannot retrieve evidence for the question;
- `unavailable`: not connected, not loaded after discovery, or errored.

Do not stop inventory after finding the first useful connectors. Declared does not mean connected, and connected does not mean searchable. If the host exposes no global connected-app inventory, exhaustive coverage is limited to the connectors visible to the plugin; disclose that limitation when the user asks for all connected sources.

If a high-value connector is unavailable, continue with the connected sources, but do not stop at a weak adjacent lane. Try the next most authoritative lane for the task first, and mention the missing lane only when it materially affects confidence.

## Authoritative Code Lane

For code, file, API, stack trace, diff, CLI, migration, schema, dependency, or "where in the codebase" questions, GitHub/code evidence is the authoritative lane. In Codex environments, the local workspace and git checkout count as this lane and should usually be faster and more reliable than connector search.

Use the local code lane before docs/wiki-only search when it is available:

- Start with `rg --files`, `rg`, or `git grep` for exact paths, symbols, commands, errors, package names, PR numbers, and likely aliases.
- For history or diff questions, search git history with exact terms using `git log --all --grep`, `gi

Preview of the first 4,000 characters. Read full instructions →

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 19, 2026 · 06:00 UTC
Collection status
Collected

Plugin_b0672f102c2081919b893649fdcfeeaa

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.