navan-debug-bundle
Use when collecting diagnostic data from a Navan API integration \u2014\ \ OAuth token inspection, API response capture, connectivity testing, and request/response\ \ logging.\nTrigger with \"navan debug bundle\" or \"debug navan api\".\n"
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill navan-debug-bundle --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 Debug Bundle ## Overview Collect diagnostic data from Navan REST API integrations into a structured, shareable debug bundle. Navan has no SDK — all debugging uses raw HTTP requests against their OAuth 2.0 REST endpoints. ## Prerequisites - Navan API credentials: `client_id` and `client_secret` from Admin > Travel admin > Settings > Integrations - `curl` and `jq` installed locally - Credent
What does the navan-debug-bundle skill do?
Use when collecting diagnostic data from a Navan API integration \u2014\ \ OAuth token inspection, API response capture, connectivity testing, and request/response\ \ logging.\nTrigger with \"navan debug bundle\" or \"debug navan api\".\n"
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill navan-debug-bundle --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.
