Oncall
pigweed-project/pigweed
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
Triage and recover a Webflow integration incident with read-only evidence, write freezes, and verified recovery.
Install Webflow Incident Runbook
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill webflow-incident-runbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace webflow-incident-runbook --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/webflow-incident-runbook .claude/skills/webflow-incident-runbook && rm -rf skills-srcUse ~/.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/
Install the "webflow-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/webflow-incident-runbook into .claude/skills/webflow-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webflow-incident-runbook", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/webflow-incident-runbookType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill webflow-incident-runbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace webflow-incident-runbook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/webflow-incident-runbook .agents/skills/webflow-incident-runbook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "webflow-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/webflow-incident-runbook into .agents/skills/webflow-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webflow-incident-runbook", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill webflow-incident-runbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace webflow-incident-runbook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/webflow-incident-runbook .cursor/skills/webflow-incident-runbook && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "webflow-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/webflow-incident-runbook into .cursor/skills/webflow-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webflow-incident-runbook", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/webflow-incident-runbook--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill webflow-incident-runbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace webflow-incident-runbook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/webflow-incident-runbook .gemini/skills/webflow-incident-runbook && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "webflow-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/webflow-incident-runbook into .gemini/skills/webflow-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webflow-incident-runbook", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace webflow-incident-runbookInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill webflow-incident-runbook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/webflow-incident-runbook .github/skills/webflow-incident-runbook && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "webflow-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/webflow-incident-runbook into .github/skills/webflow-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webflow-incident-runbook", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill webflow-incident-runbook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace webflow-incident-runbook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/webflow-incident-runbook .opencode/skills/webflow-incident-runbook && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "webflow-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/webflow-incident-runbook into .opencode/skills/webflow-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webflow-incident-runbook", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
webflow-incident-runbook- GitHub stars
- 2.8k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 537 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Triage and recover a Webflow integration incident with read-only evidence, write freezes, and verified recovery.
- Works in 6 steps: Declare severity, affected… → Check Webflow status and your own… → Classify the failure: identity/auth,… → …
- Handling auth failures
- SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Webflow Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Triage and recover a Webflow integration incident with read-only evidence, write freezes, and verified recovery. Use when handling auth failures, 429s, 5xx errors, webhook loss, bad publication, or Cloud deploy failure. Trigger with "Webflow incident", "Webflow outage", or "Webflow rollback".
Its SKILL.md is about 1.2k 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
It sits in DevOps & Cloud, covering Runbooks and postmortems, Incident response and Webhooks. It works with Webflow. 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 auth failures
- Bad publication
- Cloud deploy failure
- With Webflow incident
Example prompts
- “Webflow incident”
- “Webflow outage”
- “Webflow rollback”
- “/webflow-incident-runbook”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Declare severity, affected environment/sites, user impact, start time, incident owner, and whether live writes are frozen.
- Check Webflow status and your own service independently; capture redacted structured errors, headers, deployment IDs, and webhook evidence.
- Classify the failure: identity/auth, permission, budget, Webflow service, application, webhook, content state, or deployment.
- Contain without guessing: pause workers, stop publication, serve an approved cached fallback, or isolate the failing tenant.
- Apply one evidence-backed remediation with a rollback. Reconcile every uncertain write before resuming.
- Verify read and write paths, staged/live state, webhook delivery, rate headroom, and public routes; record timeline and follow-up actions.
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:
ReadGlobGrepWebFetchWriteEdit
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
Links to these hosts (documentation or services it may open):
developers.webflow.com
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
From compatibility in the SKILL.md frontmatter.
Context cost
Webflow Incident Runbook loads about 1.2k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 537 words of instructions outside code blocks.
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). 537 words, ~1,214 tokens.
Download SKILL.mdSave it as
.claude/skills/webflow-incident-runbook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- webflow-incident-runbook
- description
- Triage and recover a Webflow integration incident with read-only evidence, write freezes, and verified recovery. Use when handling auth failures, 429s, 5xx errors, webhook loss, bad publication, or Cloud deploy failure. Trigger with "Webflow incident", "Webflow outage", or "Webflow rollback".
- allowed-tools
- Read, Glob, Grep, WebFetch, Write, Edit
- compatibility
- Designed for Claude Code
- argument-hint
- [project-path] [incident-id] [environment]
- version
- 1.6.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, webflow, incident-response, reliability
- model
- inherit
- effort
- medium
Webflow Incident Response
Overview
This skill produces a repo-grounded Webflow plan or implementation. It treats current official documentation and the target project's installed versions as authority, keeps discovery read-only, and separates preparation from live mutation.
Prerequisites
- A named target repository or project path and permission to inspect it
- The intended Webflow environment and non-secret resource identities, or a plan to discover them read-only
- Access to current official Webflow documentation; credentials stay in the user's existing secret store
Tool Discipline
Use Read for repository instructions and relevant files, Glob to inventory manifests and Webflow integration paths, and Grep to locate API hosts, IDs, scopes, and credential names. Use WebFetch only for current official Webflow documentation. Use Write for a new user-requested artifact and Edit for minimal changes to existing files after the evidence pass.
Current Contract
- 401, 403, 429, and 5xx conditions require different action; rotating tokens is not a universal first response.
- An uncertain write must be reconciled by reading current resource state before retry.
- Webhook failures are retried only a bounded number of times and redirects, non-200s, TLS errors, and timeouts fail delivery.
- Cloud recovery must reference a specific deployment and terminal status; a previous successful deployment can be an explicit rollback target.
Authentication
Authenticate Data API calls with a bearer token selected for the integration: a site token for controlled single-site work, a workspace token only for its supported workspace/read use cases, or OAuth for user-authorized applications. Derive scopes from the exact endpoints. Never read, echo, persist, or place token values in commands, patches, examples, logs, or reports.
Workflow
- Declare severity, affected environment/sites, user impact, start time, incident owner, and whether live writes are frozen.
- Check Webflow status and your own service independently; capture redacted structured errors, headers, deployment IDs, and webhook evidence.
- Classify the failure: identity/auth, permission, budget, Webflow service, application, webhook, content state, or deployment.
- Contain without guessing: pause workers, stop publication, serve an approved cached fallback, or isolate the failing tenant.
- Apply one evidence-backed remediation with a rollback. Reconcile every uncertain write before resuming.
- Verify read and write paths, staged/live state, webhook delivery, rate headroom, and public routes; record timeline and follow-up actions.
Show full SKILL.md (173 more words)Show less
Approval Boundaries
Default to read-only inspection. Before any create, update, delete, publish, unpublish, archive, deploy, token revoke, or webhook registration, show the exact environment and resource IDs, the proposed change, validation method, and rollback or compensating action. Proceed only when the user's request clearly authorizes that mutation; require a fresh explicit approval for production publication or destructive work.
Output
Return the inspected project and versions, verified Webflow identities, relevant endpoint and scope contract, changes proposed or made, validation evidence, live-mutation status, rollback readiness, and remaining risks. Distinguish documented fact, repository evidence, and inference.
Error Handling
| Condition | Response |
|---|---|
| 401/403 | Verify token type, revocation, identity, and endpoint scope before considering rotation. |
| 429 | Honor Retry-After, coordinate shared-key workers, and reduce concurrency. |
| Bad live content | Freeze further publishes and execute the approved item-level or deployment recovery plan. |
Examples
For a 429 storm, freeze nonessential workers, record per-key headers and callers, honor Retry-After, restore a shared queue below the plan budget, and verify headroom before reopening writes.
Resources
© 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/webflow-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
Webflow 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Webflow Incident Runbook this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Oncallpigweed-project/pigweed | 548 | — | ~963 | Automated safety check: Pass | Apache-2.0 | |
| Activation Governance Chaos RolloutAli-Marandi/DataSense | 107 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Incident Response686f6c61/alfred-dev | 117 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Superset Incident Triagesuperset-sh/superset | 15k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan | 109 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Activation Governance Chaos Rollout
Ali-Marandi/DataSense
Design, validate, and govern fail-closed customer-activation automations that use an Outbox/worker pattern.
Incident Response
686f6c61/alfred-dev
Protocolo de respuesta ante incidentes en produccion: triaje, mitigacion, causa raiz y postmortem.
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.
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.
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.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming 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.
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.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
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.
Related
Works with
Categories
Questions about Webflow Incident Runbook
What does Webflow Incident Runbook do?
Triage and recover a Webflow integration incident with read-only evidence, write freezes, and verified recovery. Webflow Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Triage and recover a Webflow integration incident with read-only evidence, write freezes, and verified recovery.
When should I use Webflow Incident Runbook?
Webflow Incident Runbook fits situations like: handling auth failures; bad publication; cloud deploy failure; with Webflow incident.
How do I install Webflow Incident Runbook in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill webflow-incident-runbook -a claude-code`. Or copy the skill folder (skills/.curated/webflow-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/webflow-incident-runbook in your project. Claude Code loads it when a task matches its description.
How do I install Webflow Incident Runbook in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill webflow-incident-runbook -a codex`. Or copy the skill folder (skills/.curated/webflow-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/webflow-incident-runbook in your project. Codex loads it when a task matches its description.
Can I use Webflow 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 webflow-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/webflow-incident-runbook, .gemini/skills/webflow-incident-runbook, .github/skills/webflow-incident-runbook and .opencode/skills/webflow-incident-runbook in your project.
What does Webflow Incident Runbook need to run?
SKILL.md names no scripts, command-line tools or credentials: Webflow Incident Runbook is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code.
Does Webflow Incident Runbook access the network?
SKILL.md names 1 domain. As links in the text: developers.webflow.com. This is read from the text; nothing was executed.
Is Webflow 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 Webflow Incident Runbook use?
Webflow 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 Webflow Incident Runbook use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 205 tokens, read only when the agent opens those files.
What are the alternatives to Webflow Incident Runbook?
Skills that share tags, products or a category with Webflow 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 Webflow 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.