exec-clawhub-publish-doctor_skill

This skill diagnoses exec-tooling failures during ClawHub publishing and guides safe retry and verification to reduce downtime.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill exec-clawhub-publish-doctor

  • _meta.json312 B
  • SKILL.md2.5 KB

Overview

This skill diagnoses and mitigates exec-related failures when publishing skills to ClawHub and when running GitHub CLI repo queries. It bundles preflight checks, safer publish commands with retry-aware verification, and schema-aware GitHub search fallbacks to reduce false failures. Use it to stabilize publishing workflows and to classify transient vs persistent errors quickly.

How this skill works

It runs environment and dependency checks, verifies authentication state, and executes publish commands with built-in retries and post-publish inspection tolerant of temporary registry delays. For GitHub CLI search issues it runs a schema-aware wrapper that falls back to supported JSON fields to avoid errors like "Unknown JSON field". The skill also maps common error signatures to recommended remediation steps for faster triage.

When to use it

  • Publishing a skill to ClawHub fails or returns inspect errors immediately after publish
  • Automated CI/CD jobs hit browser-login or token authentication problems in headless environments
  • GitHub CLI repo searches fail due to JSON-field schema mismatches
  • You see pending security-scan visibility errors or temporary registry state inconsistencies
  • You need to confirm whether an inspect error is transient before escalating

Best practices

  • Use token-based login for servers and CI: clawhub login --token <clh_token>
  • Run preflight checks before publishing: bash scripts/clawhub_preflight.sh
  • Publish with the safe wrapper to get retries and tolerant verification
  • Verify both CLI inspect and the canonical web URL to confirm visibility
  • Prefer supported gh JSON fields like fullName when running searches

Example use cases

  • CI pipeline publishes a new skill version and inspect immediately fails—use safe publish to retry and re-inspect
  • Headless server cannot complete browser-login—switch to token login and run preflight checks
  • gh search repos --json returns Unknown JSON field—use the schema-aware search wrapper
  • Investigating transient pending security-scan visibility errors after a publish
  • Bulk-archiving or backing up skills where stable publish and repo search behavior is required

FAQ

Treat it as potentially transient for a few minutes; rerun the safe inspect steps and verify the web URL before escalating.

Which login method should I use in CI?

Prefer token-based login (clawhub login --token) for headless and CI environments to avoid browser-login issues.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational