Agent skill

Navan Incident Runbook

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Manage containment, reconciliation, and recovery for a Navan integration incident.

MITAuto-check passedDevOps & Cloud

Install Navan Incident Runbook

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill navan-incident-runbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace navan-incident-runbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/navan-incident-runbook .claude/skills/navan-incident-runbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
navan-incident-runbook
GitHub stars
2.8k
Token cost
~917 tokens
SKILL.md length
366 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Manage containment, reconciliation, and recovery for a Navan integration incident.

  • Works in 6 steps: Declare commander, scope, severity,… → Contain schedules, writes, transfers,… → Preserve sanitized logs, checkpoints,… → …
  • Handling credential
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Navan Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Manage containment, reconciliation, and recovery for a Navan integration incident. Use when handling credential, privacy, booking, expense, identity, or delivery failures. Trigger with "Navan incident", "Navan outage", or "Navan data exposure".

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live or external Navan actions require network access and explicit approval

It sits in DevOps & Cloud, covering Runbooks and postmortems, Accounting and bookkeeping and Incident response. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Handling credential
  • Delivery failures
  • With Navan incident
  • Navan data exposure

Example prompts

  • “Navan incident”
  • “Navan outage”
  • “Navan data exposure”
  • “/navan-incident-runbook”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; live or external Navan actions require network access and explicit approval
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Declare commander, scope, severity, timeline, and communication boundary.
  2. Contain schedules, writes, transfers, credentials, or destinations without erasing evidence.
  3. Preserve sanitized logs, checkpoints, schemas, counts, hashes, and approvals.
  4. Determine source, destination, traveler, privacy, security, and finance impact.
  5. Reconcile the affected window before replay or reopening writes.
  6. Recover gradually, monitor, close temporary access, and assign follow-ups.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; live or external Navan actions require network access and explicit approval

    From compatibility in the SKILL.md frontmatter.

Context cost

Navan Incident Runbook loads about 917 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 366 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~917
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 366 words, ~917 tokens.

Download SKILL.mdSave it as .claude/skills/navan-incident-runbook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
navan-incident-runbook
description
Manage containment, reconciliation, and recovery for a Navan integration incident. Use when handling credential, privacy, booking, expense, identity, or delivery failures. Trigger with "Navan incident", "Navan outage", or "Navan data exposure".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Designed for Claude Code; live or external Navan actions require network access and explicit approval
argument-hint
<incident-id> <surface> <severity>
version
1.9.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, navan, incident
model
inherit
effort
high

Navan Integration Incident Command

Overview

Manage containment, reconciliation, and recovery for a Navan integration incident. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

  • Access to the selected tenant's current Navan Help Center and contracted integration documentation.
  • A named business owner and data owner for the travel or expense workflow.
  • A non-production evidence set with secrets and traveler data removed.

Current Contract

The source of truth spans Navan, the integration, and downstream systems. Recovery is incomplete until credentials, data windows, financial totals, traveler impact, and destination acknowledgements are reconciled.

Authentication

Use break-glass access only under the documented incident process. Never paste tokens or traveler data into chat, tickets, status updates, or unapproved AI tools.

Instructions

  1. Declare commander, scope, severity, timeline, and communication boundary.
  2. Contain schedules, writes, transfers, credentials, or destinations without erasing evidence.
  3. Preserve sanitized logs, checkpoints, schemas, counts, hashes, and approvals.
  4. Determine source, destination, traveler, privacy, security, and finance impact.
  5. Reconcile the affected window before replay or reopening writes.
  6. Recover gradually, monitor, close temporary access, and assign follow-ups.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Show full SKILL.md (139 more words)Show less

Approval Boundaries

Credential rotation, replay, backfill, write enablement, customer communication, legal notification, and evidence sharing require the authorized incident roles.

Error Handling

  • Containment comes before reproduction.
  • Do not replay an unknown-outcome write blindly.
  • Vendor status alone does not prove local recovery.

Output

Return incident state, timeline, affected windows, containment, exposure assessment, reconciliation, recovery gates, and owners. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

  • Rotate a suspected transfer key and reconcile missed files.
  • Pause expense publication after a tenant-mapping error.

