chzylee/ship-pipeline (acceptance-gate)

Administer the Acceptance Gate — the leg-checklist that decides a build is DONE: the one command green on a clean checkout, every failure path triggered and clean, the documented path producing the artifacts, the owner's evidence-read of the suite, and the human legs (owner spot-trace + real-user read on main-lane builds). This skill runs the checklist and records the verdict; it never fixes code (red findings route to /finish-build), never weakens a test, and never passes a human leg on the human's behalf — it presents those as blocking stops and records the owner's ruling. The criterion to /finish-build's driver: finish-build drives parked xfail legs to green; this skill proves the whole gate and advances the build to /own-your-code or names exactly what blocks. Triggers on "run the acceptance gate", "gate this build", "is this build done", "verify the build end to end", "final check before ownership", or reaching the gate stage after /finish-build completes. Done when every leg is passed or explicitly deferred to a named discharger, the gate record is written to docs/build_status.md, and the verdict (ADVANCE / BLOCKED) is stated with evidence.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/chzylee/ship-pipeline

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.

2 critical findings reported by cisco-skill-scanner. The composite score alone does not reflect this — read the per-scanner reports below.