Skip to content
cccskills
FreePublished on GitHub

competition-supply-chain

Trace software artifacts from source and dependencies through builds, publishing, and runtime use in CTF sandboxes. Compare intended versions with shipped files to identify the earliest divergence and document the evidence linking each stage.

OriginalShow the original 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.

See how to install

Good for

  • Comparing declared, resolved, and shipped dependency versions
  • Tracing package or build tampering through CI/CD
  • Identifying the artifact actually used at runtime
  • Locating the first divergence in an artifact's history

Files included (3)

  • SKILL.md2.6 KB
  • agents/openai.yaml385 B
  • references/supply-chain.md754 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

api-security

FreeSummary

Assess authorized APIs through a ten-stage workflow covering endpoint discovery, authentication, access permissions, input handling, and request limits. Collect reproducible evidence and turn findings into regression checks that can run in a development pipeline.

  • Review API authentication and access permissions
  • Assess GraphQL and WebSocket security
  • Check request limits and unintended data exposure
zhaoxuya520/reverse-skill43.1KUpdated Sep 22, 2026

apk-reverse

FreeSummary

Inspect Android APKs from the command line to understand app logic, permissions, and components. Supports Java decompilation, low-level code edits, rebuilding and signing, plus Frida observation of running methods and routing to native code analysis.

  • Inspecting APK entry points, components, and permissions
  • Locating login, signing, and certificate checks
  • Editing smali code and rebuilding an APK
zhaoxuya520/reverse-skill43.1KUpdated Sep 22, 2026

attack-chain

FreeSummary

Plan and coordinate authorized penetration tests across multiple stages, from reconnaissance to access, privilege escalation, movement between systems, and impact assessment. Assign specialist skills, revise blocked paths, and maintain evidence and progress records for the final report.

  • Plan a penetration test across multiple stages
  • Assess how far a vulnerability could lead
  • Replan from existing credentials or system access
zhaoxuya520/reverse-skill43.1KUpdated Sep 22, 2026

binary-diff

FreeSummary

Transfer known function and variable names from an older binary to a newer version. Compare disassembly and pseudocode with an LLM, produce structured mappings, and apply names and comments in IDA.

  • Migrate known function names after a software update
  • Locate kernel functions when the new PDB is unavailable
  • Find updated function addresses and structure offsets
zhaoxuya520/reverse-skill43.1KUpdated Sep 22, 2026

Inspect compiled programs in Binary Ninja using strings, function references, and intermediate representations—views of program logic at different levels. Trace data flow and report findings with addresses, supporting evidence, confidence, and reproduction steps.

  • Tracing function calls and data flow in Binary Ninja
  • Cross-checking findings from other disassemblers
  • Automating binary analysis with the Python API
zhaoxuya520/reverse-skill43.1KUpdated Sep 22, 2026

Automate website navigation, form filling, content collection, and Windows desktop interactions. The skill selects browser or desktop tools for the task and guides screenshot capture and desktop network traffic observation when needed.

  • Automating website login and form entry
  • Collecting page content and screenshots
  • Operating Windows desktop applications
zhaoxuya520/reverse-skill43.1KUpdated Sep 22, 2026

See all skills by zhaoxuya520

Report a problem with this skill