{"id":"d2ec8b8e-4fa8-4cf3-93cc-8f5aff33300f","entityType":"agent","slug":"clawhub-weapon3k-github-release-workflow","name":"GitHub Release Workflow","canonicalUrl":"https://www.xpersona.co/agent/clawhub-weapon3k-github-release-workflow","canonicalPath":"/agent/clawhub-weapon3k-github-release-workflow","generatedAt":"2026-10-11T17:41:10.385Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T14:58:59.673Z","emptyReason":null},"description":"Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) updating... Skill: GitHub Release Workflow Owner: weapon3k Summary: Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) updating... Tags: git:1.0.0, github:1.0.0, latest:1.1.0, release:1.0.0, workflow:1.0.0 Version history: v1.1.0 | 2026-02-22T07:14:46.155Z | user Add README update requirement for releases v1.0.0 | 2026-02-21T17:02:5","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17271j5cae09sx67cb1fya3vh885sfv:github-release-workflow","sourceUrl":"https://clawhub.ai/weapon3k/github-release-workflow","homepage":"https://clawhub.ai/weapon3k/skills/github-release-workflow","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/weapon3k/github-release-workflow","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/weapon3k/skills/github-release-workflow","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) updating..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T14:58:59.673Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T14:58:59.673Z","emptyReason":null},"stars":null,"forks":null,"downloads":1045,"packageName":null,"latestVersion":"1.1.0","tractionLabel":"1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T14:58:59.660Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T14:58:59.673Z","lastCrawledAt":"2026-10-11T14:58:59.660Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T14:58:59.660Z","lastVerifiedAt":null,"highlights":[{"version":"1.1.0","createdAt":"2026-02-22T07:14:46.155Z","changelog":"Add README update requirement for releases","fileCount":6,"zipByteSize":6227},{"version":"1.0.0","createdAt":"2026-02-21T17:02:56.110Z","changelog":"- Initial release of github-release-workflow skill. - Provides a standardized process for GitHub releases, including tagging, committing, and changelog updates. - Documents conventional commits, branch strategy, and semantic versioning. - Quick command examples for full release flow and GitHub CLI usage. - References to detailed specifications and best practice resources included.","fileCount":6,"zipByteSize":5908}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17271j5cae09sx67cb1fya3vh885sfv:github-release-workflow","setupComplexity":"medium","setupSteps":["Python environment detected. Create a strict virtual environment (`python -m venv .venv`) before installing dependencies to prevent system-level package conflicts.","Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T17:41:10.385Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-weapon3k-github-release-workflow/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T14:58:59.673Z","emptyReason":null},"readme":"Skill: GitHub Release Workflow\n\nOwner: weapon3k\n\nSummary: Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) updating...\n\nTags: git:1.0.0, github:1.0.0, latest:1.1.0, release:1.0.0, workflow:1.0.0\n\nVersion history:\n\nv1.1.0 | 2026-02-22T07:14:46.155Z | user\n\nAdd README update requirement for releases\n\nv1.0.0 | 2026-02-21T17:02:56.110Z | auto\n\n- Initial release of github-release-workflow skill.\n- Provides a standardized process for GitHub releases, including tagging, committing, and changelog updates.\n- Documents conventional commits, branch strategy, and semantic versioning.\n- Quick command examples for full release flow and GitHub CLI usage.\n- References to detailed specifications and best practice resources included.\n\nArchive index:\n\nArchive v1.1.0: 6 files, 6227 bytes\n\nFiles: _meta.json (142b), pyproject.toml (847b), README.md (1926b), release.py (2238b), SKILL.md (2589b), SPEC.md (4493b)\n\nFile v1.1.0:SKILL.md\n\n---\nname: github-release-workflow\ndescription: \"Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) updating README and docs, (5) setting up CI/CD for releases.\"\nmetadata:\n  {\n    openclaw: { emoji: \"🚀\" },\n  }\n---\n\n# GitHub Release Workflow Skill\n\nA standardized workflow for professional GitHub releases.\n\n**IMPORTANT: Always update README.md and documentation before releasing!**\n\n## Prerequisites\n\n- Git installed\n- GitHub CLI (`gh`) authenticated\n- Git repository initialized\n\n## Quick Commands\n\n### Full Release Flow\n\n```bash\n# 1. Ensure clean working tree\ngit status\n\n# 2. Run tests and format\npip install -e \".[dev]\"\npytest\nblack lib/ tests/\n\n# 3. Update version in pyproject.toml\n# Edit: version = \"2.1.0\"\n\n# 4. Update CHANGELOG.md\n# Add new section with today's date\n\n# 5. Update README.md (IMPORTANT!)\n# - Update version badge\n# - Update features list\n# - Update project structure if changed\n# - Update roadmap table\n\n# 6. Update other docs as needed\n# - docs/*.md\n# - API documentation\n# - Examples\n\n# 7. Stage and commit\ngit add .\ngit commit -m \"release: v2.1.0 - Description\"\n\n# 8. Create tag\ngit tag -a v2.1.0 -m \"Version 2.1.0\"\n\n# 9. Push\ngit push\ngit push origin v2.1.0\n```\n\n### README Update Checklist\n\nWhen releasing a new version, always update README.md:\n\n| Item | Description |\n|------|-------------|\n| Version badge | Update `version-x.x.x-blue` |\n| Features list | Add new features, remove deprecated |\n| Project structure | Reflect new files/directories |\n| Installation | Update if deps changed |\n| Usage | Add new examples if needed |\n| Roadmap | Move current version to done, add next |\n| API docs | Update if API changed |\n\n### Conventional Commits Format\n\n```\n<type>(<scope>): <description>\n\nTypes: feat, fix, docs, style, refactor, test, chore, release\n```\n\nExamples:\n- `feat(memory): add SQLite support`\n- `fix(vitality): correct energy calculation`\n- `docs: update README`\n\n### Version Format\n\n```\nMAJOR.MINOR.PATCH\n- MAJOR: Breaking changes\n- MINOR: New features (backward compatible)\n- PATCH: Bug fixes\n```\n\n## Branch Strategy\n\n```\nmain (stable)\n  ↑\ndevelop (integration)\n  ↑\nfeature/* (new features)\n```\n\n## GitHub Release (Optional)\n\n```bash\ngh release create v2.1.0 \\\n  --title \"Version 2.1.0\" \\\n  --notes \"Release notes\"\n```\n\n## See Also\n\n- Full specification: `github-release-workflow/SPEC.md`\n- Keep a Changelog: https://keepachangelog.com/\n- Semantic Versioning: https://semver.org/\n- Conventional Commits: https://www.conventionalcommits.org/\n\nFile v1.1.0:README.md\n\n# GitHub Release Workflow\n\n<p align=\"center\">\n  <img src=\"https://img.shields.io/badge/version-1.0.0-blue\" alt=\"Version\">\n  <img src=\"https://img.shields.io/badge/python-3.10+-green\" alt=\"Python\">\n  <img src=\"https://img.shields.io/badge/license-MIT-orange\" alt=\"License\">\n</p>\n\n> A standardized workflow for professional GitHub releases.\n\n## Overview\n\nThis project provides a complete specification and CLI tool for professional GitHub releases, following industry best practices:\n\n- **Conventional Commits** — Clear commit message format\n- **Semantic Versioning** — Standard version numbers\n- **Keep a Changelog** — Structured changelog\n- **GitHub Releases** — Tagged releases with notes\n\n## Installation\n\n```bash\ngit clone https://github.com/weapon3k/github-release-workflow.git\ncd github-release-workflow\npip install -e .\n```\n\n## Quick Start\n\n```bash\n# Initialize git (first time)\ngh-release init\n\n# Create a release\ngh-release release v1.0.0\n\n# Check status\ngh-release status\n\n# View log\ngh-release log -n 10\n```\n\n## Workflow\n\n### 1. Prepare\n\n```bash\n# Ensure clean working tree\ngit status\npytest\nblack .\n```\n\n### 2. Update\n\n- Update version in `pyproject.toml`\n- Add entry to `CHANGELOG.md`\n\n### 3. Release\n\n```bash\ngit add .\ngit commit -m \"release: v1.0.0\"\ngit tag -a v1.0.0 -m \"Version 1.0.0\"\ngit push\ngit push origin v1.0.0\n```\n\n## Commit Format\n\n```\n<type>(<scope>): <description>\n\nTypes: feat, fix, docs, style, refactor, test, chore, release\n```\n\n## Version Format\n\n```\nMAJOR.MINOR.PATCH\n```\n\n- **MAJOR**: Breaking changes\n- **MINOR**: New features (backward compatible)\n- **PATCH**: Bug fixes\n\n## Files\n\n- `SPEC.md` — Full specification\n- `SKILL.md` — OpenClaw skill definition\n- `release.py` — CLI tool\n\n## See Also\n\n- [Conventional Commits](https://www.conventionalcommits.org/)\n- [Semantic Versioning](https://semver.org/)\n- [Keep a Changelog](https://keepachangelog.com/)\n\n---\n\n**License**: MIT\n\nFile v1.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn71685jv7z3r8kfqpg450k4dd81kkd8\",\n  \"slug\": \"github-release-workflow\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1771744486155\n}\n\nFile v1.1.0:SPEC.md\n\n# GitHub Release Workflow Specification\n\n> A standardized workflow for professional GitHub releases.\n\n## Overview\n\nThis specification defines a professional release workflow for Python projects, inspired by industry best practices.\n\n## Prerequisites\n\n- Git installed\n- GitHub CLI (`gh`) authenticated\n- Python 3.10+\n- Git repository initialized\n\n## Release Workflow\n\n### 1. Pre-Release Checklist\n\n```bash\n# Ensure clean working tree\ngit status\n\n# Update dependencies\npip install -e \".[dev]\"\n\n# Run tests\npytest\n\n# Format code\nblack lib/ tests/\n\n# Type checking (optional)\nmypy lib/\n```\n\n### 2. Update Version\n\nUpdate version in:\n- `pyproject.toml` → `version`\n- `CHANGELOG.md` → Add new version header\n\n```bash\n# Example: bump to 2.1.0\n# Edit pyproject.toml: version = \"2.1.0\"\n```\n\n### 3. Update Changelog\n\nAdd new section in `CHANGELOG.md`:\n\n```markdown\n## [2.1.0] - YYYY-MM-DD\n\n### Added\n- New feature 1\n- New feature 2\n\n### Changed\n- Improvement 1\n\n### Fixed\n- Bug fix 1\n\n### Removed\n- Deprecated feature 1\n```\n\n### 4. Stage Changes\n\n```bash\ngit add .\ngit status\n```\n\n### 5. Commit\n\nFollow [Conventional Commits](https://www.conventionalcommits.org/):\n\n```bash\ngit commit -m \"release: v2.1.0 - Added new features and improvements\"\n```\n\n### 6. Create Tag\n\n```bash\ngit tag -a v2.1.0 -m \"Version 2.1.0: Release description\"\n```\n\n### 7. Push\n\n```bash\ngit push\ngit push origin v2.1.0\n```\n\n### 8. Create GitHub Release (Optional)\n\n```bash\ngh release create v2.1.0 \\\n  --title \"Version 2.1.0\" \\\n  --notes \"Release notes from CHANGELOG.md\"\n```\n\n## Branch Strategy\n\n```\nmain (stable)\n  ↑\ndevelop (integration)\n  ↑\nfeature/* (new features)\n  ↑\nhotfix/* (urgent fixes)\n```\n\n### Branch Types\n\n| Branch | Purpose | Base | Merge To |\n|--------|---------|------|----------|\n| `main` | Stable releases | - | - |\n| `develop` | Integration | main | main |\n| `feature/*` | New features | develop | develop |\n| `hotfix/*` | Urgent fixes | main | main, develop |\n| `release/*` | Release prep | develop | main, develop |\n\n## Versioning\n\nFollow [Semantic Versioning](https://semver.org/):\n\n```\nMAJOR.MINOR.PATCH\n  │    │    │\n  │    │    └── Bug fixes\n  │    └─────── New features (backward compatible)\n  └─────────── Breaking changes\n```\n\n### Version Format\n\n- **Release**: `v2.1.0` (annotated tag)\n- **Pre-release**: `v2.1.0-alpha.1`, `v2.1.0-beta.1`\n- **Build**: `v2.1.0+build.123`\n\n## Commit Message Format\n\n### Conventional Commits\n\n```\n<type>(<scope>): <description>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n### Types\n\n| Type | Description |\n|------|-------------|\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `docs` | Documentation |\n| `style` | Formatting |\n| `refactor` | Code restructuring |\n| `test` | Tests |\n| `chore` | Maintenance |\n| `release` | Version release |\n\n### Examples\n\n```bash\ngit commit -m \"feat(memory): add SQLite storage support\"\ngit commit -m \"fix(vitality): correct energy decay calculation\"\ngit commit -m \"docs: update README with examples\"\ngit commit -m \"release: v2.1.0\"\n```\n\n## CI/CD Integration (Optional)\n\n### GitHub Actions Example\n\n```yaml\n# .github/workflows/release.yml\nname: Release\n\non:\n  push:\n    tags:\n      - 'v*'\n\njobs:\n  release:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions/checkout@v4\n      - uses: actions/setup-python@v5\n        with:\n          python-version: '3.10'\n      - run: pip install -e \".[dev]\"\n      - run: pytest\n      - run: pip install build\n      - run: python -m build\n      - uses: softprops/action-gh-release@v1\n        with:\n          files: dist/*\n        env:\n          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n```\n\n## Quick Reference\n\n```bash\n# Full release flow\ngit checkout develop\ngit pull origin develop\n# Make changes...\ngit add .\ngit commit -m \"feat: new feature\"\ngit checkout main\ngit merge develop\ngit tag -a v2.1.0 -m \"Version 2.1.0\"\ngit push origin main --follow-tags\n\n# Hotfix flow\ngit checkout main\ngit checkout -b hotfix/fix-description\n# Fix...\ngit commit -m \"fix: description\"\ngit checkout main\ngit merge hotfix/fix-description\ngit tag -a v2.1.1 -m \"Version 2.1.1\"\ngit push origin main --follow-tags\ngit branch -d hotfix/fix-description\n```\n\n## Related Standards\n\n- [Conventional Commits](https://www.conventionalcommits.org/)\n- [Semantic Versioning](https://semver.org/)\n- [Keep a Changelog](https://keepachangelog.com/)\n- [GitHub Flow](https://docs.github.com/en/get-started/quickstart/github-flow)\n\n---\n\n_Last updated: 2026-02-22_\n\nFile v1.1.0:pyproject.toml\n\n[build-system]\nrequires = [\"setuptools>=61.0\"]\nbuild-backend = \"setuptools.build_meta\"\n\n[project]\nname = \"github-release-workflow\"\nversion = \"1.1.0\"\ndescription = \"Professional GitHub release workflow specification\"\nreadme = \"README.md\"\nlicense = {text = \"MIT\"}\nauthors = [\n    {name = \"Steven\", email = \"steven@example.com\"}\n]\nkeywords = [\"git\", \"github\", \"release\", \"workflow\", \"cicd\", \"conventional-commits\"]\nclassifiers = [\n    \"Development Status :: 4 - Beta\",\n    \"Intended Audience :: Developers\",\n    \"License :: OSI Approved :: MIT License\",\n    \"Programming Language :: Python :: 3\",\n    \"Programming Language :: Python :: 3.10\",\n    \"Programming Language :: Python :: 3.11\",\n    \"Programming Language :: Python :: 3.12\",\n]\n\ndependencies = []\n\n[project.scripts]\ngh-release = \"release:main\"\n\n[tool.setuptools.packages.find]\nwhere = [\".\"]\n\nArchive v1.0.0: 6 files, 5908 bytes\n\nFiles: pyproject.toml (847b), README.md (1926b), release.py (2238b), SKILL.md (1788b), SPEC.md (4493b), _meta.json (142b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: github-release-workflow\ndescription: \"Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) setting up CI/CD for releases.\"\nmetadata:\n  {\n    openclaw: { emoji: \"🚀\" },\n  }\n---\n\n# GitHub Release Workflow Skill\n\nA standardized workflow for professional GitHub releases.\n\n## Prerequisites\n\n- Git installed\n- GitHub CLI (`gh`) authenticated\n- Git repository initialized\n\n## Quick Commands\n\n### Full Release Flow\n\n```bash\n# 1. Ensure clean working tree\ngit status\n\n# 2. Run tests and format\npip install -e \".[dev]\"\npytest\nblack lib/ tests/\n\n# 3. Update version in pyproject.toml\n# Edit: version = \"2.1.0\"\n\n# 4. Update CHANGELOG.md\n# Add new section with today's date\n\n# 5. Stage and commit\ngit add .\ngit commit -m \"release: v2.1.0 - Description\"\n\n# 6. Create tag\ngit tag -a v2.1.0 -m \"Version 2.1.0\"\n\n# 7. Push\ngit push\ngit push origin v2.1.0\n```\n\n### Conventional Commits Format\n\n```\n<type>(<scope>): <description>\n\nTypes: feat, fix, docs, style, refactor, test, chore, release\n```\n\nExamples:\n- `feat(memory): add SQLite support`\n- `fix(vitality): correct energy calculation`\n- `docs: update README`\n\n### Version Format\n\n```\nMAJOR.MINOR.PATCH\n- MAJOR: Breaking changes\n- MINOR: New features (backward compatible)\n- PATCH: Bug fixes\n```\n\n## Branch Strategy\n\n```\nmain (stable)\n  ↑\ndevelop (integration)\n  ↑\nfeature/* (new features)\n```\n\n## GitHub Release (Optional)\n\n```bash\ngh release create v2.1.0 \\\n  --title \"Version 2.1.0\" \\\n  --notes \"Release notes\"\n```\n\n## See Also\n\n- Full specification: `github-release-workflow/SPEC.md`\n- Keep a Changelog: https://keepachangelog.com/\n- Semantic Versioning: https://semver.org/\n- Conventional Commits: https://www.conventionalcommits.org/\n\nFile v1.0.0:README.md\n\n# GitHub Release Workflow\n\n<p align=\"center\">\n  <img src=\"https://img.shields.io/badge/version-1.0.0-blue\" alt=\"Version\">\n  <img src=\"https://img.shields.io/badge/python-3.10+-green\" alt=\"Python\">\n  <img src=\"https://img.shields.io/badge/license-MIT-orange\" alt=\"License\">\n</p>\n\n> A standardized workflow for professional GitHub releases.\n\n## Overview\n\nThis project provides a complete specification and CLI tool for professional GitHub releases, following industry best practices:\n\n- **Conventional Commits** — Clear commit message format\n- **Semantic Versioning** — Standard version numbers\n- **Keep a Changelog** — Structured changelog\n- **GitHub Releases** — Tagged releases with notes\n\n## Installation\n\n```bash\ngit clone https://github.com/weapon3k/github-release-workflow.git\ncd github-release-workflow\npip install -e .\n```\n\n## Quick Start\n\n```bash\n# Initialize git (first time)\ngh-release init\n\n# Create a release\ngh-release release v1.0.0\n\n# Check status\ngh-release status\n\n# View log\ngh-release log -n 10\n```\n\n## Workflow\n\n### 1. Prepare\n\n```bash\n# Ensure clean working tree\ngit status\npytest\nblack .\n```\n\n### 2. Update\n\n- Update version in `pyproject.toml`\n- Add entry to `CHANGELOG.md`\n\n### 3. Release\n\n```bash\ngit add .\ngit commit -m \"release: v1.0.0\"\ngit tag -a v1.0.0 -m \"Version 1.0.0\"\ngit push\ngit push origin v1.0.0\n```\n\n## Commit Format\n\n```\n<type>(<scope>): <description>\n\nTypes: feat, fix, docs, style, refactor, test, chore, release\n```\n\n## Version Format\n\n```\nMAJOR.MINOR.PATCH\n```\n\n- **MAJOR**: Breaking changes\n- **MINOR**: New features (backward compatible)\n- **PATCH**: Bug fixes\n\n## Files\n\n- `SPEC.md` — Full specification\n- `SKILL.md` — OpenClaw skill definition\n- `release.py` — CLI tool\n\n## See Also\n\n- [Conventional Commits](https://www.conventionalcommits.org/)\n- [Semantic Versioning](https://semver.org/)\n- [Keep a Changelog](https://keepachangelog.com/)\n\n---\n\n**License**: MIT\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn71685jv7z3r8kfqpg450k4dd81kkd8\",\n  \"slug\": \"github-release-workflow\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1771693376110\n}\n\nFile v1.0.0:SPEC.md\n\n# GitHub Release Workflow Specification\n\n> A standardized workflow for professional GitHub releases.\n\n## Overview\n\nThis specification defines a professional release workflow for Python projects, inspired by industry best practices.\n\n## Prerequisites\n\n- Git installed\n- GitHub CLI (`gh`) authenticated\n- Python 3.10+\n- Git repository initialized\n\n## Release Workflow\n\n### 1. Pre-Release Checklist\n\n```bash\n# Ensure clean working tree\ngit status\n\n# Update dependencies\npip install -e \".[dev]\"\n\n# Run tests\npytest\n\n# Format code\nblack lib/ tests/\n\n# Type checking (optional)\nmypy lib/\n```\n\n### 2. Update Version\n\nUpdate version in:\n- `pyproject.toml` → `version`\n- `CHANGELOG.md` → Add new version header\n\n```bash\n# Example: bump to 2.1.0\n# Edit pyproject.toml: version = \"2.1.0\"\n```\n\n### 3. Update Changelog\n\nAdd new section in `CHANGELOG.md`:\n\n```markdown\n## [2.1.0] - YYYY-MM-DD\n\n### Added\n- New feature 1\n- New feature 2\n\n### Changed\n- Improvement 1\n\n### Fixed\n- Bug fix 1\n\n### Removed\n- Deprecated feature 1\n```\n\n### 4. Stage Changes\n\n```bash\ngit add .\ngit status\n```\n\n### 5. Commit\n\nFollow [Conventional Commits](https://www.conventionalcommits.org/):\n\n```bash\ngit commit -m \"release: v2.1.0 - Added new features and improvements\"\n```\n\n### 6. Create Tag\n\n```bash\ngit tag -a v2.1.0 -m \"Version 2.1.0: Release description\"\n```\n\n### 7. Push\n\n```bash\ngit push\ngit push origin v2.1.0\n```\n\n### 8. Create GitHub Release (Optional)\n\n```bash\ngh release create v2.1.0 \\\n  --title \"Version 2.1.0\" \\\n  --notes \"Release notes from CHANGELOG.md\"\n```\n\n## Branch Strategy\n\n```\nmain (stable)\n  ↑\ndevelop (integration)\n  ↑\nfeature/* (new features)\n  ↑\nhotfix/* (urgent fixes)\n```\n\n### Branch Types\n\n| Branch | Purpose | Base | Merge To |\n|--------|---------|------|----------|\n| `main` | Stable releases | - | - |\n| `develop` | Integration | main | main |\n| `feature/*` | New features | develop | develop |\n| `hotfix/*` | Urgent fixes | main | main, develop |\n| `release/*` | Release prep | develop | main, develop |\n\n## Versioning\n\nFollow [Semantic Versioning](https://semver.org/):\n\n```\nMAJOR.MINOR.PATCH\n  │    │    │\n  │    │    └── Bug fixes\n  │    └─────── New features (backward compatible)\n  └─────────── Breaking changes\n```\n\n### Version Format\n\n- **Release**: `v2.1.0` (annotated tag)\n- **Pre-release**: `v2.1.0-alpha.1`, `v2.1.0-beta.1`\n- **Build**: `v2.1.0+build.123`\n\n## Commit Message Format\n\n### Conventional Commits\n\n```\n<type>(<scope>): <description>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n### Types\n\n| Type | Description |\n|------|-------------|\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `docs` | Documentation |\n| `style` | Formatting |\n| `refactor` | Code restructuring |\n| `test` | Tests |\n| `chore` | Maintenance |\n| `release` | Version release |\n\n### Examples\n\n```bash\ngit commit -m \"feat(memory): add SQLite storage support\"\ngit commit -m \"fix(vitality): correct energy decay calculation\"\ngit commit -m \"docs: update README with examples\"\ngit commit -m \"release: v2.1.0\"\n```\n\n## CI/CD Integration (Optional)\n\n### GitHub Actions Example\n\n```yaml\n# .github/workflows/release.yml\nname: Release\n\non:\n  push:\n    tags:\n      - 'v*'\n\njobs:\n  release:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions/checkout@v4\n      - uses: actions/setup-python@v5\n        with:\n          python-version: '3.10'\n      - run: pip install -e \".[dev]\"\n      - run: pytest\n      - run: pip install build\n      - run: python -m build\n      - uses: softprops/action-gh-release@v1\n        with:\n          files: dist/*\n        env:\n          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n```\n\n## Quick Reference\n\n```bash\n# Full release flow\ngit checkout develop\ngit pull origin develop\n# Make changes...\ngit add .\ngit commit -m \"feat: new feature\"\ngit checkout main\ngit merge develop\ngit tag -a v2.1.0 -m \"Version 2.1.0\"\ngit push origin main --follow-tags\n\n# Hotfix flow\ngit checkout main\ngit checkout -b hotfix/fix-description\n# Fix...\ngit commit -m \"fix: description\"\ngit checkout main\ngit merge hotfix/fix-description\ngit tag -a v2.1.1 -m \"Version 2.1.1\"\ngit push origin main --follow-tags\ngit branch -d hotfix/fix-description\n```\n\n## Related Standards\n\n- [Conventional Commits](https://www.conventionalcommits.org/)\n- [Semantic Versioning](https://semver.org/)\n- [Keep a Changelog](https://keepachangelog.com/)\n- [GitHub Flow](https://docs.github.com/en/get-started/quickstart/github-flow)\n\n---\n\n_Last updated: 2026-02-22_\n\nFile v1.0.0:pyproject.toml\n\n[build-system]\nrequires = [\"setuptools>=61.0\"]\nbuild-backend = \"setuptools.build_meta\"\n\n[project]\nname = \"github-release-workflow\"\nversion = \"1.0.0\"\ndescription = \"Professional GitHub release workflow specification\"\nreadme = \"README.md\"\nlicense = {text = \"MIT\"}\nauthors = [\n    {name = \"Steven\", email = \"steven@example.com\"}\n]\nkeywords = [\"git\", \"github\", \"release\", \"workflow\", \"cicd\", \"conventional-commits\"]\nclassifiers = [\n    \"Development Status :: 4 - Beta\",\n    \"Intended Audience :: Developers\",\n    \"License :: OSI Approved :: MIT License\",\n    \"Programming Language :: Python :: 3\",\n    \"Programming Language :: Python :: 3.10\",\n    \"Programming Language :: Python :: 3.11\",\n    \"Programming Language :: Python :: 3.12\",\n]\n\ndependencies = []\n\n[project.scripts]\ngh-release = \"release:main\"\n\n[tool.setuptools.packages.find]\nwhere = [\".\"]","readmeExcerpt":"Skill: GitHub Release Workflow Owner: weapon3k Summary: Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) updating... Tags: git:1.0.0, github:1.0.0, latest:1.1.0, release:1.0.0, workflow:1.0.0 Version history: v1.1.0 | 2026-02-22T07:14:46.155Z | user Add README update requirement for releases v1.0.0 | 2026-02-21T17:02:5","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"# 1. Ensure clean working tree\ngit status\n\n# 2. Run tests and format\npip install -e \".[dev]\"\npytest\nblack lib/ tests/\n\n# 3. Update version in pyproject.toml\n# Edit: version = \"2.1.0\"\n\n# 4. Update CHANGELOG.md\n# Add new section with today's date\n\n# 5. Update README.md (IMPORTANT!)\n# - Update version badge\n# - Update features list\n# - Update project structure if changed\n# - Update roadmap table\n\n# 6. Update other docs as needed\n# - docs/*.md\n# - API documentation\n# - Examples\n\n# 7. Stage and commit\ngit add .\ngit commit -m \"release: v2.1.0 - Description\"\n\n# 8. Create tag\ngit tag -a v2.1.0 -m \"Version 2.1.0\"\n\n# 9. Push\ngit push\ngit push origin v2.1.0"},{"language":"text","snippet":"<type>(<scope>): <description>\n\nTypes: feat, fix, docs, style, refactor, test, chore, release"},{"language":"text","snippet":"MAJOR.MINOR.PATCH\n- MAJOR: Breaking changes\n- MINOR: New features (backward compatible)\n- PATCH: Bug fixes"},{"language":"text","snippet":"main (stable)\n  ↑\ndevelop (integration)\n  ↑\nfeature/* (new features)"},{"language":"bash","snippet":"gh release create v2.1.0 \\\n  --title \"Version 2.1.0\" \\\n  --notes \"Release notes\""},{"language":"bash","snippet":"git clone https://github.com/weapon3k/github-release-workflow.git\ncd github-release-workflow\npip install -e ."}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: github-release-workflow\ndescription: \"Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) updating README and docs, (5) setting up CI/CD for releases.\"\nmetadata:\n  {\n    openclaw: { emoji: \"🚀\" },\n  }\n---\n\n# GitHub Release Workflow Skill\n\nA standardized workflow for professional GitHub releases.\n\n**IMPORTANT: Always update README.md and documentation before releasing!**\n\n## Prerequisites\n\n- Git installed\n- GitHub CLI (`gh`) authenticated\n- Git repository initialized\n\n## Quick Commands\n\n### Full Release Flow\n\n```bash\n# 1. Ensure clean working tree\ngit status\n\n# 2. Run tests and format\npip install -e \".[dev]\"\npytest\nblack lib/ tests/\n\n# 3. Update version in pyproject.toml\n# Edit: version = \"2.1.0\"\n\n# 4. Update CHANGELOG.md\n# Add new section with today's date\n\n# 5. Update README.md (IMPORTANT!)\n# - Update version badge\n# - Update features list\n# - Update project structure if changed\n# - Update roadmap table\n\n# 6. Update other docs as needed\n# - docs/*.md\n# - API documentation\n# - Examples\n\n# 7. Stage and commit\ngit add .\ngit commit -m \"release: v2.1.0 - Description\"\n\n# 8. Create tag\ngit tag -a v2.1.0 -m \"Version 2.1.0\"\n\n# 9. Push\ngit push\ngit push origin v2.1.0\n```\n\n### README Update Checklist\n\nWhen releasing a new version, always update README.md:\n\n| Item | Description |\n|------|-------------|\n| Version badge | Update `version-x.x.x-blue` |\n| Features list | Add new features, remove deprecated |\n| Project structure | Reflect new files/directories |\n| Installation | Update if deps changed |\n| Usage | Add new examples if needed |\n| Roadmap | Move current version to done, add next |\n| API docs | Update if API changed |\n\n### Conventional Commits Format\n\n```\n<type>(<scope>): <description>\n\nTypes: feat, fix, docs, style, refactor, test, chore, release\n```\n\nExamples:\n- `feat(memory): add SQLite support`\n- `fix(vitality): correct energy calculation`\n- `docs: update README`\n\n### Version Format\n\n```\nMAJOR.MINOR.PATCH\n- MAJOR: Breaking changes\n- MINOR: New features (backward compatible)\n- PATCH: Bug fixes\n```\n\n## Branch Strategy\n\n```\nmain (stable)\n  ↑\ndevelop (integration)\n  ↑\nfeature/* (new features)\n```\n\n## GitHub Release (Optional)\n\n```bash\ngh release create v2.1.0 \\\n  --title \"Version 2.1.0\" \\\n  --notes \"Release notes\"\n```\n\n## See Also\n\n- Full specification: `github-release-workflow/SPEC.md`\n- Keep a Changelog: https://keepachangelog.com/\n- Semantic Versioning: https://semver.org/\n- Conventional Commits: https://www.conventionalcommits.org/"},{"path":"README.md","content":"# GitHub Release Workflow\n\n<p align=\"center\">\n  <img src=\"https://img.shields.io/badge/version-1.0.0-blue\" alt=\"Version\">\n  <img src=\"https://img.shields.io/badge/python-3.10+-green\" alt=\"Python\">\n  <img src=\"https://img.shields.io/badge/license-MIT-orange\" alt=\"License\">\n</p>\n\n> A standardized workflow for professional GitHub releases.\n\n## Overview\n\nThis project provides a complete specification and CLI tool for professional GitHub releases, following industry best practices:\n\n- **Conventional Commits** — Clear commit message format\n- **Semantic Versioning** — Standard version numbers\n- **Keep a Changelog** — Structured changelog\n- **GitHub Releases** — Tagged releases with notes\n\n## Installation\n\n```bash\ngit clone https://github.com/weapon3k/github-release-workflow.git\ncd github-release-workflow\npip install -e .\n```\n\n## Quick Start\n\n```bash\n# Initialize git (first time)\ngh-release init\n\n# Create a release\ngh-release release v1.0.0\n\n# Check status\ngh-release status\n\n# View log\ngh-release log -n 10\n```\n\n## Workflow\n\n### 1. Prepare\n\n```bash\n# Ensure clean working tree\ngit status\npytest\nblack .\n```\n\n### 2. Update\n\n- Update version in `pyproject.toml`\n- Add entry to `CHANGELOG.md`\n\n### 3. Release\n\n```bash\ngit add .\ngit commit -m \"release: v1.0.0\"\ngit tag -a v1.0.0 -m \"Version 1.0.0\"\ngit push\ngit push origin v1.0.0\n```\n\n## Commit Format\n\n```\n<type>(<scope>): <description>\n\nTypes: feat, fix, docs, style, refactor, test, chore, release\n```\n\n## Version Format\n\n```\nMAJOR.MINOR.PATCH\n```\n\n- **MAJOR**: Breaking changes\n- **MINOR**: New features (backward compatible)\n- **PATCH**: Bug fixes\n\n## Files\n\n- `SPEC.md` — Full specification\n- `SKILL.md` — OpenClaw skill definition\n- `release.py` — CLI tool\n\n## See Also\n\n- [Conventional Commits](https://www.conventionalcommits.org/)\n- [Semantic Versioning](https://semver.org/)\n- [Keep a Changelog](https://keepachangelog.com/)\n\n---\n\n**License**: MIT"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn71685jv7z3r8kfqpg450k4dd81kkd8\",\n  \"slug\": \"github-release-workflow\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1771744486155\n}"},{"path":"SPEC.md","content":"# GitHub Release Workflow Specification\n\n> A standardized workflow for professional GitHub releases.\n\n## Overview\n\nThis specification defines a professional release workflow for Python projects, inspired by industry best practices.\n\n## Prerequisites\n\n- Git installed\n- GitHub CLI (`gh`) authenticated\n- Python 3.10+\n- Git repository initialized\n\n## Release Workflow\n\n### 1. Pre-Release Checklist\n\n```bash\n# Ensure clean working tree\ngit status\n\n# Update dependencies\npip install -e \".[dev]\"\n\n# Run tests\npytest\n\n# Format code\nblack lib/ tests/\n\n# Type checking (optional)\nmypy lib/\n```\n\n### 2. Update Version\n\nUpdate version in:\n- `pyproject.toml` → `version`\n- `CHANGELOG.md` → Add new version header\n\n```bash\n# Example: bump to 2.1.0\n# Edit pyproject.toml: version = \"2.1.0\"\n```\n\n### 3. Update Changelog\n\nAdd new section in `CHANGELOG.md`:\n\n```markdown\n## [2.1.0] - YYYY-MM-DD\n\n### Added\n- New feature 1\n- New feature 2\n\n### Changed\n- Improvement 1\n\n### Fixed\n- Bug fix 1\n\n### Removed\n- Deprecated feature 1\n```\n\n### 4. Stage Changes\n\n```bash\ngit add .\ngit status\n```\n\n### 5. Commit\n\nFollow [Conventional Commits](https://www.conventionalcommits.org/):\n\n```bash\ngit commit -m \"release: v2.1.0 - Added new features and improvements\"\n```\n\n### 6. Create Tag\n\n```bash\ngit tag -a v2.1.0 -m \"Version 2.1.0: Release description\"\n```\n\n### 7. Push\n\n```bash\ngit push\ngit push origin v2.1.0\n```\n\n### 8. Create GitHub Release (Optional)\n\n```bash\ngh release create v2.1.0 \\\n  --title \"Version 2.1.0\" \\\n  --notes \"Release notes from CHANGELOG.md\"\n```\n\n## Branch Strategy\n\n```\nmain (stable)\n  ↑\ndevelop (integration)\n  ↑\nfeature/* (new features)\n  ↑\nhotfix/* (urgent fixes)\n```\n\n### Branch Types\n\n| Branch | Purpose | Base | Merge To |\n|--------|---------|------|----------|\n| `main` | Stable releases | - | - |\n| `develop` | Integration | main | main |\n| `feature/*` | New features | develop | develop |\n| `hotfix/*` | Urgent fixes | main | main, develop |\n| `release/*` | Release prep | develop | main, develop |\n\n## Versioning\n\nFollow [Semantic Versioning](https://semver.org/):\n\n```\nMAJOR.MINOR.PATCH\n  │    │    │\n  │    │    └── Bug fixes\n  │    └─────── New features (backward compatible)\n  └─────────── Breaking changes\n```\n\n### Version Format\n\n- **Release**: `v2.1.0` (annotated tag)\n- **Pre-release**: `v2.1.0-alpha.1`, `v2.1.0-beta.1`\n- **Build**: `v2.1.0+build.123`\n\n## Commit Message Format\n\n### Conventional Commits\n\n```\n<type>(<scope>): <description>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n### Types\n\n| Type | Description |\n|------|-------------|\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `docs` | Documentation |\n| `style` | Formatting |\n| `refactor` | Code restructuring |\n| `test` | Tests |\n| `chore` | Maintenance |\n| `release` | Version release |\n\n### Examples\n\n```bash\ngit commit -m \"feat(memory): add SQLite storage support\"\ngit commit -m \"fix(vitality): correct energy decay calculation\"\ngit commit -m \"docs: update README with examples\"\ngit commit -m \"release: v2.1.0\"\n```\n\n## CI"},{"path":"pyproject.toml","content":"[build-system]\nrequires = [\"setuptools>=61.0\"]\nbuild-backend = \"setuptools.build_meta\"\n\n[project]\nname = \"github-release-workflow\"\nversion = \"1.1.0\"\ndescription = \"Professional GitHub release workflow specification\"\nreadme = \"README.md\"\nlicense = {text = \"MIT\"}\nauthors = [\n    {name = \"Steven\", email = \"steven@example.com\"}\n]\nkeywords = [\"git\", \"github\", \"release\", \"workflow\", \"cicd\", \"conventional-commits\"]\nclassifiers = [\n    \"Development Status :: 4 - Beta\",\n    \"Intended Audience :: Developers\",\n    \"License :: OSI Approved :: MIT License\",\n    \"Programming Language :: Python :: 3\",\n    \"Programming Language :: Python :: 3.10\",\n    \"Programming Language :: Python :: 3.11\",\n    \"Programming Language :: Python :: 3.12\",\n]\n\ndependencies = []\n\n[project.scripts]\ngh-release = \"release:main\"\n\n[tool.setuptools.packages.find]\nwhere = [\".\"]"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) updating... Skill: GitHub Release Workflow Owner: weapon3k Summary: Professional GitHub release workflow. Use when: (1) releasing a new version, (2) managing versions and tags, (3) following conventional commits, (4) updating... Tags: git:1.0.0, github:1.0.0, latest:1.1.0, release:1.0.0, workflow:1.0.0 Version history: v1.1.0 | 2026-02-22T07:14:46.155Z | user Add README update requirement for releases v1.0.0 | 2026-02-21T17:02:5","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1019,"uniquenessScore":49,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T14:58:59.673Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T14:58:59.673Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T17:41:10.385Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}