Use when the user asks about internal code, implementations, patterns across repositories, or needs to understand how something is built. Triggers on "how is X implemented", "where is the code for", "find the implementation of", "what repos contain", "who wrote the code for", or code architecture questions about internal systems.
Explores code across internal repositories to find implementations, patterns, and examples using organizational search.
npx claudepluginhub gleanwork/claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
When users need to understand code across internal repositories—beyond the local codebase—use Glean's code search to explore the entire organization's code.
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 Glean code search when users ask about:
Not every code result is worth presenting.
Quality Test
Recency Test
Relevance Test
Filter Out:
/deprecated/, /old/, /legacy/ pathsQuality over quantity: 3 good examples beat 10 mediocre ones.
Local tools (grep, glob) search only the current repo. Glean searches across ALL repositories in the organization. This is powerful for:
| User Intent | Glean Tool |
|---|---|
| Find code by content, pattern, or file | code_search |
| Find related design docs or specs | search |
| Identify code owners/contributors | code_search + employee_search |
| Read full file content | read_document |
Glean's code search understands natural language. Use filters for precision:
# Search by content
code_search "authentication middleware"
code_search "rate limiting implementation"
# Search by contributor
code_search "owner:\"John Smith\" billing service"
code_search "from:me updated:past_week"
# Search by time
code_search "after:2024-01-01 payments API"
# Search by file pattern
code_search "*.proto user service"
code_search "[system name]"search "[system name] design doc OR architecture"code_search "owner:* [system] updated:past_month"read_document with URLs from vetted resultsDon't pad with weak results:
No high-quality code examples found for [topic].
**What was searched:**
- [Queries attempted]
**What was filtered:**
- [X] matches - [reasons: outdated/poor quality]
**Suggestions:**
- Check external libraries
- Ask in [relevant channel]
- This may need to be built from scratch
For structured workflows, suggest the relevant slash command:
/glean-code:codebase-context [system] - Get comprehensive context/glean-code:find-examples [API/pattern] - Find usage examples/glean-code:code-owners [component] - Identify maintainers/glean-code:similar-code [pattern] - Find similar implementationsExpert 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.