clawdhub

The ClawdHub CLI is an essential tool for developers and power users of the CLAWDBOT ecosystem. It acts as a package management interface specifically designed for agent skills, enabling seamless interaction with the clawdhub.com registry. By providing a centralized command-line interface, it simplifies the lifecycle management of skills, allowing you to discover community-contributed functionality, maintain version consistency across your local environments, and share your own developments with the global community.

• Perform granular searches for specific agent capabilities, such as postgres backups or web scraping tools, using simple string matching.

• Support for precision version control during installation and updates, allowing users to lock skills to specific releases or upgrade to the latest versions.

• Comprehensive update management, including hash-based file validation to ensure local installations are synced correctly, with support for force-updates and global batch operations.

• Direct publication workflow to push new skill folders to the registry, including support for custom slugs, semantic versioning, and changelog management to inform end users of updates.

• Seamless integration into local development environments, with configurable registry URLs and custom work directories to suit varying project structures.

• Input Requirements: Users must have Node.js installed to run the npm-packaged CLI. Authentication via clawdhub login is required for publication workflows.

• Usage Tips: If you are working in a WSL environment, ensure you are utilizing the native WSL filesystem rather than Windows mounts to avoid permission errors and performance bottlenecks during installation.

• Configuration: The tool defaults to the cwd for operations, but you can override the installation directory using the --dir flag or manage global registries via the CLAWDHUB_REGISTRY environment variable.

• Practical Constraints: Always ensure that dependencies required by specific skills—such as Homebrew or specific Node.js versions—are met in your local host environment before executing skill-specific commands.

• Security: Treat all externally fetched skills as potentially untrusted code. Regularly verify the changelogs and source contents of installed skills before executing them within your local AI assistant's runtime.