Claw 发布工具：ClawSec 技能自动化发布与版本管理工具

claw-release by prompt-security/clawsec

102 周安装量

847 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/prompt-security/clawsec --skill claw-release

自动化开发运维版本控制

🇨🇳中文介绍

Claw 发布工具

用于发布技能和管理 ClawSec 目录的内部工具。

由 Prompt Security 开发的内部工具

快速参考

发布类型	命令	标签格式
技能发布	`./scripts/release-skill.sh <name> <version>`	`<name>-v<version>`
预发布	`./scripts/release-skill.sh <name> 1.0.0-beta1`	`<name>-v1.0.0-beta1`

发布工作流程

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

步骤 1：确定版本类型

询问发生了什么变化：

仅修复错误 → 补丁版本 (1.0.0 → 1.0.1)
新增功能，向后兼容 → 次要版本 (1.0.0 → 1.1.0)
破坏性变更 → 主要版本 (1.0.0 → 2.0.0)
测试/不稳定版本 → 预发布版本 (1.0.0-beta1, 1.0.0-rc1)

步骤 2：发布前检查

# 检查是否有未提交的更改
git status

# 验证技能目录是否存在
ls skills/<skill-name>/skill.json

# 获取当前版本
jq -r '.version' skills/<skill-name>/skill.json

步骤 3：运行发布脚本

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

脚本将执行以下操作：

验证版本格式 (semver)
检查标签是否已存在
更新 skill.json 中的版本号
更新 SKILL.md 文件头中的版本号 (如果文件存在)
更新硬编码的版本 URL (feed_url)
提交更改
创建带注释的 git 标签

步骤 4：推送发布

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

步骤 5：验证发布

推送后，CI/CD 流水线将：

验证技能是否存在
验证版本号是否与 skill.json 匹配
验证版本号是否与 SKILL.md 文件头匹配 (如果存在)
根据 SBOM 生成校验和
创建 .skill 包 (ZIP)
创建 GitHub Release
触发网站重建 (仅针对非内部技能)

GitHub Releases: https://github.com/prompt-security/clawsec/releases/tag/<skill-name>-v<version>
GitHub Actions: 检查工作流运行状态

撤销发布 (推送前)

如果需要在推送前撤销：

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

对于 beta、alpha 或候选发布版本：

./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

预发布版本会在 GitHub Releases 中自动标记。

错误	解决方案
`标签已存在`	选择不同的版本号
`CI 中版本不匹配`	确保使用了发布脚本 (而非手动打标签)
`SKILL.md 版本不匹配`	确保使用了发布脚本，它会同时更新 skill.json 和 SKILL.md
`存在未提交的更改`	先提交或暂存：`git stash` 或 `git add . && git commit`
`找不到 skill.json`	验证技能目录路径是否正确

在其 openclaw 部分包含 "internal": true 的技能：

通常通过 GitHub Releases 发布
不会显示在公共技能目录网站上
仍然可以直接从发布 URL 下载

此技能 (claw-release) 是一个内部技能。

技能	类别	内部
clawsec-feed	security	No
clawtributor	security	No
openclaw-audit-watchdog	security	No
soul-guardian	security	No
claw-release	utility	Yes

发布后，请确认：

GitHub Release 存在且标签正确
Release 包含：skill.json、SKILL.md、checksums.json、.skill 包
如果是预发布版本，已正确标记
GitHub Actions 工作流已成功完成
网站已更新 (仅针对非内部技能)

GNU AGPL v3.0 或更高版本 - 详情请参阅仓库。

由 Prompt Security 团队构建。

🇺🇸English

Claw Release

Internal tool for releasing skills and managing the ClawSec catalog.

An internal tool byPrompt 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

# 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:

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

git 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:

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

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`

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.

Weekly Installs

102

Repository

prompt-security/clawsec

GitHub Stars

847

First Seen

Feb 10, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

openclaw97

opencode93

gemini-cli91

kimi-cli90

github-copilot90

codex90