/
stakeholders
Cursor Command
Identify stakeholders who should be consulted or informed about a change, project, or decision
Official Glean plugin for Cursor — search documents, Slack, and email; explore code across repos; and find experts and stakeholders.
Commands10
code-ownersIdentify who owns or maintains a specific code area, service, or component
codebase-contextGet architectural context about an internal system from code repositories and documentation
find-examplesFind usage examples of an API, library, or code pattern across internal repositories
find-expertFind subject matter experts for a topic based on actual activity and contributions, not just org chart position
mcp-setupConfigure a Glean MCP server connection for Cursor
Subagents4
codebase-navigatorNavigates internal code repositories to find implementations, understand patterns, and trace dependencies across systems via Glean code search
enterprise-searcherSearches enterprise knowledge across documents, Slack, email, and other sources to find relevant information on a topic
people-finderFinds people by role, expertise, activity, or organizational relationship using employee search and activity signals
plan-prep-researcherResearch enterprise context and similar patterns for planning tasks
Skills17
code-explorationSearch internal code repositories to find implementations, patterns, and contributors across the organization. Use when asked how something is implemented in other repos, where the code for a system lives, or who has been actively working on a codebase.
code-ownersIdentify who owns, maintains, or has expertise in a specific code area or component. Use when asked who to talk to about a system, who to request a code review from, or who has been actively working in a codebase area.
codebase-contextGather architectural context about an internal system from code and documentation across the organization. Use when asked to understand a system's architecture, find its repos, or get an overview before working on it.
confidence-signalsAssess and communicate the reliability, freshness, and authority of Glean search results before presenting them. Use when presenting Glean results that may be stale, come from informal sources, or where the user should verify before acting on them.
enterprise-searchSearch company documents, wikis, policies, design docs, and internal knowledge via Glean. Use when asked about company policies, internal specs, design docs, RFCs, or any information that lives in enterprise systems rather than the local codebase.