marsai:dev-readyz

Automate startup-health validation with readyz and startup self-probe checks.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/V4-Company/marsai --skill marsai-dev-readyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: marsai:dev-readyz
Source: https://github.com/V4-Company/marsai/tree/main/dev-team/skills/dev-readyz
Command: npx skills add https://github.com/V4-Company/marsai --skill marsai-dev-readyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures startup and runtime reliability for services with external dependencies by performing comprehensive readyz checks and startup self-probes, exposing per-dependency status with latency and TLS information to prevent silent outages.

Core Features & Use Cases

  • Dependency Scanning & Validation: Detects all external dependencies (databases, caches, queues) and validates TLS configuration according to deployment mode.
  • Readyz & Health Endpoints: Implements /api/admin/health/readyz and /health to report per-dependency health with latency and TLS posture.
  • Startup Self-Probe: Runs dependency validation at startup and blocks traffic until startupHealthy is true, ensuring safe rollout.

Quick Start

Configure and run the startup self-probe on a new service to validate all external dependencies and TLS posture before traffic is permitted.

Frequently Asked Questions about marsai:dev-readyz

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

FAQPage Schema
How do I validate external dependencies and TLS configuration before routing traffic to a new service?

Startup self-probe checks validate external dependencies and TLS configuration before traffic is permitted. Running these probes at startup blocks incoming requests until startupHealthy is true, preventing silent outages during service rollout.

What is the difference between readyz and health endpoints for runtime readiness checks?

Readyz endpoints report per-dependency health including latency and TLS posture, while general health endpoints provide overall service status. Both expose external dependency readiness to ensure databases, caches, and queues are fully operational before handling requests.

How do I implement startup probes for SaaS services with multiple external dependencies?

Startup probes for SaaS services automate dependency scanning to detect databases, caches, and queues. The probe validates TLS configuration for each external dependency and blocks traffic until all checks pass, ensuring safe rollout and runtime reliability.

Does Kubernetes readyz probe configuration support per-dependency latency and TLS verification?

Kubernetes readyz probe configuration supports per-dependency latency and TLS verification by exposing /api/admin/health/readyz endpoints. These endpoints validate TLS posture and report individual dependency status to prevent silent outages.

Why does my service experience silent outages when external dependencies fail during startup?

Silent outages occur when services handle traffic before external dependencies like databases and queues are ready. Startup self-probes validate dependencies and TLS posture at launch, blocking traffic until startupHealthy is true to ensure reliability.

Can I use readyz probes to check database, cache, and queue connections simultaneously during startup?

Readyz probes check database, cache, and queue connections simultaneously during startup. Dependency scanning detects all external services and validates their TLS configuration, blocking traffic until every dependency passes the startup self-probe.