Skip to content
SkillModel-led418 tokens in use

competition-supply-chain

A CTF sandbox workflow for tracing dependency drift, CI steps and release artifacts to the point where provenance diverges.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-supply-chain
git clone https://github.com/zhaoxuya520/reverse-skill.git
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing competition-supply-chain costs

107tokens idle
418tokens in use
578tokens, 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
  • Examples0/15
  • Output7/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 downstream specialization of the ctf-sandbox-orchestrator skill. It covers CTF sandbox challenges about provenance: dependency drift, registry pulls, build and release pipelines, artifact signing and the artifact a runtime consumer ends up using.

The agent walks the chain from source checkout to runtime consumer, compares declared and resolved versions, reconciles build-time and runtime state and reports the earliest point where the chain diverges. Replies are in Simplified Chinese unless English is requested.

What You Get

  • A seven-step provenance chain from source checkout to runtime consumer
  • A comparison approach for declared version, resolved version and shipped artifact
  • A list of high-value evidence: lockfile drift, registry or mirror differences, install scripts and artifact hashes
  • A report format that keeps the evidence as one short chain

Common Use Cases

  • Finding where a dependency in a lab pipeline differs from the checked-in lockfile
  • Comparing a signed artifact hash with the artifact a sandbox runtime loaded
  • Tracing a build step or install script that changes a shipped image

What Makes It Unique

It treats checked-in manifests and live pipeline behavior as different things and asks for proof of runtime consumption, not only lockfile drift. It reports the earliest divergence point, and it runs only after the orchestrator skill has set sandbox assumptions.

Under The Hood

The skill is instruction text only: a SKILL.md, one reference checklist and an agent config file that disables implicit invocation. It ships no scripts and does not itself fetch pages, call APIs, run commands or write files. The agent reads manifests, logs and artifacts in the sandbox with the tools the user provides.

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