Security compliance gate

Use when deciding security or compliance gates before merge, release, publication, or handoff.From its SKILL.md

Install

npx -y skills add jukrap/ai-agent-playbook --skill security-compliance-gate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

1.2 KB, 214 tokens by cl100k_base, as published. Nobody here has run it

Use this as the primary security skill for deciding whether a change can proceed through a merge, release, publication, or handoff gate.

Identify the artifact, audience, environment, data scope, trust boundary, and required policy or compliance evidence.
Route implementation-specific questions to security-review, auth-access-control, dependency-supply-chain-review, or license-notice-review instead of duplicating their checks.
Classify findings as block, warn, or document, and record the owner, expiry, compensating evidence, and verification path for any accepted risk.
Verify public-doc hygiene, translation or notice coverage, runtime evidence safety, and required local scanner or repository-defined check output before calling the gate passed.

Read references/gate-severity-model.md before recording block, warn, document, or accepted-risk outcomes.

Read references/evidence-routing.md when connecting security, dependency, license, runtime schema, locator, or public documentation checks.

5.5 KB alongside SKILL.md