competition-supply-chain — Claude Code skill: trace artifacts
The competition-supply-chain Claude Code skill traces artifact provenance from source to runtime. It is routed after ctf-sandbox-orchestrator when a challenge involves dependency drift, CI, builds, or releases.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-supply-chain -a claude-codeWhat competition-supply-chain does
The skill follows an artifact from source checkout through dependency resolution, build, packaging, publication, and runtime use. It compares declared and resolved dependency versions with the shipped artifact, then identifies the earliest point where the chain diverges.
It runs only after ctf-sandbox-orchestrator has established sandbox assumptions, node ownership, and evidence priorities. The workflow keeps findings in one short provenance chain and reproduces the smallest build or packaging path that demonstrates the issue. references/supply-chain.md contains the provenance checklist and common pipeline failure modes.
What it helps with
- locate where a resolved dependency diverges from its declared version
- trace registry pulls and changes made during CI
- compare image contents with the artifact used at runtime
- identify which pipeline step altered a release package
Example prompts for the agent
- Trace why the running artifact uses a different dependency version from the lockfile.
- Find the CI step that changed the package before publication.
- Identify which image or package the application actually uses at runtime.
How to install competition-supply-chain
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-supply-chain -a claude-code2Manually: put the files in place
~/.claude/skills/competition-supply-chain/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-supply-chain/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-supply-chain -a codex2Manually: put the files in place
.agents/skills/competition-supply-chain/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-supply-chain -a cursor2Manually: put the files in place
.cursor/skills/competition-supply-chain/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-supply-chain/SKILL.md2Manually: put the files in place
.github/skills/competition-supply-chain/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-supply-chain -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-supply-chainManually: put the files in place
.devin/skills/competition-supply-chain/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-supply-chain -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-supply-chain
How do I install competition-supply-chain in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-supply-chain -a claude-code. The skill file is at ~/.claude/skills/competition-supply-chain/SKILL.md.
What does competition-supply-chain do?
It traces dependencies, builds, publication, and the artifact consumed at runtime. The workflow pinpoints the earliest break between the expected and shipped artifact.
What has to happen before competition-supply-chain runs?
ctf-sandbox-orchestrator must first establish the sandbox assumptions, node ownership, and evidence priorities. This skill is used downstream of that setup.
Source text
SKILL.md · MIT
--- 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
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill