Use when the user asks about company documents, internal wikis, policies, specifications, design docs, RFCs, or enterprise knowledge. Triggers on phrases like "find the doc about", "what's our policy on", "where is the spec for", "company guidelines", "internal documentation", or when searching for information that would be in enterprise systems rather than the local codebase.
Searches internal company documents and knowledge bases to find policies, specifications, and enterprise information.
npx claudepluginhub gleanwork/claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
When users ask about internal company information that lives in enterprise systems (not the local codebase), use Glean tools to find it.
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 Glean search when users ask about:
Not every search result is relevant or current. Before presenting results, evaluate:
Relevance Test
Freshness Test
Authority Test
Filter Out:
See confidence-signals skill for how to communicate reliability.
| User Intent | Glean Tool |
|---|---|
| Find documents, policies, specs | search |
| Complex analysis across sources | chat |
| Read full document content | read_document |
Glean understands natural language. Enhance queries with filters when helpful:
# Recent documents
"API documentation updated:past_week"
# By author
"design doc owner:\"Sarah Chen\""
# Date range
"quarterly planning after:2024-01-01"
# Specific app
"authentication RFC app:confluence"
search to find relevant documentsread_document with URLs from vetted resultschat for multi-source analysisWhen presenting information from Glean, always include:
confidence-signals skill)This allows users to assess reliability and explore further.
Don't pad with weak results:
No relevant results found for [query].
**What was searched:**
- [Search terms used]
**Suggestions:**
- Try alternative terms: [suggestions]
- Ask in [relevant channel]
- This may not be documented
For comprehensive, structured workflows, suggest the relevant slash command:
/glean-search:search <query> - Quick search with formatted results/glean-docs:verify-rfc - Compare spec to implementation/glean-meetings:catch-up - Systematic catch-up after time awayExpert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.