What is claw-release?

Perfeito para Agentes de Desenvolvedor que necessitam de fluxos de trabalho de lançamento de habilidades e gerenciamento de catálogo otimizados. Release automation for Claw skills and website. Guides through version bumping, tagging, and release verification.

How do I install claw-release?

Run the command: npx killer-skills add CoralShades/CurryDash-Central-Hub/claw-release. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for claw-release?

Key use cases include: Automatizar lançamentos de habilidades com controle de versão, Gerenciar o catálogo ClawSec com marcação de pré-lançamento, Otimizar fluxos de trabalho de lançamento para desenvolvedores e equipes de segurança.

Which IDEs are compatible with claw-release?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for claw-release?

Requer ambiente de execução de script de shell. Limitado ao gerenciamento do catálogo ClawSec. Versionamento segue formato de marcação específico como -v .

claw-release

Install claw-release, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md

Readonly

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Supporting Evidence

Claw Release

Name: claw-release
Availability: InStock
Author: CoralShades

Internal tool for releasing skills and managing the ClawSec catalog.

An internal tool by Prompt Security

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

bash
1# Check for uncommitted changes
2git status
3
4# Verify skill directory exists
5ls skills/<skill-name>/skill.json
6
7# Get current version
8jq -r '.version' skills/<skill-name>/skill.json

Step 3: Run Release Script

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

The script will:

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

Step 4: Push Release

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

Step 5: Verify Release

After pushing, the CI/CD pipeline will:

Validate skill exists
Verify version matches skill.json
Verify version matches SKILL.md frontmatter (if exists)
Generate checksums from SBOM
Create .skill package (ZIP)
Create GitHub Release
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:

bash
1git reset --hard HEAD~1 && git tag -d <skill-name>-v<version>

Pre-release Versions

For beta, alpha, or release candidates:

bash
1./scripts/release-skill.sh <skill-name> 1.2.0-beta1
2./scripts/release-skill.sh <skill-name> 1.2.0-alpha1
3./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.

claw-release — community claw-release, CurryDash-Central-Hub, community, ide skills

Sobre este Skill

Killer-Skills Review

Por que usar essa habilidade

Melhor para

↓ Casos de Uso Práticos for claw-release

! Segurança e Limitações

Why this page is reference-only

Source Boundary

Decide The Next Action Before You Keep Reading Repository Material

Start With Installation And Validation

Cross-Check Against Trusted Picks

Move To Workflow Collections For Team Rollout

Browser Sandbox Environment

⚡️ Ready to unleash?

FAQ & Installation Steps

? Frequently Asked Questions