Agent skill · software engineering · jeremylongshore
glean-local-dev-loop
Configure Glean local development with mock search responses, test datasources,
Why this skill is useful
Adds a local development setup for Glean API integration with mock responses and testing workflows that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. Requires glean account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Glean Local Dev Loop Overview Local development workflow for Glean enterprise search API integration. Provides a fast feedback loop with mock search results, connector testing, and document indexing simulation so you can build custom datasource connectors and search UIs without needing a live Glean deployment. Toggle between mock mode for rapid connector iteration and sandbox mode for validating against your Glean instance. Environment Setup Dev Server Mock Mode Testing Workflow Debug Tips Use curl -X POST http://localhost:3003/api/search -d '{"query":"test"}' to verify mock search Glean connectors must return documents with id, title, body.textContent, and datasource fields Check connector transform output shape before pushing to the indexing API Enable verbose logging on the Glean SDK client to trace API call timing Verify OAuth scopes if search returns empty results against a live instance Error Handling Issue Cause Fix ------- ------- ----- 401 Unauthorized Invalid API key or expired token Regenerate at Glean admin console 403 Forbidden Key lacks indexing scope Request Indexing API permissions from admin 400 Bad Request Malformed document payload Validate required fields: id, title, body 429 Rate Limited Too many indexing requests Batch documents (max 100 per request) ECONNREFUSED :3003 Dev server not running Run npm run dev:mock first Prerequisites A local mock or sandbox endpoint, a fictitious datasource, and no production token in environment files, shell history, or test output. A fixture reset command and two synthetic identities for access-boundary tests. A change record and rollback path for any configuration that might later be promoted. Instructions 1. Start in mock mode with bounded fixtures and validate transforms, rejection paths, and redaction before any network call. 2. Use a sandbox datasource with a scoped credential only after local tests pass; assign an idempotency key and verify both allow and deny cases. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/glean-local-dev-loop