Agent skill

glean-incident-runbook

Triage: Is search returning results? Check Glean status page. '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill glean-incident-runbook --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Version: 1.8.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(npm:*)Bash(curl:*)Grep
Requires: Designed for Claude Code
Path: skills/.curated/glean-incident-runbook/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 ```bash # Test search API health curl -s -o /dev/null -w "HTTP %{http_code}\n" \ -H "Auth

What's inside
Steps it walks through
  1. Overview
  2. Severity Levels
  3. Diagnostic Steps
  4. Incident Playbooks
  5. API Outage
  6. Authentication Failure
  7. Data Sync Failure
  8. Communication Template
  9. Post-Incident
  10. Error Handling
  11. Resources
  12. Next Steps
Commands it runs
Test search API health
curl -s -o /dev/null -w "HTTP %{http_code}\n" \
Check datasource connector status
curl -s -H "Authorization: Bearer $GLEAN_API_TOKEN" \
Verify indexing queue depth
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the glean-incident-runbook skill do?

Triage: Is search returning results? Check Glean status page. '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill glean-incident-runbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going