Agent skill · Data & Analytics

flexport-incident-runbook

Execute Flexport incident response for API outages, webhook failures, and supply chain data sync issues with triage and mitigation steps. '

jeremylongshoregithub.com/jeremylongshoreGitHub ↗
claude-coderead-onlyMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill flexport-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.6.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadBash(curl:*)Bash(jq:*)Grep
Requires: Designed for Claude Code
Path: skills/.curated/flexport-incident-runbook/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
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

# Flexport Incident Runbook ## Overview Incident response procedures for Flexport logistics API integration failures. Covers shipment tracking outages, customs data sync failures, webhook delivery loss, and API degradation scenarios. Flexport powers real-time supply chain visibility, so incidents directly impact shipment tracking, booking workflows, and customs compliance reporting. Classify sever

More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the flexport-incident-runbook skill do?

Execute Flexport incident response for API outages, webhook failures, and supply chain data sync issues with triage and mitigation steps. '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill flexport-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.

Keep going