runtime-analyst

Audit microservice runtime configurations and generate Part 10 documentation.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Muath2000/TradeStation --skill runtime-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-analyst
Source: https://github.com/Muath2000/TradeStation/tree/main/.claude/skills/runtime-analyst
Command: npx skills add https://github.com/Muath2000/TradeStation --skill runtime-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and examples (resource) components.

What problem does it solve?

This Skill automates the comprehensive auditing and documentation of a service's runtime configuration and deployment topology, ensuring production readiness and identifying potential risks.

Core Features & Use Cases

  • Runtime Configuration Audit: Analyzes Dockerfiles, container settings, environment variables, and resource allocations.
  • Deployment Topology Mapping: Documents orchestration manifests (Kubernetes, Docker Compose), health probes, and startup/shutdown sequences.
  • Production Readiness Assessment: Validates against a strict checklist for security, scalability, and reliability.
  • Use Case: A new microservice is ready for deployment. Use this Skill to generate a Part 10 document detailing its container setup, K8s deployment, resource limits, and security context, ensuring it meets all production standards.

Quick Start

Run a quick 5-minute audit of the runtime configuration for all services.

Frequently Asked Questions about runtime-analyst

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

FAQPage Schema
How do I audit Kubernetes manifests and Dockerfiles for production readiness?

Auditing Kubernetes manifests and Dockerfiles involves analyzing containerization, orchestration, environment configuration, resource limits, and runtime security to validate production readiness and identify deployment risks. This generates Part 10 documentation.

What is runtime configuration audit for microservices?

Runtime configuration audit is the process of analyzing Dockerfiles, container settings, environment variables, and resource allocations for microservices. It verifies deployment topology, health probes, and startup sequences to ensure reliability and security.

How do I document deployment topology and health probes for a new microservice?

Documenting deployment topology requires analyzing orchestration manifests like Kubernetes and Docker Compose to map out health probes, startup sequences, and infrastructure dependencies. This produces comprehensive Part 10 documentation for the service.

Can I use this to check Docker Compose and Helm charts for resource limits and security?

Yes, you can analyze Docker Compose and Helm charts to audit resource limits, port mappings, environment variables, and runtime security contexts. This validates the configuration against strict production readiness standards.

What is the best way to generate deployment documentation for Docker and Kubernetes?

The best way to generate deployment documentation is to automate the analysis of Dockerfiles, Kubernetes manifests, and Helm charts. This audits container setup, resource allocation, and security context to produce detailed Part 10 documents.

Why does my microservice deployment fail production readiness checks?

Microservice deployments fail production readiness checks due to missing or misconfigured health probes, inadequate resource limits, improper startup sequences, or runtime security vulnerabilities found within Dockerfiles and Kubernetes manifests.