replit-observability
Sets up health endpoints, performance monitoring, and alerting for Replit-hosted services.
Install
mkdir -p .claude/skills/replit-observability && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7594" && unzip -o skill.zip -d .claude/skills/replit-observability && rm skill.zipInstalls to .claude/skills/replit-observability
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.
Monitor Replit deployments with health checks, uptime tracking, resourceKey capabilities
- →Implement health endpoints with detailed metrics
- →Configure structured JSON logging
- →Set up external uptime monitoring
- →Detect cold starts in Autoscale deployments
- →Configure Slack alerting for memory and error rates
How it works
The skill provides patterns for exposing health metrics via an Express endpoint and integrating with external monitoring services to track uptime and performance. It also includes middleware for structured logging and cold start detection.
Inputs & outputs
When to use replit-observability
- →Implementing application health endpoints
- →Setting up uptime and availability alerts
- →Monitoring resource consumption
- →Building health dashboards for Replit apps
About replit-observability
Implements structured health checks and performance monitoring patterns. It enables developers to track resource usage and deployment reliability through external monitoring tools.
Set up comprehensive observability for Replit integrations with metrics, traces, and alerts. Use when implementing monitoring for Replit operations, setting up dashboards, or configuring alerting for Replit integration health. Trigger with phrases like "replit monitoring", "replit metrics", "replit observability", "monitor replit", "replit alerts", "replit tracing".
When not to use it
- →When monitoring non-Replit infrastructure
- →When lacking access to deployment settings
Prerequisites
Limitations
- →Deployment logs are missing if the container restarts
- →Cold starts may remain undetected without external monitoring
How it compares
Unlike manual logging, this approach standardizes health checks and integrates directly with Replit's deployment lifecycle for automated alerting.
Compared to similar skills
replit-observability side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| replit-observability (this skill) | 1 | 2mo | Caution | Intermediate |
| distributed-tracing | 5 | 4mo | No flags | Intermediate |
| service-mesh-observability | 5 | 4mo | No flags | Advanced |
| observability-engineer | 12 | 5mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
distributed-tracing
wshobson
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
service-mesh-observability
wshobson
Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.
observability-engineer
sickn33
Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.
prometheus-configuration
wshobson
Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.
langfuse
davila7
Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production. Use when: langfuse, llm observability, llm tracing, prompt management, llm evaluation.
slo-implementation
wshobson
Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.