Checks release readiness by verifying artifacts, tests, docs, approval, risks, and evidence before publishing tags, packages, or deployment notes.
Security Analysis
high confidenceThis is a benign instruction-only release checklist, with minor notes to verify the package identity/version and any optional AANA checker before sharing release details.
The stated purpose is release-readiness review, and the artifacts consistently provide checklist-style instructions for verifying tests, docs, artifacts, approval, and rollback before release.
The instructions are safety-gating rather than action-taking: they require evidence, approval, review for higher-risk releases, and blocking unsupported or misleading releases.
There is no install spec and no bundled code, but the registry slug/version differ from the manifest/README values, so users should verify they are installing the intended package.
No credentials, commands, files, or environment access are requested. The only data-flow note is an optional configured AANA checker, which is explicitly limited to a minimal redacted payload.
The artifacts declare no persistence, no memory storage, no file writes, no command execution, and no privileged access.
Guidance
This skill appears safe to install as an instruction-only release gate. Before using it, verify the package name/version mismatch is expected, and if you connect an AANA checker, share only the redacted fields listed in the skill.
Latest Release
v1.0.0
Initial release of the AANA Release Readiness Check Skill. - Provides detailed pre-release readiness guidelines for OpenClaw-style agents. - Defines required checks for artifacts, tests, documentation, security, and approval. - Outlines evidence and artifact/version consistency rules. - Specifies higher-risk release situations and associated requirements. - Introduces a standardized minimal review payload format. - Details decision rules and a structured release gate output pattern.
More by @mindbomber
Published by @mindbomber on ClawHub
