Stats
Actions
Tags
From glean-dev-docs
Searches and fetches Glean developer docs via MCP tools for APIs, SDKs (Python/JS), MCP config, authentication, indexing, and integrations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/glean-dev-docs:dev-docs-guideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When users ask about developing with Glean, use the Glean Developer Docs MCP tools.
When users ask about developing with Glean, use the Glean Developer Docs MCP tools.
Tools follow the pattern: mcp__glean_dev_docs__[tool]
docs_search - Search across documentationdocs_fetch - Get full page contentIf tools unavailable, suggest running /glean-dev-docs:setup.
| Need | Tool | Example |
|---|---|---|
| Find relevant docs | docs_search | docs_search "API authentication" |
| Get implementation details | docs_fetch | docs_fetch "https://developers.glean.com/docs/api/auth" |
docs_search "user query terms"docs_fetch "[url]" for code examplesGood: "OAuth token refresh", "Python SDK search API"
Less effective: "authentication", "API", "how to use"
This skill is for public developer documentation:
For internal company data (Slack, email, internal docs), guide to glean-core plugins instead.
npx claudepluginhub gleanwork/claude-plugins --plugin glean-dev-docsIndexes documents into Glean custom datasources via Indexing API and searches using Client API. For building connectors, testing search quality, or learning patterns.
Manages Gemini CLI docs: scraping from llms.txt/sites, local storage, keyword/NL/tag search, index rebuild/maintenance, doc resolution via scripts.
Searches a gnosis-mcp knowledge base via keyword, hybrid semantic+keyword, category filter, or git commit history. Useful when you need to find docs or past work by concept or commit message.