Validation

Tabletop credential leak, personal-data exposure, vendor outage, schema drift, duplicate replay, and destination corruption. Record expected and observed results, including fail-closed behavior.

Resources

  • Current first-party evidence map — recheck dated sources and the selected tenant's in-account contract before relying on mutable endpoints, fields, entitlements, limits, or delivery behavior.
  • Record tenant observations as environment-specific evidence, never universal Navan guarantees.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/navan-incident-runbook of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Navan Incident Runbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Navan Incident Runbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Navan Incident Runbook this skilljeremylongshore/tons-of-skills-marketplace2.8k—~917Automated safety check: PassMIT
Oncallpigweed-project/pigweed548—~963Automated safety check: PassApache-2.0
Activation Governance Chaos RolloutAli-Marandi/DataSense107—~1.9kAutomated safety check: PassMIT
Incident Response686f6c61/alfred-dev117—~1.1kAutomated safety check: PassMIT
Superset Incident Triagesuperset-sh/superset15k—~1kAutomated safety check: PassCustom licence
Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan109—~1.9kAutomated safety check: PassMIT

Similar skills

  • Oncall

    pigweed-project/pigweed

    Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).

    548 GitHub stars~963 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Design, validate, and govern fail-closed customer-activation automations that use an Outbox/worker pattern.

    107 GitHub stars~1.9k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Incident Response

    686f6c61/alfred-dev

    Protocolo de respuesta ante incidentes en produccion: triaje, mitigacion, causa raiz y postmortem.

    117 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Superset Incident Triage

    superset-sh/superset

    Does a read-only first pass on a possible production incident: gathers deploy, Sentry and health-check signals, proposes a severity and status message, then stops for human approval.

    15k GitHub stars~1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Post-Incident Debrief

    VeryGoodOpenSource/vgv-wingspan

    Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.

    109 GitHub stars~1.9k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed
  • SRE Engineer

    Jeffallan/claude-skills

    Defines SLIs, SLOs and error budgets, and sets up golden-signal monitoring, blameless postmortems, toil automation and chaos experiments for production systems.

    12k GitHub stars~1.7k tokensUpdated 7 days ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Navan Incident Runbook

What does Navan Incident Runbook do?

Manage containment, reconciliation, and recovery for a Navan integration incident. Navan Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Manage containment, reconciliation, and recovery for a Navan integration incident.

When should I use Navan Incident Runbook?

Navan Incident Runbook fits situations like: handling credential; delivery failures; with Navan incident; navan data exposure.

How do I install Navan Incident Runbook in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill navan-incident-runbook -a claude-code`. Or copy the skill folder (skills/.curated/navan-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/navan-incident-runbook in your project. Claude Code loads it when a task matches its description.

How do I install Navan Incident Runbook in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill navan-incident-runbook -a codex`. Or copy the skill folder (skills/.curated/navan-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/navan-incident-runbook in your project. Codex loads it when a task matches its description.

Can I use Navan Incident Runbook in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill navan-incident-runbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/navan-incident-runbook, .gemini/skills/navan-incident-runbook, .github/skills/navan-incident-runbook and .opencode/skills/navan-incident-runbook in your project.

What does Navan Incident Runbook need to run?

SKILL.md names no scripts, command-line tools or credentials: Navan Incident Runbook is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live or external Navan actions require network access and explicit approval.

Does Navan Incident Runbook access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Navan Incident Runbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Navan Incident Runbook use?

Navan Incident Runbook is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Navan Incident Runbook use?

About 917 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 286 tokens, read only when the agent opens those files.

What are the alternatives to Navan Incident Runbook?

Skills that share tags, products or a category with Navan Incident Runbook: Oncall (pigweed-project/pigweed, 548 stars), Activation Governance Chaos Rollout (Ali-Marandi/DataSense, 107 stars), Incident Response (686f6c61/alfred-dev, 117 stars) and Superset Incident Triage (superset-sh/superset, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Navan Incident Runbook?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.