---

name: release-workflow description: > Orchestrate ClawMart skill releases with version bumps, tagging, and announcements. USE WHEN: the user says "release [skill name]", "start a release", "batch release", "bump version", "what needs releasing", "draft a release tweet", or "announce [skill] on Twitter". DON'T USE WHEN: the user wants to create a new skill from scratch (use scaffold), verify provenance (use provenance-verifier), or bootstrap their dev environment (use dev-install). OUTPUTS: version bump commits, git tags, GitHub Actions run URLs, Claw Mart publication confirmation, and draft tweets for user approval.

Release Workflow

Version: 1.1.0 Price: Free Type: Skill

Description

End-to-end release orchestrator for SpookyJuice skills on Claw Mart. Handles version bumps, git tagging, GitHub Actions triggering, and Twitter/X announcements in a single guided workflow. Supports both single-skill and batch releases. Every destructive action requires explicit user confirmation.

Prerequisites

• Git repository with versions.json at the root
• GitHub repository with the release-skill.yml Actions workflow configured
• Claw Mart creator account with API key
• Environment variables:
  • CLAWMART_API_KEY=cm_live_... (Claw Mart API auth)
  • X_CONSUMER_KEY (Twitter/X API v2)
  • X_CONSUMER_SECRET (Twitter/X API v2)
  • X_BEARER_TOKEN (Twitter/X API v2)
  • X_OAUTH2_CLIENT_ID (Twitter/X OAuth 2.0)
  • X_OAUTH2_CLIENT_SECRET (Twitter/X OAuth 2.0)
• Push access to the remote repository (for tags)

Setup

1. Set all required environment variables listed above
2. Copy SKILL.md into your OpenClaw skills directory (e.g. skills/release-workflow/SKILL.md)
3. Verify versions.json exists at the repo root and contains a "skills" key
4. Verify .github/workflows/release-skill.yml exists and is configured
5. Reload OpenClaw
6. Test with: "Show release status"

Commands

Release Execution

• "Release [skill-name] at [version]"
• "Release [skill-name] with a patch bump"
• "Release [skill-name] with a minor bump"
• "Release [skill-name] with a major bump"
• "Batch release all updated skills"
• "Release all skills that need updating"

Status & Info

• "Show release status"
• "What needs releasing?"
• "What version is [skill-name] at?"
• "Show changelog for [skill-name]"
• "Compare local vs published versions"

Version Management

• "Bump [skill-name] to [version]"
• "Update changelog for [skill-name]"
• "Show versions.json"

Announcements

• "Draft a release tweet for [skill-name] v[version]"
• "Announce [skill-name] release on Twitter"
• "Show pending announcements"

Workflow

Single Skill Release

1. Validate prerequisites

   • Confirm versions.json exists and is valid JSON
   • Confirm the skill entry exists under "skills" or "tools" in versions.json
   • Confirm the working tree is clean (git status — no uncommitted changes)
   • Confirm the current branch is main

2. Determine version

   • If explicit version provided: validate it is a valid semver and greater than the current version
   • If bump type provided (patch/minor/major): compute the new version from the current version
   • Show the version transition: skill-inspector: 1.0.0 -> 1.1.0
   • Require explicit confirmation to proceed

3. Update versions.json

   • Set "version" to the new semver string
   • Set "changelog" to the user-provided changelog entry (prompt if not provided)
   • Write the updated versions.json to disk
   • Stage and commit: git add versions.json && git commit -m "chore: bump <skill-name> to v<version>"

4. Create and push git tag

   • Tag format for skills: <skill-name>/v<semver> (e.g. skill-inspector/v1.1.0)
   • Tag format for tools: v<semver> (e.g. v1.1.0)
   • Show the exact tag string and require confirmation
   • Run: git tag <tag> then git push origin main --tags

5. Monitor GitHub Actions

   • The release-skill.yml workflow triggers on the tag push
   • Report the Actions run URL: https://github.com/<owner>/<repo>/actions
   • Wait for user to confirm the workflow completed successfully before proceeding

6. Verify Claw Mart publication

   • Call GET https://www.shopclawmart.com/api/v1/listings with Authorization: Bearer ${CLAWMART_API_KEY}
   • Confirm the new version appears on the listing
   • Report: skill name, version, price, visibility

