clawhub-publish-doctor

What This Skill Does

The clawhub-publish-doctor is an essential utility for developers and AI agents managing the lifecycle of OpenClaw skills on the ClawHub registry. Publishing to a registry can often be hampered by transient network issues, authentication bottlenecks, or environmental discrepancies. This skill provides a structured framework for stabilizing the publishing process. It acts as an automated reliability layer that executes pre-publish diagnostic checks, handles authentication protocols, manages safe-publishing logic with built-in retry mechanisms, and offers post-publish verification to ensure your skill is discoverable and correctly configured. By integrating this skill, users can bypass common pitfalls like browser-login timeouts in headless CI/CD environments and resolve ambiguous security-scan visibility errors through standardized inspection workflows.

Installation

You can add the ClawHub Publish Doctor to your environment by running the following command in your terminal:

clawhub install openclaw/skills/skills/bluebirdback/clawhub-publish-doctor

Ensure that you have the base clawhub CLI installed and your credentials properly exported if working in a headless environment.

Use Cases

• Automated CI/CD Pipelines: Integrate preflight checks and safe-publish scripts into your GitHub Actions or GitLab runners to ensure deployments are successful without manual oversight.
• Troubleshooting Failed Deployments: If a skill fails to appear on the registry or returns an error during the inspect phase, use this tool to classify the error and attempt a verified retry.
• Headless Environment Management: Utilize token-based login workflows to bypass browser-dependent authentication requirements.
• Registry Maintenance: Verify that skill metadata, slug names, and versioning adhere to the canonical structure required for public listing.

Example Prompts

1. "I'm getting an auth error when trying to push my new skill. Can you run the preflight checks and help me authenticate using a token?"
2. "My skill was published but isn't showing up on the website. Use the inspection tool to check for transient registry issues and verify the slug URL."
3. "Run a safe publish for my current directory as a new skill named 'data-processor' version 1.0.1, and verify the deployment once complete."

Tips & Limitations

• Transient States: Always allow a few minutes after a publish command before declaring a permanent failure, as the ClawHub backend may require time to propagate metadata and perform security scans.
• Token Security: When using token-based logins, ensure your tokens are handled as secrets and never committed to source control.
• Error Classification: Always cross-reference the error codes with the references/error-map.md file included in the source repo before attempting manual overrides.
• Environment: This skill is optimized for environments where standard POSIX shell commands are available; users on Windows should ensure they are using Git Bash or WSL.