runtime-verifier

Execute health checks, HTTP requests, and log inspections on Docker services.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ksopyla/agent-patterns-lab --skill runtime-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-verifier
Source: https://github.com/ksopyla/agent-patterns-lab/tree/main/.cursor/skills/runtime-verifier
Command: npx skills add https://github.com/ksopyla/agent-patterns-lab --skill runtime-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that Docker services and examples are working correctly by performing live runtime verification, including health checks, representative requests, and log inspections.

Core Features & Use Cases

  • Health Checks: Verify the health status of Docker containers and services.
  • Representative Requests: Execute example HTTP requests to ensure services are functioning as expected.
  • Log Inspections: Review container logs for errors and warnings.
  • Use Case: After implementing a new service, use this Skill to confirm that it's running correctly and responding to requests as intended.

Quick Start

Verify the runtime status of the service in the 'examples/01-orchestrator-pipeline' directory.

Frequently Asked Questions about runtime-verifier

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

FAQPage Schema
How do I perform runtime verification on a Docker service after deployment?

Runtime verification for a Docker service is performed by executing health checks, sending representative HTTP requests, and inspecting container logs to confirm the service runs and responds correctly.

What's the best way to check Docker container health and inspect logs for errors?

Checking Docker container health and logs involves reviewing container logs for errors and warnings while verifying the health status of the running containers and services to ensure correct functionality.

Do I need MCP configurations to execute HTTP requests and trace Docker containers?

Yes, performing live runtime verification on Docker services requires Docker and the necessary MCP configurations for tracing and logging during post-implementation checks and debugging sessions.

Can I use runtime verification to debug a newly implemented Docker example?

Yes, you can verify the runtime status of newly implemented Docker examples by executing health checks and representative requests, which is intended for post-implementation checks and debugging sessions.

What limitations exist when performing live runtime verification on Docker services?

Live runtime verification is limited to checking health status, executing representative HTTP requests, and inspecting container logs, requiring Docker and proper MCP configurations to function.