Skip to content
SkillModel-led572 tokens in use

competition-container-runtime

A downstream CTF-sandbox skill for live containers: it compares manifests with running mounts, sidecars and init output and traces which route reaches which container.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-container-runtime

Skill label

measured from its files

What installing competition-container-runtime costs

111tokens idle
572tokens in use
800tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples3/15
  • Output10/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

This skill is a specialization of the ctf-sandbox-orchestrator skill for challenges about what a live container or pod is doing now, as opposed to what its checked-in manifest says. The agent separates manifest, image, startup, live mount, live route and live process, and maps the chain from host and proxy to container, mounted volume and consuming process.

The skill states that it runs only after the orchestrator has set sandbox assumptions.

What You Get

  • A three-step workflow: map the live runtime, trace route and mount boundaries, report the runtime deviation
  • A reference checklist for comparing intent with reality and for tracing who writes, mounts and reads each file
  • A list of high-value deviations such as rendered secrets on shared volumes and init or sidecar output
  • Hand-off rules to four sibling skills for control plane, routing, container escape and Linux credential questions

Common Use Cases

  • Finding which process consumes a mounted secret or rendered config in a lab container
  • Explaining why a route works only after startup because of an init container or sidecar
  • Documenting how a virtual host and proxy resolve to a specific live container

What Makes It Unique

It starts from the position that checked-in manifests are intent and the live container is the evidence. Its checklist asks for the consuming process behind every mounted secret, and it flags sidecar and init output that is missed when only the main service is inspected.

Under The Hood

The skill is instruction text only: a SKILL.md, one reference checklist and an agent configuration file. It ships no scripts. The method involves running container and cluster inspection commands and reading mounted files, so the agent’s own shell tools do that work in the sandbox the orchestrator set up. The skill does not fetch pages or call APIs on its own.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers