health-check

Verify health of web, API, Celery, Postgres, and Redis services.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/phoenicisf/forex-analyzer --skill health-check-phoenicisf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health-check
Source: https://github.com/phoenicisf/forex-analyzer/tree/main/.agents/skills/health-check
Command: npx skills add https://github.com/phoenicisf/forex-analyzer --skill health-check-phoenicisf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end health verification of core services (Web, API, Celery, PostgreSQL, Redis) to quickly detect outages and connectivity issues.

Core Features & Use Cases

  • Web service health checks on port 3000
  • API health endpoint checks on /health (port 5000)
  • Celery worker status verification via ping
  • PostgreSQL and Redis availability checks
  • Actionable status reports and quick remediation guidance

Quick Start

Run the health-check skill after deployment to verify all core services are up and reachable.

Frequently Asked Questions about health-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify containerized service health after a deployment?

You can check Docker stack health by running automated checks that verify web, API, Celery, Postgres, and Redis endpoints, returning structured statuses with recommended next steps for any unreachable services.

How do I check if Postgres and Redis are reachable before integration tests?

Check Postgres and Redis availability before integration tests by running automated connectivity checks that return structured status reports and quick remediation guidance for any unresponsive database or cache services.

Does this health check tool work with Celery workers and API endpoints on different ports?

Yes, the health check tool works with Celery workers via ping and API endpoints on port 5000, verifying responsiveness across web services on port 3000 alongside Postgres and Redis availability checks.

What is the best way to monitor service uptime across a containerized stack?

The best way to monitor service uptime across a containerized stack is running automated health checks that test web, API, Celery, Postgres, and Redis endpoints, returning actionable status reports with remediation guidance.

Why does my API health endpoint check fail after a container restart?

API health endpoint checks on port 5000 may fail after a container restart if the service is not fully responsive, and the automated check will return a structured status with recommended next steps for quick remediation.