claw-release

Automate version bumps, tagging, and artifact publishing for ClawSec releases.

1.1k|114|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/prompt-security/clawsec --skill claw-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claw-release
Source: https://github.com/prompt-security/clawsec/tree/main/skills/claw-release
Command: npx skills add https://github.com/prompt-security/clawsec --skill claw-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, gh.

What problem does it solve?

Release management for ClawSec skills and the catalog is complex and error-prone; this skill automates version bumps, tagging, and release verification to ensure consistency across SKILL.md, skill.json, and feed URLs.

Core Features & Use Cases

  • Release automation: bump versions, tag releases, and verify integrity across artifacts.
  • Catalog maintenance: update SKILL.md frontmatter and feed URLs during releases.
  • Quality control: CI-ready checks and automatic artifact generation for GitHub Releases.

Quick Start

Run the release script with the skill name and new version to start the release workflow.

Frequently Asked Questions about claw-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate version bumps and tagging for skill releases?

Automating skill releases handles version bumps, tag creation, and verification across SKILL.md and skill.json files. The workflow enforces checksum generation and artifact publishing to ensure catalog consistency during CI/CD pipelines.

Do I need Git, jq, and gh installed to run release automation workflows?

Yes, Git, jq, and gh are required prerequisites for release automation. Git manages repository state, jq parses skill.json metadata, and gh handles GitHub Release artifact publishing and tag creation commands.

What is the best way to update SKILL.md frontmatter and feed URLs during a release?

Release automation updates SKILL.md frontmatter and feed URLs by applying version bumps directly across catalog files. This ensures metadata stays synchronized with the new release tags and artifact checksums without manual edits.

Can I use CI-ready checks to verify artifact integrity before publishing a GitHub Release?

Yes, CI-ready checks verify artifact integrity before publishing. The release workflow enforces checksum generation and validation steps, ensuring artifacts match expected hashes before GitHub Release publishing completes.

Why does manual release management cause errors in skill catalogs?

Manual release management causes errors because version bumps, tagging, and feed URL updates require synchronized changes across SKILL.md and skill.json. Automation enforces consistent checksum generation and artifact publishing to eliminate human error.

What are the limitations of automating ClawSec skill releases with this workflow?

Release automation is limited to ClawSec skills and catalog structures, requiring specific SKILL.md and skill.json formats. It depends on Git, jq, and gh, meaning environments lacking these tools cannot execute the versioning and tagging workflow.