navan-incident-runbook
Use when responding to Navan platform incidents \u2014 flight cancellations,\ \ booking API failures, expense sync outages, or OAuth authentication errors.\n\ Trigger with \"navan incident runbook\" or \"navan outage response\".\n"
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill navan-incident-runbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Navan Incident Runbook ## Overview Structured incident response for Navan travel platform disruptions. Navan uses raw REST APIs with OAuth 2.0 — there is no SDK and no sandbox. All diagnostic commands run against production. ## Prerequisites - Access to Navan admin console (Admin > Travel admin) - OAuth credentials (`client_id`, `client_secret`) stored in your secret manager - Familiarity with N
What does the navan-incident-runbook skill do?
Use when responding to Navan platform incidents \u2014 flight cancellations,\ \ booking API failures, expense sync outages, or OAuth authentication errors.\n\ Trigger with \"navan incident runbook\" or \"navan outage response\".\n"
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill navan-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,596 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.