competition-agent-cloud

Trace prompt-to-tool flows, deployment drift, and artifact provenance in CTF sandbox challenges.

21|8|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill competition-agent-cloud-chengzongcai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: competition-agent-cloud
Source: https://github.com/chengzongcai/reverse-skill-backup/tree/main/CTF-Sandbox-Orchestrator/competition-agent-cloud
Command: npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill competition-agent-cloud-chengzongcai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When tackling CTF challenges involving AI agents, prompt injection, cloud infrastructure, containers, or CI/CD pipelines, it is hard to systematically connect untrusted input to tool side effects or reconcile checked-in manifests with live runtime state. This Skill provides a structured methodology for that analysis under established sandbox assumptions. ## Core Features & Use Cases - Agentic Path Analysis: Map instruction layers, retrieval boundaries, memory files, and tool gates to prove a minimal chain from untrusted content to tool side effects. - Cloud and Container Reconciliation: Compare compose or Kubernetes manifests against live mounts, environment variables, logs, and traffic across build-time, deploy-time, and runtime. - Supply-Chain Provenance Tracing: Track the chain from source to dependency resolution, build, publish, and runtime consumer, focusing on version drift and registry pulls. - Use Case: In a CTF challenge where a prompt-injected agent triggers an unintended tool call, use this Skill to build a compact evidence block linking the retrieved chunk, planner transition, and final tool arguments. ## Quick Start After the ctf-sandbox-orchestrator skill is active, ask the agent to trace the prompt-to-tool flow or deployment drift in this challenge using competition-agent-cloud.

Frequently Asked Questions about competition-agent-cloud

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

FAQPage Schema
How do I analyze prompt injection in a CTF challenge?▼

Map one minimal control chain from untrusted input to model-visible context to tool side effect. Treat prompts, retrieved chunks, planner notes, and tool arguments as evidence artifacts, and prove the chain with minimal instrumentation before exploring variants.

How to detect deployment drift between manifests and runtime?▼

Split analysis into build-time, deploy-time, and runtime phases. Reconcile compose or Kubernetes manifests against live mounts, environment variables, sidecars, logs, and traffic rather than trusting checked-in configuration as deployment truth.

Can I use this skill without ctf-sandbox-orchestrator?▼

No. This is a downstream specialization that requires ctf-sandbox-orchestrator to be active first, since it relies on established sandbox assumptions, node ownership, and evidence priorities before routing to this workflow.

What evidence should I preserve for supply-chain CTF challenges?▼

Keep a compact provenance chain covering source, dependency resolution, build, package or sign, publish, and runtime consumer. Focus on artifact hashes, version drift, registry pulls, CI steps, and the final runtime hook points.

When should I use a more specialized skill instead?▼

Route to dedicated skills for narrower scopes: prompt-boundary abuse, CI and dependency provenance, queue worker drift, SSRF to metadata endpoints, request smuggling, Kubernetes control plane, container runtime secrets, or kernel container escape.