Stats
Actions
Tags
From glean-core
Finds employees, team members, org structure, and experts using Glean tools like employee_search for roles/teams and code_search for contributions. Applies skepticism tests for evidence, recency, and availability.
How this skill is triggered — by the user, by Claude, or both
Slash command
/glean-core:people-lookupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When users ask about people in the organization, use Glean's employee search and activity signals to find the right person.
When users ask about people in the organization, use Glean's employee search and activity signals to find the right person.
See the glean-tools-guide skill for Glean MCP tool naming conventions. Tools follow the pattern mcp__glean_[server-name]__[tool] where the server name is dynamic. Use whatever Glean server is available in your tool list.
Use this approach when users ask:
Not everyone who appears in search results is a good recommendation.
Expertise Evidence Test
Recency Test
Availability Test
Filter Out:
Quality over quantity: Better to recommend 2 right people than 10 weak matches.
| User Intent | Glean Tool |
|---|---|
| Find by name, role, team | employee_search |
| Find by code contributions | code_search |
| Find by document authorship | search with owner: filter |
| Complex expertise analysis | chat |
Never use regular search for people lookups. The employee_search tool is specifically designed for:
# Find by name
employee_search "John Smith"
# Find by team
employee_search "payments team"
# Find direct reports
employee_search "reportsto:\"Jane Doe\""
# Find by role type
employee_search "engineering managers"
# Find recent hires
employee_search "startafter:2024-01-01"
For "who actually knows about X" questions, combine signals:
employee_search "[topic]"code_search "[topic] owner:\"name\""search "[topic] RFC owner:\"name\""People with multiple signals are true experts. Single-signal matches should be noted with lower confidence.
Don't pad with weak recommendations:
No strong expertise matches found for [topic].
**What was checked:**
- Employee search: [results]
- Code contributions: [results]
- Doc authorship: [results]
**Suggestions:**
- Ask in [relevant channel]
- Check with [related team] leadership
For comprehensive expertise discovery, suggest:
/glean-people:find-expert <topic> - Multi-signal expertise analysis/glean-people:stakeholders <change> - Find who needs to be involved/glean-docs:onboarding <team> - Get to know a new teamnpx claudepluginhub gleanwork/claude-plugins --plugin glean-coreGuides selection of Glean MCP tools for enterprise search tasks including document, employee, meeting, email, code discovery, and activity lookup. Covers decision tree, query formatting, and best practices.
Activate for: workplace memory, person brief, team profile, organisation profile, add person, add project, add terminology, four-layer memory, communication style, stakeholder brief, post-meeting memory revision, who works on, team directory, revise workplace memory, organisation context. NOT for: basic memory CRUD (use official productivity plugin memory-management), cross-context search (use workplace-search).
Searches Confluence, Jira, and internal docs for company systems, terminology, processes, deployment, authentication, infrastructure, and technical concepts with parallel cited results.