using-glean
Use Glean MCP tools to answer questions about company documents, internal wikis, policies, RFCs, design docs, people, teams, meetings, decisions, action items, email, calendar events, internal code, and the user's own work activity. Reach for this whenever the answer lives in enterprise systems rather than the local codebase or public web. Trigger phrases include "find the doc about", "what's our policy on", "where is the spec for", "who works on", "who owns", "find someone who knows", "what was decided in the meeting", "action items from", "search my email", "what did I work on last week", and "find the implementation in our repos". Don't use it for questions answerable from the local working directory, the public web, or generic programming knowledge.
Install
With your agent
Install OMGSkills skill "gleanwork/claude-plugins:plugins/glean/skills/using-glean" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/gleanwork/claude-plugins /tmp/claude-plugins && ln -s /tmp/claude-plugins/plugins/glean/skills/using-glean ~/.claude/skills/using-gleanFrom README
Using Glean The Glean MCP server exposes a family of tools that let the assistant query the user's company knowledge: documents, people, meetings, email, internal code, the user's activity feed, structured memory, and the knowledge graph. This skill is the entry point. It maps a user's question to the right tool, names the rules that apply across all of them, and links to per-tool reference files that carry the deep syntax. Where these tools live The tools listed below come from the user's Glean MCP server connection. Refer to them by their bare names (search, employeesearch, meetinglookup, …) — the assistant resolves them against the active tool inventory. In the raw MCP tool list, Glean tools appear as mcpglean[server-name][tool] where [server-name] is the user's configured server identifier (e.g., default, production, acme). The tool suffix after the final is always consistent across deployments. Use whatever Glean server is visible in your tool inventory.
More from this repo
catch-up
Catch up on what you missed while away — meetings, decisions, action items, mentions, and important threads from a...
code-owners
Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system,...
codebase-context
Gather architectural context about an internal system from code and documentation across the organization — use when...