agentskills.codes
RE

replit-incident-runbook

by jeremylongshoreCodingSource

Emergency procedures for triaging and recovering from Replit hosting and deployment outages.

DebuggingMonitoringDeployment

Install

mkdir -p .claude/skills/replit-incident-runbook && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8585" && unzip -o skill.zip -d .claude/skills/replit-incident-runbook && rm skill.zip

Installs to .claude/skills/replit-incident-runbook

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Execute Replit incident response: triage deployment failures, database
70 charsno explicit “when” trigger
Intermediate

Key capabilities

  • →Perform incident triage for deployment crashes and database issues
  • →Execute rollback to previous deployment versions
  • →Capture incident timelines and post-mortem reports
  • →Monitor platform status via Replit API
  • →Diagnose cold start latency and autoscale issues

How it works

The runbook provides a decision tree and bash scripts to query Replit health endpoints, analyze deployment logs, and trigger rollbacks via the Replit interface.

Inputs & outputs

You give it
Deployment URL or incident details
You get back
Diagnostic logs, incident report, or restored deployment

When to use replit-incident-runbook

  • →Triage app deployment crashes
  • →Rollback failed deployments
  • →Debug platform-level outages
  • →Perform incident post-mortem

About replit-incident-runbook

Provides diagnostic steps for Replit deployment crashes, database connection issues, and platform outages. Includes procedures for rollback, triage, and post-incident review.

Execute Replit incident response procedures with triage, mitigation, and postmortem. Use when responding to Replit-related outages, investigating errors, or running post-incident reviews for Replit integration failures. Trigger with phrases like "replit incident", "replit outage", "replit down", "replit on-call", "replit emergency", "replit broken".

When not to use it

  • →When the Replit platform itself is experiencing a total outage
  • →When attempting to rollback database schema changes

Prerequisites

Access to Replit Workspace and Deployment settingsDeployment URL for health checksCommunication channelRollback awareness

Limitations

  • →Rollback does not revert database changes
  • →Logs may be truncated if the container restarts

How it compares

Unlike manual troubleshooting, this provides a structured severity-based response framework and automated diagnostic scripts for Replit-specific infrastructure.

Compared to similar skills

replit-incident-runbook side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
replit-incident-runbook (this skill)02moCautionIntermediate
vercel-advanced-troubleshooting32moCautionAdvanced
stac-troubleshooter17moReviewIntermediate
analyzing-logs142moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore →

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

vercel-advanced-troubleshooting

jeremylongshore

Execute apply Vercel advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Vercel support escalation. Trigger with phrases like "vercel hard bug", "vercel mystery error", "vercel impossible to debug", "difficult vercel issue", "vercel deep debug".

320

stac-troubleshooter

StacDev

Diagnose Stac build, deploy, rendering, caching, and navigation issues using repeatable checks. Use when users report stac build finding no screens, deploy mismatches, runtime unknown widget/action errors, cache staleness, or migration regressions.

13

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

sentry

openai

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

1048

obsidian-incident-runbook

jeremylongshore

Troubleshoot Obsidian plugin failures with systematic incident response. Use when plugins crash, data is corrupted, or users report critical issues with your Obsidian plugin. Trigger with phrases like "obsidian crash", "obsidian plugin broken", "obsidian incident", "debug obsidian failure", "obsidian emergency".

346

obsidian-observability

jeremylongshore

Set up comprehensive logging and monitoring for Obsidian plugins. Use when implementing debug logging, tracking plugin performance, or setting up error reporting for your Obsidian plugin. Trigger with phrases like "obsidian logging", "obsidian monitoring", "obsidian debug", "track obsidian plugin".

534

Search skills

Search the agent skills registry