langchain-incident-runbook
Triage LangChain 1.0 / LangGraph 1.0 production incidents \u2014 LLM-specific\ \ SLOs,\nprovider outage runbook, latency spike decision tree, cost-overrun response,\n\ agent loop containment. Use during an on-call page, in a post-mortem, or writing\n\ the team's first LLM runbook.\nTrigger with \"langchain incident\", \"llm on-call\"\ , \"langchain slo\",\n\"langchain outage\", \"langchain cost spike\", \"langchain\ \ agent loop\".\n"
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langchain-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.
# LangChain Incident Runbook ## Overview 3:07am. PagerDuty: "LangChain p95 latency > 10s for 5 minutes." You open LangSmith, filter by `service="triage-agent"` over the last 15 minutes, and the first trace is 43 seconds long — an agent is on step 24 of 25 iterations, bouncing between the same two tools on a vague user prompt ("help me with my account"). The cost dashboard shows **$400 spent in the
What does the langchain-incident-runbook skill do?
Triage LangChain 1.0 / LangGraph 1.0 production incidents \u2014 LLM-specific\ \ SLOs,\nprovider outage runbook, latency spike decision tree, cost-overrun response,\n\ agent loop containment. Use during an on-call page, in a post-mortem, or writing\n\ the team's first LLM runbook.\nTrigger with \"langchain incident\", \"llm on-call\"\ , \"langchain slo\",\n\"langchain outage\", \"langchain cost spike\", \"langchain\ \ agent loop\".\n"
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langchain-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.