← Back to Skills Marketplace
okikesolutions

ClawHub Release Manager

by okikeSolutions · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ⚠ suspicious
98
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install clawhub-release-manager
Description
Safely release and publish skill updates to ClawHub with version bump discipline. Use when preparing patch/minor releases, running lint/build checks, writing...
README (SKILL.md)

ClawHub Release Manager

Workflow

  1. Preflight
  • Confirm clawhub whoami authenticated.
  • Ensure working directory points to target skill.
  1. Versioning
  • Determine bump type (patch by default for fixes).
  • Update version in all required places (runtime + package manifest).
  1. Validation
  • Run project checks (Bun preferred):
    • bun run lint
    • bun run build
  • Stop on failure and return fix-first plan.
  1. Publish
  • Run clawhub publish ... --version ... --changelog ...
  • Capture and return release id.
  1. Post-publish
  • Provide install/update command to test.
  • Suggest scanner rerun if security-related.

Output format

Use references/output-template.md.

Guardrails

  • Do not publish without a version bump.
  • Keep changelog factual and tied to code/docs changes.
  • Include routing disclosure in release notes when behavior or data flow changed.
Usage Guidance
This skill appears to implement a reasonable ClawHub release workflow, but there are a few issues to check before installing: - Tooling: The runtime expects the 'clawhub' CLI and 'bun' (for lint/build). The skill metadata does not declare required binaries. Ensure those tools are installed and available on PATH before using the skill. - Credentials: Publishing requires ClawHub authentication (the SKILL.md checks 'clawhub whoami'). The skill doesn't declare which credentials it will use; confirm which account/config the agent will use and that you trust it to publish on your behalf. - Source transparency: The skill has no source or homepage listed. Prefer skills with a public repo or homepage you can inspect. Lack of source increases risk if something goes wrong. - File changes: The workflow edits version files and changelogs in the working directory. Run this in a branch or ensure you have backups and CI checks; verify the skill's actions on a non-production repo first. - Operational guardrails: Consider requiring an explicit confirmation step before the skill runs 'clawhub publish' (manual approval), or restricting the agent's environment so it cannot access production credentials inadvertently. If you need higher assurance, ask the publisher to update metadata to declare required binaries (clawhub, bun/node), list expected credential/config usage, and provide a source repository or homepage for review.
Capability Analysis
Type: OpenClaw Skill Name: clawhub-release-manager Version: 0.1.0 The skill bundle defines a standard release management workflow for the ClawHub platform, including version bumping, linting, building, and publishing. The instructions in SKILL.md and the template in references/output-template.md are aligned with the stated purpose and do not contain any indicators of malicious intent, data exfiltration, or harmful prompt injection.
Capability Assessment
⚠ Purpose & Capability
The SKILL.md explicitly requires running the 'clawhub' CLI and running project checks via 'bun' (bun run lint/build). However, the skill metadata lists no required binaries, no required env vars, and no primary credential. A release manager that runs 'clawhub publish' normally requires the ClawHub CLI and authenticated credentials; those should be declared. The absence of a declared source/homepage (source: unknown) reduces transparency.
ℹ Instruction Scope
The instructions stay on-topic: they describe checking authentication, bumping versions, running lint/build, publishing, and returning the release id using a provided output template. They instruct the agent to operate on the local working directory and modify version files and changelogs — expected for a release tool, but this implies the agent will edit repository files and invoke CLI tooling with whatever credentials/config are available in the environment.
✓ Install Mechanism
This is an instruction-only skill with no install spec or code files, which minimizes install-time risk (nothing is downloaded or written by an installer).
ℹ Credentials
No environment variables or credentials are declared, but the runtime steps depend on an authenticated 'clawhub' environment (clawhub whoami / clawhub publish). That implies reliance on existing local credentials/config; the skill should declare this dependence so users understand what secrets will be used. No unrelated credentials or unusual environment access are requested.
✓ Persistence & Privilege
The skill is not always-enabled and is user-invocable; it does not request to modify other skills or system-wide agent settings. The default ability for the model to invoke the skill autonomously remains, but that is normal and not by itself flagged.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install clawhub-release-manager
  3. After installation, invoke the skill by name or use /clawhub-release-manager
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release: adds routing change disclosure guidance and improved release output template.
Metadata
Slug clawhub-release-manager
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is ClawHub Release Manager?

Safely release and publish skill updates to ClawHub with version bump discipline. Use when preparing patch/minor releases, running lint/build checks, writing... It is an AI Agent Skill for Claude Code / OpenClaw, with 98 downloads so far.

How do I install ClawHub Release Manager?

Run "/install clawhub-release-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is ClawHub Release Manager free?

Yes, ClawHub Release Manager is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does ClawHub Release Manager support?

ClawHub Release Manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created ClawHub Release Manager?

It is built and maintained by okikeSolutions (@okikesolutions); the current version is v0.1.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments