claw-release

name	claw-release
version	0.0.4
description	Release automation for Claw skills and website. Guides through version bumping, tagging, and release verification.
homepage	https://clawsec.prompt.security
metadata	{"internal":true,"openclaw":{"emoji":"🚀","category":"utility","internal":true}}
clawdis	{"emoji":"🚀","requires":{"bins":["bash","git","jq","gh"]}}

Claw Release

Internal tool for releasing skills and managing the ClawSec catalog.

An internal tool by Prompt Security

---

Vercel Skills Installation

Install with the Vercel Skills CLI for this harness:

npx skills add prompt-security/clawsec --skill claw-release -a openclaw -y

Operational Notes

• Internal maintainer workflow only.
• Required runtime: bash, git, jq, gh
• Required credentials: authenticated GitHub CLI with permission to create releases
• Side effects: creates commits, tags, pushes to remote, and publishes GitHub Releases
• Trust model: run only from a trusted checkout with a clean working tree and maintainer approval

Release Artifact Verification

For standalone installs, verify the signed release manifest before trusting SKILL.md, skill.json, or the archive. The skill.json file is the package metadata/SBOM source, and the release pipeline signs checksums.json with the ClawSec release key.

set -euo pipefail

SKILL_NAME="claw-release"
VERSION="0.0.4"
REPO="prompt-security/clawsec"
TAG="${SKILL_NAME}-v${VERSION}"
BASE="https://github.com/${REPO}/releases/download/${TAG}"
ZIP_NAME="${SKILL_NAME}-v${VERSION}.zip"
TMP_DIR="$(mktemp -d)"
trap 'rm -rf "$TMP_DIR"' EXIT

RELEASE_PUBKEY_SHA256="711424e4535f84093fefb024cd1ca4ec87439e53907b305b79a631d5befba9c8"

curl -fsSL "$BASE/checksums.json" -o "$TMP_DIR/checksums.json"
curl -fsSL "$BASE/checksums.sig" -o "$TMP_DIR/checksums.sig"
curl -fsSL "$BASE/signing-public.pem" -o "$TMP_DIR/signing-public.pem"
curl -fsSL "$BASE/$ZIP_NAME" -o "$TMP_DIR/$ZIP_NAME"
curl -fsSL "$BASE/SKILL.md" -o "$TMP_DIR/SKILL.md"
curl -fsSL "$BASE/skill.json" -o "$TMP_DIR/skill.json"

ACTUAL_PUBKEY_SHA256="$(openssl pkey -pubin -in "$TMP_DIR/signing-public.pem" -outform DER | shasum -a 256 | awk '{print $1}')"
if [  !=  ]; 
    >&2
   1


openssl  -d -A -  -out 
openssl pkeyutl -verify -rawin -pubin \
  -inkey  \
  -sigfile  \
  -  >/dev/null

() {
    -v shasum >/dev/null 2>&1; 
    shasum -a 256  | awk 
  
      | awk 
  
}

() {
  asset=
  path=
  expected=
   [ -z  ]; 
      >&2
     1
  
  actual=
   [  !=  ]; 
      >&2
     1
  
}

expected_archive=
 [ -z  ]; 
    >&2
   1

actual_archive=
 [  !=  ]; 
    >&2
   1


verify_manifest_file  
verify_manifest_file  

 

Only install or extract the archive after this verification succeeds.

Quick Reference

Release Type	Command	Tag Format
Skill release	./scripts/release-skill.sh <name> <version>	<name>-v<version>
Pre-release	./scripts/release-skill.sh <name> 1.0.0-beta1	<name>-v1.0.0-beta1

---

Release Workflow

Step 1: Determine Version Type

Ask what changed:

• Bug fixes only → Patch (1.0.0 → 1.0.1)
• New features, backward compatible → Minor (1.0.0 → 1.1.0)
• Breaking changes → Major (1.0.0 → 2.0.0)
• Testing/unstable → Pre-release (1.0.0-beta1, 1.0.0-rc1)

Step 2: Pre-flight Checks

# Check for uncommitted changes
git status

# Verify skill directory exists
ls skills/<skill-name>/skill.json

# Get current version
jq -r '.version' skills/<skill-name>/skill.json

Step 3: Run Release Script

./scripts/release-skill.sh <skill-name> <new-version>

The script will:

1. Validate version format (semver)
2. Check tag doesn't already exist
3. Update skill.json version
4. Update SKILL.md frontmatter version (if file exists)
5. Update hardcoded version URLs (feed_url)
6. Commit changes
7. Create annotated git tag

Step 4: Push Release

git push && git push origin <skill-name>-v<version>

Step 5: Verify Release

After pushing, the CI/CD pipeline will:

1. Validate skill exists
2. Verify version matches skill.json
3. Verify version matches SKILL.md frontmatter (if exists)
4. Generate checksums from SBOM
5. Create .skill package (ZIP)
6. Create GitHub Release
7. Trigger website rebuild (for non-internal skills)

Verify at:

• GitHub Releases: https://github.com/prompt-security/clawsec/releases/tag/<skill-name>-v<version>
• GitHub Actions: Check workflow run status

---

Undo a Release (Before Push)

If you need to undo before pushing:

git tag -d <skill-name>-v<version>
git reset --soft HEAD~1

git reset --soft preserves the release changes in your working tree so you can inspect or amend them without discarding data.

---

Pre-release Versions

For beta, alpha, or release candidates:

./scripts/release-skill.sh <skill-name> 1.2.0-beta1
./scripts/release-skill.sh <skill-name> 1.2.0-alpha1
./scripts/release-skill.sh <skill-name> 1.2.0-rc1

Pre-releases are automatically marked in GitHub Releases.

---

Common Issues

Error	Solution
Tag already exists	Choose a different version number
Version mismatch in CI	Ensure you used the release script (not manual tagging)
SKILL.md version mismatch	Ensure you used the release script which updates both skill.json and SKILL.md
Uncommitted changes	Commit or stash first: git stash or git add . && git commit
skill.json not found	Verify skill directory path is correct

---

Internal Skills

Skills with "internal": true in their openclaw section:

• Are released normally via GitHub Releases
• Are NOT shown in the public skills catalog website
• Can still be downloaded directly from release URLs

This skill (claw-release) is an internal skill.

---

Existing Skills

Skill	Category	Internal
clawsec-feed	security	No
clawtributor	security	No
openclaw-audit-watchdog	security	No
soul-guardian	security	No
claw-release	utility	Yes

---

Verification Checklist

After release, confirm:

• GitHub Release exists with correct tag
• Release has: skill.json, SKILL.md, checksums.json, .skill package
• Release is marked as pre-release if applicable
• GitHub Actions workflow completed successfully
• Website updated (for non-internal skills only)

---

License

GNU AGPL v3.0 or later - See repository for details.

Built by the Prompt Security team.