artifact-acceptance
Run a final evidence-backed acceptance gate on a content, research, documentation, sales, or other knowledge artifact against an explicit brief, required evidence, unresolved findings, and format/QA criteria. Use when the user asks whether an artifact is actually ready, complete, publishable as a deliverable, or has passed its defined acceptance contract. Do not use as the final production-release gate for software, to choose among consequential strategic options, to perform the initial review, or to invent acceptance criteria after seeing the result; use release-readiness, ai-council, or the relevant reviewer instead.
Pinned to revision 6626bb65beb0, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/artifact-acceptance/SKILL.md
- skills/artifact-acceptance/CHANGELOG.md
- skills/artifact-acceptance/LICENSE
- skills/artifact-acceptance/README.md
- skills/artifact-acceptance/VERSION
- skills/artifact-acceptance/agents/openai.yaml
- skills/artifact-acceptance/assets/icon.svg
- skills/artifact-acceptance/evals/cases.json
- skills/artifact-acceptance/evals/real-host.json
- skills/artifact-acceptance/references/evaluation.md
- skills/artifact-acceptance/references/gate-model.md
- skills/artifact-acceptance/references/output-contract.md
- skills/artifact-acceptance/references/policy-lock-and-evidence-floor.md
- skills/artifact-acceptance/references/policy-packs-and-waivers.md
- skills/artifact-acceptance/references/traceability.md
- skills/artifact-acceptance/references/untrusted-input.md
- skills/artifact-acceptance/scripts/kernel.py
- skills/artifact-acceptance/scripts/run_evals.py
Every link opens the file at its source, pinned to the revision this page describes.