Procedure

Locate an agent-completion-gate checkout (the engine + scaffolder live in the repo, not in this installed skill — npx skills add ships skills, not the gate engine). If the user doesn't have one, clone it:
```
git clone https://github.com/zhjai/agent-completion-gate
```
From the user's project root, run the scaffolder, pointing it at the project:
```
sh <checkout>/scripts/init.sh --dest .
```
It creates gate/ (engine + empty manifest), control/surface_inventory.yaml, state/, .github/workflows/completion-gate.yml, and a CODEOWNERS example. It is idempotent and will not overwrite existing files (engine or specs) without --force.
Relay the script's "Next" steps to the user verbatim. Then help with step 1 of those (define real surfaces/checks) if asked.

Do not

Do not edit gate/acceptance_manifest.yaml to weaken it, do not move gate//control/ into a worker-writable location, and do not invent your own scaffolding — only run the script.
Do not claim the gate is active/authoritative. It only enforces the state machine until the user (a human) sets the required status check + CODEOWNERS. Say so plainly.
Do not set up anything that lets you (the agent) grant complete. That asymmetry is the whole point: you propose candidate_complete; CI / a human verifies.