Release Discipline
v1.0.0Enforce release discipline for AI agents and developers. Prevents version spam, forces quality checks before publishing, and maintains a 24-hour cooldown bet...
⭐ 0· 456·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name and description match the instructions: the SKILL enforces pre-release gates (cooldown, feedback, docs, quality, kill criteria, principle checks) and logs outcomes. The requested actions (reading README/CHANGELOG/SOUL.md, summarizing feedback, writing a release-log) are appropriate for a release-discipline tool. One minor mismatch: the checklist asks the agent to check external signals (GitHub issues, npm downloads, ClawHub installs, user messages) but the skill declares no credentials or APIs—this may be because it expects the platform/agent to already provide access.
Instruction Scope
The SKILL.md stays within release-related scope (project files, user feedback, logging). However the instructions are high-level and leave implementation details to the agent (e.g., how to 'check GitHub issues' or 'summarize user messages'), which grants broad discretion. It also instructs 'Intercept any release/publish/deploy action'—as an instruction for the agent this is fine, but there is no concrete trigger mechanism described.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest-risk installation surface (nothing written to disk by an installer).
Credentials
The skill declares no required environment variables or credentials, which is consistent with being instruction-only. That said, it expects access to external signals (GitHub, npm, ClawHub, user messages) that in practice may require tokens or platform permissions; the skill does not request or document these, so you should confirm how the agent will obtain that access before enabling automatic enforcement.
Persistence & Privilege
always:false (no forced inclusion). The skill asks to write to memory/release-log.md — writing its own log is reasonable and scoped to the skill. It does not request changes to other skills or system-wide config.
Assessment
This instruction-only skill is coherent with its stated goal of gating releases and logging outcomes. Before installing or enabling autonomous enforcement, check: 1) how the agent will access external signals (GitHub issues, npm download counts, 'ClawHub installs', and user messages) — do you need to provide tokens or grant platform permissions? 2) where memory/release-log.md is stored and who can read it (sensitive info could end up in logs); and 3) whether you want the agent to 'intercept' release actions automatically or only run the checklist when explicitly invoked. If you want stricter assurances, request the author to document required API scopes, exact triggers, and the storage location/retention policy for the release log.Like a lobster shell, security has layers — review code before you run it.
latestvk970hxc3332cjp5gtydfndq769817cqf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.