Nm Minister Release Health Gates

Standardize release approvals with GitHub-aware checklists and deployment gate validation

This skill appears to do what it says (generate GitHub-aware release checklists and persist gating data), but it references GitHub API calls and a separate 'tracker' for reading/writing release state while declaring no credentials or configuration. Before installing or enabling it: - Ask the author which credentials/integrations the skill expects (e.g., GITHUB_TOKEN, tracker API key) and demand they be explicitly declared in the metadata. - Confirm where 'tracker' lives (self-hosted spreadsheet, issue tracker, project management tool) and what credentials and scopes are required to read/write it. - If you provide credentials, restrict them to the minimum scope (repo read/checks and PR comment/write only if needed). Avoid supplying broad org-level or cloud credentials. - Test the skill in a sandbox repository with minimal privileges and review any sample tracker writes to ensure no unexpected data exfiltration. If the author provides explicit integration details and required env vars that align with the described actions (e.g., a GITHUB_TOKEN limited to the repo, a named tracker endpoint), this assessment could be upgraded to benign. Without that info, the mismatch between declared requirements and the actions instructed is a notable risk.

Type: OpenClaw Skill Name: nm-minister-release-health-gates Version: 1.0.0 The skill bundle provides a framework for managing GitHub release gates and deployment checklists. The instructions in SKILL.md and the modules (deployment-readiness.md, quality-signals.md) focus on standardizing release approvals using GitHub API data and markdown templates. There is no evidence of malicious intent, data exfiltration, or unauthorized execution.