service-health-check-audit

Diagnose startup failures, port drift, and health check mismatches across chatbot services.

7|2|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/SkastVnT/AI-Assistant --skill service-health-check-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-health-check-audit
Source: https://github.com/SkastVnT/AI-Assistant/tree/main/.github/skills/service-health-check-audit
Command: npx skills add https://github.com/SkastVnT/AI-Assistant --skill service-health-check-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose startup failures, port drift, and service health issues across the core chatbot stack. It provides a structured approach to verify entry points, ports, virtual envs, and dependencies, surfacing mismatches between scripts, docs, and deployments.

Core Features & Use Cases

  • Startup verification: checks for consistent startup commands, entry points, and environment setups across services.
  • Health endpoint validation: ensures health probes return expected status and that databases are reachable.
  • Documentation alignment: reconciles docs with actual runtime behavior, updating drift risk maps and CI checks.
  • Use Case: When a service fails to start or reports port mismatches, run this audit to identify the root causes and recommended remediation steps.

Quick Start

Run the audit against the current stack to surface startup and health discrepancies.

Frequently Asked Questions about service-health-check-audit

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

FAQPage Schema
How do I diagnose chatbot startup failures and port mismatches across services?

Diagnose chatbot startup failures and port mismatches by running a structured audit that verifies entry points, startup commands, and virtual environment configurations to identify where scripts, docs, and deployment configs diverge.

What is port drift and how does it affect service health checks?

Port drift occurs when configured ports diverge between scripts, documentation, and deployment configs. It causes service health checks to fail by probing incorrect endpoints, which prevents the system from confirming if databases and dependencies are reachable.

How do I verify health endpoints and database reachability for my chatbot stack?

Verify health endpoints and database reachability by enforcing a health check validation sequence across the chatbot stack, ensuring probes return expected statuses and confirming that dependencies are operational before completing the audit.

Can I use this audit to reconcile documentation with actual runtime behavior?

You can use this audit to reconcile documentation with actual runtime behavior by surfacing mismatches between docs and live services, which allows you to update drift risk maps and enforce consistent CI checks across the stack.

Does this health check audit work for complex chatbot deployment configurations?

This health check audit works for complex chatbot deployments by systematically verifying startup sequences, entry points, and environmental dependencies to ensure reliable operation across divergent scripts and deployment configs.

What should I do when service health checks fail due to venv configuration divergence?

When service health checks fail due to venv configuration divergence, run the audit to identify the exact mismatches between scripts and deployment configs, then apply the recommended remediation steps to align the environments.