Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/glean-incident-runbook
Triage: Is search returning results? Check Glean status page. Trigger: "glean incident runbook", "incident-runbook".
Passed 19 of 22 test cases with the skill, and 6 of 22 without it.
and 19 more in the full report
13 fixed6 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Provide the exact cURL command syntax to fetch Glean indexing queue statistics using the official indexing status endpoint.
| Checked | Without skill | With skill |
|---|---|---|
| Queries endpoint https://your-domain.glean.com/api/index/v1/getstatus | Missed | Passed |
| Pipes cURL output to jq '.statistics' | Missed | Passed |
The instructions your model reads when the skill loads.
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.
| 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 |
# Test search API health
curl -s -o /dev/null -w "HTTP %{http_code}\n" \
-H "Authorization: Bearer $GLEAN_API_TOKEN" \
-H "Content-Type: application/json" \
-X POST https://your-domain.glean.com/api/v1/search \
-d '{"query": "test", "pageSize": 1}'
# Check datasource connector status
curl -s -H "Authorization: Bearer $GLEAN_API_TOKEN" \
https://your-domain.glean.com/api/v1/getdatasourceconfig \
-d '{"datasource": "DATASOURCE_NAME"}' | jq '.status'
# Verify indexing queue depth
curl -s -H "Authorization: Bearer $GLEAN_API_TOKEN" \
https://your-domain.glean.com/api/index/v1/getstatus | jq '.statistics'
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.