Skip to content
alyn
glebis

Cull Release Verify skill

Use when verifying or auditing a Cull release, DMG, updater archive, notarization, Homebrew cask, installed version, launch health, or post-publication distribution state.

$npx skills add glebis/claude-skills --skill cull-release-verify
View this skill on GitHubglebis/claude-skills/cull-release-verify/SKILL.md
Pack stars
413
Pack installs
15k
Alyn Score
52/99
Updated
8 h ago
License
MIT
– views – installs via Alyn

Install Cull Release Verify

Pick your agent. Every command is ready to paste.

$npx skills add glebis/claude-skills --skill cull-release-verify

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads cull-release-verify when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the cull-release-verify skill”. In Codex, type $cull-release-verify.

The skill itself

SKILL.md

FolderGitHub

Cull Release Verify

Principle

Reconstruct release truth from immutable public evidence. Verification is read-only by default.

Verify

  1. Resolve the Cull checkout and select the explicit version or latest public release.
  2. Run npm run release:cull -- state show --version "$VERSION" --json and parse exactly one JSON envelope.
  3. Bind the annotated Git tag object and peeled commit to the published release, authenticated workflow run, provenance, and required asset inventory.
  4. Download artifacts to an isolated temporary directory. Run Cull's exact artifact verifier; check updater signature, SHA-256 checksums, DMG contents, embedded version and architecture, codesign, Gatekeeper, and notarization staple. The verifier requires exactly the 4 signed assets in --artifact-dir — checksums.txt and release-provenance.json are verifier outputs, not inputs; remove them before running.
  5. Compare Homebrew version and SHA-256 with public provenance and require its promotion evidence.
  6. Report version, commit, tag object, workflow, asset hashes, release URL, tap commit, installed-version evidence, launch evidence, and mismatches.

Default to no installation. When the user explicitly requests an install smoke, use an isolated location and preserve any existing app. Never edit release state, the GitHub release, tags, the tap, system Applications, or cull.db.

Tips for Cull Release Verify

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Cull Release Verify

What does the Cull Release Verify skill do?

Use when verifying or auditing a Cull release, DMG, updater archive, notarization, Homebrew cask, installed version, launch health, or post-publication distribution state.

How do I install Cull Release Verify?

Run "npx skills add glebis/claude-skills --skill cull-release-verify" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Cull Release Verify work in Cursor and Codex?

Yes. Cull Release Verify uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Cull Release Verify free?

Cull Release Verify is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.

Who made Cull Release Verify?

Cull Release Verify is published by glebis in the glebis/claude-skills repository, together with 29 other skills.

Similar skills. From other creators.