Agent skill · operations · jeremylongshore
glean-incident-runbook
Triage: Is search returning results? Check Glean status page.
Why this skill is useful
Provides specific diagnostic commands and incident response procedures for Glean enterprise search that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq installed locally. Requires glean account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Glean Incident Runbook Overview Incident response procedures for Glean enterprise search integration failures. Covers search degradation, connector sync failures, indexing backlogs, and permission sync drift. Glean aggregates knowledge across all company tools, so incidents impact employee productivity across the entire organization. When search breaks or returns stale results, teams lose access to critical institutional knowledge. Classify severity immediately and follow the matching playbook below. Severity Levels Level Definition Response Time Example ------- ----------- --------------- --------- P1 - Critical Search fully down or returning zero results 15 min All queries return empty, API 5xx errors P2 - High Connector sync failed, content going stale 30 min Google Drive connector last synced 24h ago P3 - Medium Indexing backlog or partial result degradation 2 hours New documents not appearing for 4+ hours P4 - Low Permission sync drift or single datasource issue 8 hours One user sees docs they shouldn't access Diagnostic Steps Incident Playbooks API Outage 1. Confirm outage with diagnostic curl above and check Glean status page 2. Verify your Glean instance URL resolves and TLS cert is valid 3. Test from multiple networks to rule out local DNS or firewall issues 4. Notify users that search is temporarily unavailable 5. Contact Glean support with instance name, timestamps, and error codes Authentication Failure 1. Verify API token is set: echo $GLEANAPITOKEN wc -c 2. Check token expiry — Glean tokens may have a TTL configured by your admin 3. Test with a minimal search request (see diagnostics above) 4. If 401: regenerate token in Glean admin console under API settings 5. If 403: verify token scopes include search and indexing permissions Data Sync Failure 1. Identify which connector failed via getdatasourceconfig for each source 2. Check connector credentials — OAuth tokens for Google/Slack/Confluence may have expired 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/glean-incident-runbook--f18953