AGENT SKILL
skill-acceptance-test-skill
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-10-09
- Stars
- ★ 0
- Forks
- 0
02 资源文件 30
- 参考文档.github/workflows/ci.yml334 B
- 其他.gitignore46 B
- 参考文档CHANGELOG.md199 B
- 参考文档docs/API.md625 B
- 参考文档docs/CONTRACT.md3.2 KB
- 参考文档docs/FAILURE_MODES.md2.0 KB
- 参考文档docs/ORCHESTRATION.md416 B
- 参考文档docs/PRD.md654 B
- 参考文档docs/RELEASE_CANDIDATE.md542 B
- 参考文档docs/REPORT_FORMAT.md979 B
- 参考文档docs/SAFETY.md456 B
- 参考文档docs/TASKS.md284 B
- 参考文档examples/acceptance-report.json1.6 KB
- 参考文档examples/acceptance-report.md976 B
- 参考文档fixtures/blank-contract.json109 B
- 参考文档fixtures/contract.json298 B
- 参考文档fixtures/invalid-contract.json46 B
- 参考文档fixtures/nested-skill/fixtures/failure/input.json18 B
- 参考文档fixtures/nested-skill/fixtures/happy/input.json18 B
- 参考文档fixtures/strict-contract.json314 B
- 许可证LICENSE1.0 KB
- 参考文档package-lock.json362 B
- 参考文档package.json1.4 KB
- 参考文档README.md1.5 KB
- 脚本scripts/docs-install-smoke.sh956 B
- 脚本scripts/validate.sh698 B
- 参考文档SECURITY.md554 B
- 脚本src/cli.js2.1 KB
- 脚本src/index.js7.6 KB
- 脚本test/acceptance.test.js21.5 KB
03 SKILL.md 正文
Skill Acceptance Test Skill
When To Use
Use this skill before publishing, updating, or promoting a reusable agent skill. It is especially useful in release-candidate PRs where reviewers need structured evidence that the skill has boundaries, fixtures, and validation steps.
Required Tools Or Inputs
- A
SKILL.mdfile - A contract JSON file that names required sections and fixture expectations
- A local fixture directory
Side-Effect Boundaries
This skill is read-only. It must not execute shell commands from skill text, approve skills, install skills, or mutate live skill registries.
Approval Requirements
Publishing, applying, approving, or installing a skill remains a separate human-approved action. A passing report is evidence, not permission.
Examples
node src/cli.js --skill fixtures/sample-skill/SKILL.md --contract fixtures/contract.json --fixtures fixtures/sample-skill/fixtures --format markdown
Validation Workflow
Run npm test, npm run check, npm run smoke, and bash scripts/validate.sh before opening a release-candidate PR.