Release outcome
Skill LionSR/AgenticPublicationProtocol/skills/release-outcome
Perform the lightweight final author review/freeze gate after full APP validation, then either publish a real tagged APP release with manifest or record a developer-sandbox outcome without public compliance records.From its SKILL.md
npx -y skills add LionSR/AgenticPublicationProtocol --skill release-outcomeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 21 stars21 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.
SKILL.md
1.8 KB, as published. Nobody here has run it
Release Outcome
Use this after /validate-publication --stage full. This skill performs final author approval/freeze and then the final outcome.
It is not a second validator. If final review finds a substantive issue, stop and return to prepare-staging, define-paper-agent, or validate-publication.
Lightweight Release Gate
Before any release action:
- Confirm full validation passed, or dev-sandbox blockers are explicitly classified.
- Confirm required final artifacts exist:
publication-staging/supplementary/validation-report.md;publication-staging/supplementary/paper-agent-test.mdfor real publication;publication-staging/LICENSEfor real publication.
- Confirm no files changed since full validation before freezing; if they changed, rerun validation.
- Walk the author through the final staged state in plain language:
- included files/folders;
- excluded files;
- ground truth versus optional context;
- warnings, manual checks, sandbox-only deferrals;
- what becomes public in real mode.
- Record approval:
- approval date;
- approving author names;
- approval statement;
- validation report SHA-256;
- staging tree hash/checksum when available.
- Freeze the tree. After freeze, do not edit without returning to validation.
Final Outcome
Choose exactly one:
- real publication mode: follow
release-real.md; - developer sandbox mode: follow
release-sandbox.md.
Do not mix modes. Dev-sandbox must not create a public repo, APP_PUBLICATION.json, or .publications.md compliance record.