post-deploy-check

Name: post-deploy-check
Availability: InStock
Author: jongensutrecht

Verify deployed containerized services via health endpoints and recent logs.

1|Updated Jan 13, 2026

Search Tags:#deployment #logs #verification #container #health-check #post-deploy

Ready to run

npx skills add https://github.com/jongensutrecht/demo-ai-stack --skill post-deploy-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: post-deploy-check
Source: https://github.com/jongensutrecht/demo-ai-stack/tree/main/lars%20skills/post-deploy-check
Command: npx skills add https://github.com/jongensutrecht/demo-ai-stack --skill post-deploy-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork after a deploy by checking whether a service is truly live, healthy, and behaving correctly with hard evidence instead of assumptions.

Core Features & Use Cases

Live Service Verification: Confirms container or process status, recent startup logs, and restart behavior.
Health and Smoke Validation: Checks health endpoints and can perform a real request against a public endpoint when appropriate.
Safe Evidence Reporting: Uses fingerprints and masked output for config checks so secrets are never exposed.
Use Case: After a deploy, restart, or token rotation, use this Skill to determine whether the service is healthy, degraded, broken, or unknown.

Quick Start

Ask the skill to verify the named service on the target server after deployment and return an evidence-based verdict from container status, health checks, and recent logs.

Frequently Asked Questions about post-deploy-check

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

FAQPage Schema

How do I verify a containerized service is truly live after a deployment?▼

Post-deploy verification confirms a service is live by checking container status, validating health endpoints, and inspecting recent startup logs. This provides an evidence-based verdict on whether your deployed service is healthy, degraded, or broken.

What does a post-deploy health check include for containerized services?▼

A post-deploy health check includes confirming container status, validating health endpoints, reviewing restart behavior, and optionally performing a real request against a public endpoint to validate service behavior with hard evidence.

Can I use post-deploy verification after a token rotation or configuration change?▼

Yes, post-deploy verification applies to token rotations and configuration changes. It uses fingerprints and masked output for config checks so secrets are never exposed, returning an evidence-based verdict on service health.

How do I check service logs and container status without exposing secrets?▼

You can check logs and container status safely using masked output and config fingerprints during verification. This ensures secrets are never exposed while still determining if the service is healthy, degraded, or broken.

What is the best way to confirm a remote server service is healthy after a restart?▼

The best way to confirm a service is healthy after a restart is to evaluate container status, health endpoint validation, and recent log inspection together. This yields an evidence-based verdict on the service's live state.