reverse-skills-max: initial public release (restored, redacted, hardened)

reverse-skill-repo/CTF-Sandbox-Orchestrator/competition-supply-chain/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: competition-supply-chain
+description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for CI/CD, registry, dependency drift, artifact provenance, image build, release pipeline, and runtime consumer challenges. Use when the user asks to trace dependency drift, registry pulls, malicious packages, build or release tampering, CI execution, artifact signing, or which shipped artifact the runtime actually consumes. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
+---
+
+# Competition Supply Chain
+
+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 provenance, dependency drift, build output, release flow, or what runtime artifact actually got shipped.
+
+Reply in Simplified Chinese unless the user explicitly requests English.
+
+## Quick Start
+
+1. Split the problem into source, dependency resolution, build, packaging, publish, and runtime consumption.
+2. Decide where the first divergence occurs between intended artifact and runtime artifact.
+3. Keep provenance as a compact chain, not a scattered set of observations.
+4. Reproduce the smallest possible build or package path that still shows the issue.
+5. Separate checked-in intent from what the pipeline actually emitted.
+
+## Workflow
+
+### 1. Trace Provenance End-To-End
+
+- Map source checkout, lockfiles, dependency fetch, pre/post-install steps, build scripts, packaging, publish target, and runtime consumer.
+- Compare declared version, resolved version, and shipped artifact.
+- Note registry, cache, mirror, or CI environment differences.
+
+### 2. Reconcile Build-Time And Runtime
+
+- Compare manifests with image layers, mounted secrets, generated files, and runtime hooks.
+- Identify whether the decisive mutation happens in dependency install, build step, publish step, or runtime bootstrap.
+
+### 3. Report The Break Point
+
+- State the earliest point where provenance diverges.
+- Keep evidence in one short chain from source to runtime consumer.
+
+## Read This Reference
+
+- Load `references/supply-chain.md` for the provenance checklist, evidence packaging, and common pipeline failure modes.
+
+## What To Preserve
+
+- Declared dependency, resolved dependency, and runtime artifact versions
+- CI step names, registry pulls, artifact hashes, and image or package layers
+- The runtime consumer that actually accepts or executes the artifact

reverse-skill-repo/CTF-Sandbox-Orchestrator/competition-supply-chain/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Competition Supply Chain"
+  short_description: "Trace dependency drift, CI output, and shipped artifact lineage"
+  default_prompt: "After $ctf-sandbox-orchestrator is active, use $competition-supply-chain to trace dependency drift, CI behavior, release tampering, and which artifact the runtime really consumes."
+
+policy:
+  allow_implicit_invocation: false

reverse-skill-repo/CTF-Sandbox-Orchestrator/competition-supply-chain/references/supply-chain.md

@@ -0,0 +1,26 @@
+# Supply Chain And CI Checklist
+
+## Provenance Chain
+
+Track this order explicitly:
+
+1. Source checkout
+2. Dependency declaration
+3. Lockfile or resolver result
+4. Build step
+5. Packaging or signing step
+6. Publish target
+7. Runtime consumer
+
+## High-Value Evidence
+
+- Version drift between source, lockfile, and fetched artifact
+- Registry or mirror pulls that differ from expected origin
+- Build scripts with preinstall, prepare, postinstall, or codegen steps
+- Signed or packaged artifact hash compared to runtime-loaded artifact
+
+## Common Pitfalls
+
+- Stopping at lockfile drift without proving runtime consumption
+- Treating checked-in manifests as equivalent to live pipeline behavior
+- Losing the earliest divergence point inside a wall of CI logs