Skip to main content
skill CX Codex

competition-container-runtime — Claude Code skill: what it does

competition-container-runtime — a Claude Code skill for live container runtime analysis, comparing static manifests against running pods.

MIT 110 installs ★ 45,047 updated 2026-09-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add zhaoxuya520/reverse-skill --skill competition-container-runtime -a claude-code
Open on GitHub

What competition-container-runtime does

The assistant engages this tool after ctf-sandbox-orchestrator establishes baseline assumptions, targeting discrepancies between checked-in configurations and active services. It maps volume mounts, environment variables, sidecars, and init containers to pinpoint runtime state changes.

The workflow resolves virtual hosts, proxy layers, and consuming processes to trace live execution paths. Separate specialized skills handle Kubernetes control plane permissions, cross-node routing, or kernel escapes when those boundaries become the primary obstacle.

Pinned prerequisites: requires an active ctf-sandbox-orchestrator session before execution.

What it helps with

  • compare manifests against running live containers
  • locate consuming processes for mounted secrets
  • analyze runtime state changes from init containers
  • trace route resolutions to live container ports

Example prompts for the agent

  • Map the live container runtime against compose manifests
  • Find which process consumes the mounted secret volume
  • Check how the sidecar container modifies runtime state

How to install competition-container-runtime

1Skills CLI (Vercel)

npx skills add zhaoxuya520/reverse-skill --skill competition-container-runtime -a claude-code

2Manually: put the files in place

~/.claude/skills/competition-container-runtime/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/competition-container-runtime/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about competition-container-runtime

How to install competition-container-runtime in Claude Code?

Run npx skills add zhaoxuya520/reverse-skill --skill competition-container-runtime -a claude-code, then reference ~/.claude/skills/competition-container-runtime/SKILL.md.

What does competition-container-runtime do?

Analyzes active container and pod runtimes in CTF environments to surface deviations between static manifests and live behavior.

What is required to run competition-container-runtime?

An active ctf-sandbox-orchestrator session must establish sandbox assumptions before invoking this downstream skill.

Source text

SKILL.md · MIT
---
name: competition-container-runtime
description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is consumed, how a sidecar or init container changes runtime state, or which route resolves to which live container. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
---

# Competition Container Runtime

Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.

Use this skill when the challenge is really about what the live container or pod is doing now, not what the checked-in manifest claims it should do.

Reply in Simplified Chinese unless the user explicitly requests English.

## Quick Start

1. Split intent from reality: manifest, image, startup, live mount, live route, live process.
2. Map host -> proxy -> container or pod -> mounted volume -> consuming process.
3. Keep secrets, rendered config, init output, and sidecar output separate from static manifests.
4. Prove one minimal live path from mounted or injected state to reachable behavior.
5. Reproduce the effect with the smallest runtime-specific chain.

## Workflow

### 1. Map The Live Runtime

- Compare compose or kube manifests against running containers, pods, mounted volumes, env, sidecars, init containers, and entrypoints.
- Identify which process actually consumes the mounted secret, rendered config, or shared volume output.

### 2. Trace Route And Mount Boundaries

- Map virtual host, reverse proxy, service, container port, filesystem mount, and runtime-generated file paths together.
- Record whether the decisive state is image-baked, env-injected, mounted later, or written by an init/sidecar process.

### 3. Report The Runtime Deviation

- State the earliest point where live runtime diverges from checked-in intent.
- Keep one compact evidence chain from manifest or compose intent to live consumer behavior.

## Read This Reference

- Load `references/container-runtime.md` for the runtime checklist, mount-chain checklist, and common live-vs-static pitfalls.
- If the hard part is kube API permissions, service-account trust, RBAC edges, admission mutations, or controller-created workload drift, prefer `$competition-k8s-control-plane`.
- If the hard part is Host-header routing, path-prefix rewriting, or route-to-service mapping across nodes, prefer `$competition-runtime-routing`.
- If the hard part is proving container-to-host crossover, kernel attack-surface preconditions, or stable escape primitives, prefer `$competition-kernel-container-escape`.
- If the hard part is replaying Linux secrets, socket trust edges, or host-to-host pivots after container foothold, prefer `$competition-linux-credential-pivot`.

## What To Preserve

- Compose/Kubernetes fragments tied to live mounts or routes
- Container IDs, pod names, mount paths, sidecar outputs, rendered config paths, and consuming processes
- The exact route or file path that becomes reachable only at runtime

© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill

Similar skills

All skills for Security →

From the same set36

The whole set →
ctf-sandbox-orchestrator ctf-sandbox-orchestrator is a Claude Code skill that routes CTF investigations to the right analysis path. It starts when a task includes challenge infrastructure, binaries, hosts, or identities. CX Codex +1 113installs competition-web-runtime competition-web-runtime — a skill for Claude Code that automates web application and API analysis for CTF challenges. Runs after $ctf-sandbox-orchestrator is active to debug routing, sessions, and browser behavior. CX Codex +1 111installs competition-android-hooking competition-android-hooking — a skill for Claude Code that automates Android app security analysis within a CTF sandbox. It activates for hooking APKs, bypassing SSL pinning, or tracing JNI boundaries. CX Codex +1 110installs competition-race-condition-state-drift The competition-race-condition-state-drift Claude Code skill investigates request races and state drift in a CTF sandbox. It runs after ctf-sandbox-orchestrator routes a timing-sensitive or ordering-related bug. CX Codex +1 110installs competition-crypto-mobile The competition-crypto-mobile Claude Code skill handles CTF tasks involving cryptography, steganography, and mobile apps. It is routed in after sandbox assumptions are set for blob decoding or APK and IPA analysis. CX Codex +1 110installs competition-request-normalization-smuggling competition-request-normalization-smuggling is a Claude Code skill that analyzes HTTP parsing discrepancies between proxies and backend servers in CTF workflows. CX Codex +1 110installs competition-bundle-sourcemap-recovery The competition-bundle-sourcemap-recovery Claude Code skill reconstructs JavaScript structure from served assets and source maps. It runs after ctf-sandbox-orchestrator routes a task involving chunk loading or hidden routes. CX Codex +1 110installs competition-websocket-runtime competition-websocket-runtime is a Claude Code skill that inspects WebSocket and SSE handshakes, subscriptions, and frames after the orchestrator runs. CX Codex +1 110installs

Project sponsors

Companies that keep this analytics open