7. Draft Twitter/X announcement

   • Generate tweet from template:

     [Skill Name] v[version] is live on Claw Mart. [one-line changelog]. Free/[$price] at shopclawmart.com #OpenClaw #AI
     

   • Show the full draft tweet to user
   • NEVER auto-post — require explicit "post it", "yes", or "tweet it" confirmation
   • On approval: post via X API v2 (POST https://api.twitter.com/2/tweets) from the configured X/Twitter account
   • Report: tweet URL and confirmation

8. Future: Update website ticker (placeholder)

   • When the project website releases feed is implemented, push the release event here
   • Currently a no-op — log that this step is pending

Batch Release

1. Read versions.json — identify all skills and tools
2. For each entry, compare the local version against the latest git tag matching <name>/v* or v*
3. Show a table of what needs releasing:

   Skill              Local     Tagged    Status
   skill-inspector    1.1.0     1.0.0     NEEDS RELEASE
   clawmart-manager   1.0.0     1.0.0     CURRENT
   clawmart-reviewer  1.0.1     1.0.0     NEEDS RELEASE
   

4. Require confirmation of the full batch before proceeding
5. Run the single-skill release workflow for each item that needs releasing, in sequence
6. Collect all tweet drafts and present them together for batch approval
7. Post approved tweets in sequence

Release Status

1. Read versions.json for all entries
2. Fetch latest git tags for each skill/tool
3. Call GET /listings from Claw Mart API to check published versions
4. Show a combined status table:

   Skill              versions.json   Git Tag   Claw Mart   Status
   skill-inspector    1.0.0           1.0.0     1.0.0       IN SYNC
   clawmart-manager   1.1.0           1.0.0     1.0.0       LOCAL AHEAD
   release-workflow   1.0.0           (none)    (none)      UNRELEASED
   

Tag Format

| Entry Type | Tag Pattern | Example | |------------|-----------------------|----------------------------| | Skill | <skill-name>/v<ver> | skill-inspector/v1.1.0 | | Tool | v<ver> | v1.1.0 |

Tags are created on the main branch only. The release-skill.yml GitHub Actions workflow matches these tag patterns to determine which skill to publish.

Tweet Template

[Skill Name] v[version] is live on Claw Mart. [one-line changelog]. Free/[$price] at shopclawmart.com #OpenClaw #AI

• Character limit: 280 (validate before posting)
• Hashtags: #OpenClaw #AI (always included)
• Price: "Free" if price is 0, otherwise "$[price]"
• Account: configured X/Twitter account
• API: X API v2 with OAuth 2.0 PKCE or OAuth 1.0a User Context

API Reference

Claw Mart

• Base URL: https://www.shopclawmart.com/api/v1
• Auth: Authorization: Bearer ${CLAWMART_API_KEY}

| Method | Endpoint | Purpose | |--------|----------------|----------------------------------| | GET | /me | Profile + subscription state | | GET | /listings | Your creator listings |

Twitter/X

• Base URL: https://api.twitter.com/2
• Auth: OAuth 2.0 with PKCE or OAuth 1.0a User Context

| Method | Endpoint | Purpose | |--------|------------|------------------| | POST | /tweets | Post a tweet |

Guardrails

• Never auto-post tweets. Always show the full draft and require explicit approval ("yes", "post it", "tweet it").
• Never publish or tag without user confirmation. Every destructive action (commit, tag, push, post) requires a "yes" gate.
• Never release from a dirty working tree. Require git status to be clean before starting.
• Never release from a branch other than main unless the user explicitly overrides.
• Never skip the versions.json update. The version bump commit must precede the tag.
• Never print or log API keys or tokens. Redact CLAWMART_API_KEY, all X/Twitter credentials in all output.
• Never push a tag that already exists. Check with git tag -l before creating.
• Never post duplicate tweets. Check recent tweets or maintain a local log before posting.
• Validate semver strictly. Reject versions that are not valid semver or not greater than the current version.
• Require GET /me validation before any Claw Mart API write operation.
• Batch releases run sequentially — never parallelize tag pushes to avoid race conditions in GitHub Actions.