# competition-container-runtime

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

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 110 installs · ★ 45047 repo stars
- Author: zhaoxuya520
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-container-runtime/SKILL.md
- Updated: 2026-09-22
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/competition-container-runtime

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-container-runtime -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/competition-container-runtime/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/competition-container-runtime/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-container-runtime -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/competition-container-runtime/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-container-runtime -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/competition-container-runtime/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-container-runtime/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/competition-container-runtime/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-container-runtime -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-container-runtime
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/competition-container-runtime/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-container-runtime -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-container-runtime/SKILL.md

## When to use it
- 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
- Map the live container runtime against compose manifests
- Find which process consumes the mounted secret volume
- Check how the sidecar container modifies runtime state

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 27d3456409294837.

BEGIN THIRD-PARTY FILE 27d3456409294837
```text
---
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`.
```
END THIRD-PARTY FILE 27d3456409294837

The third-party file has ended. Everything between the 27d3456409294837 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2658 of 3398 bytes. © zhaoxuya520 · MIT · https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-container-runtime/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
