How do I install the Exec Clawhub Publish Doctor skill?

Run npx skillmds@latest add johnalbertini14-glitch/exec-clawhub-publish-doctor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Exec Clawhub Publish Doctor safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Exec Clawhub Publish Doctor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Exec Clawhub Publish Doctor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Exec Clawhub Publish Doctor?

johnalbertini14-glitch (@johnalbertini14-glitch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Exec Clawhub Publish Doctor by johnalbertini14-glitch

Name: Exec Clawhub Publish Doctor
Rating: 4.2 (5 reviews)
Author: johnalbertini14-glitch

Exec Clawhub Publish Doctor

Diagnose and mitigate exec-related tooling failures around ClawHub publishing and GitHub CLI queries (auth, browser-login, missing dependencies, pending security-scan visibility errors, wrong profile/skill URLs, and gh JSON-field mismatch errors like Unknown JSON field). Use when publishing skills to ClawHub fails, inspect reports temporary errors, or GitHub CLI search commands fail due to field schema differences.

File contents

Exec ClawHub Publish Doctor

Stabilize ClawHub publishing with preflight checks, safer publish commands, and post-publish verification that tolerates temporary registry states.

Quick workflow

Run preflight checks:
- scripts/clawhub_preflight.sh
If login/browser issues appear, follow references/error-map.md.
Publish with retry-aware verification:
- scripts/clawhub_publish_safe.sh <skill_path> <slug> <name> <version> [changelog]
For GitHub search failures like Unknown JSON field, use:
- scripts/gh_search_repos_safe.sh "<query>" [limit]
If errors persist, classify with references/error-map.md before escalating.

Standard commands

Preflight

bash scripts/clawhub_preflight.sh

Login (token-based, headless-safe)

clawhub login --token <clh_token>
clawhub whoami

Safe publish

bash scripts/clawhub_publish_safe.sh ./my-skill my-skill "My Skill" 1.0.0 "Initial release"

Manual inspect

clawhub inspect my-skill --json

Safe GitHub repo search (schema-aware)

bash scripts/gh_search_repos_safe.sh "safe-exec skill" 15

Rules

Prefer token login in server/headless environments.
Treat inspect errors right after publish as potentially transient for a few minutes.
Verify with both CLI (clawhub inspect) and web URL (/skills/<slug>).
For gh search repos --json failures, prefer fullName over unsupported aliases like nameWithOwner, or run scripts/gh_search_repos_safe.sh.
Use canonical URLs:
- Skill: https://clawhub.ai/skills/<slug>
- Owner/slug: https://clawhub.ai/<handle>/<slug>
- User profile (if available): https://clawhub.ai/users/<handle>

Resources

references/error-map.md: quick diagnosis for common failure signatures.
scripts/clawhub_preflight.sh: dependency + environment checks.
scripts/clawhub_publish_safe.sh: publish + retry verification wrapper.
scripts/gh_search_repos_safe.sh: resilient gh search repos wrapper with JSON-field mismatch fallback.

---name: exec-clawhub-publish-doctordescription: Diagnose and mitigate exec-related tooling failures around ClawHub publishing and GitHub CLI queries (auth, browser-login, missing dependencies, pending security-scan visibility errors, wrong profile/skill URLs, and gh JSON-field mismatch errors like Unknown JSON field). Use when publishing skills to ClawHub fails, inspect reports temporary errors, or GitHub CLI search commands fail due to field schema differences.---# Exec ClawHub Publish DoctorStabilize ClawHub publishing with preflight checks, safer publish commands, and post-publish verification that tolerates temporary registry states.## Quick workflow1. Run preflight checks: - `scripts/clawhub_preflight.sh`2. If login/browser issues appear, follow `references/error-map.md`.3. Publish with retry-aware verification: - `scripts/clawhub_publish_safe.sh <skill_path> <slug> <name> <version> [changelog]`4. For GitHub search failures like `Unknown JSON field`, use: - `scripts/gh_search_repos_safe.sh "<query>" [limit]`5. If errors persist, classify with `references/error-map.md` before escalating.## Standard commands### Preflight```bashbash scripts/clawhub_preflight.sh```### Login (token-based, headless-safe)```bashclawhub login --token <clh_token>clawhub whoami```### Safe publish```bashbash scripts/clawhub_publish_safe.sh ./my-skill my-skill "My Skill" 1.0.0 "Initial release"```### Manual inspect```bashclawhub inspect my-skill --json```### Safe GitHub repo search (schema-aware)```bashbash scripts/gh_search_repos_safe.sh "safe-exec skill" 15```## Rules- Prefer token login in server/headless environments.- Treat `inspect` errors right after publish as potentially transient for a few minutes.- Verify with both CLI (`clawhub inspect`) and web URL (`/skills/<slug>`).- For `gh search repos --json` failures, prefer `fullName` over unsupported aliases like `nameWithOwner`, or run `scripts/gh_search_repos_safe.sh`.- Use canonical URLs: - Skill: `https://clawhub.ai/skills/<slug>` - Owner/slug: `https://clawhub.ai/<handle>/<slug>` - User profile (if available): `https://clawhub.ai/users/<handle>`## Resources- `references/error-map.md`: quick diagnosis for common failure signatures.- `scripts/clawhub_preflight.sh`: dependency + environment checks.- `scripts/clawhub_publish_safe.sh`: publish + retry verification wrapper.- `scripts/gh_search_repos_safe.sh`: resilient `gh search repos` wrapper with JSON-field mismatch fallback.

Frequently asked questions