github-to-clawhub_skill

This skill converts a GitHub project into a clawhub-ready OpenClaw skill by analyzing README, checking duplicates, drafting SKILL.md, and publishing.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 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 github-to-clawhub

  • _meta.json310 B
  • SKILL.md5.4 KB

Overview

This skill automates converting a GitHub open-source project into an OpenClaw skill and publishing it to clawhub.com. It guides the user through fetching project documentation, checking for existing skills on clawhub, generating skill metadata and files, and performing the publish step. It can run end-to-end when given a GitHub URL and a clawhub API token.

How this skill works

Given a GitHub URL and a clawhub token, the skill fetches the project’s documentation and extracts core function, technical approach, external dependencies, license, and hard requirements. It queries clawhub for similar skills to detect duplicates or overlaps, helps craft a unique slug, display name and tags, generates the necessary skill metadata and local directory structure, then runs the clawhub publish command and validates the result. If information is missing, it asks only for the missing item and supports a one-shot quick mode when all inputs are provided.

When to use it

  • You want to turn an open-source GitHub project into a reusable OpenClaw skill.
  • You have a GitHub URL and a clawhub API token and want an automated publish flow.
  • You need duplicate detection on clawhub before publishing a new skill.
  • You want consistent skill metadata, templates, and publish automation.
  • You prefer a single command flow that handles common publish errors.

Best practices

  • Provide the clawhub token upfront to enable uninterrupted automation.
  • Supply a descriptive slug and display name; use lowercase and hyphens for slugs.
  • Ensure the project does not require local GPU, specialized hardware, or complex local services.
  • Confirm tags and a one-line core value so the generated metadata is accurate.
  • Use quick mode only when all inputs (URL, token, slug/name/tags) are complete.

Example use cases

  • Convert a lightweight NLP project into a skill that exposes its analysis endpoints.
  • Publish a CLI-based utility as an OpenClaw skill with example invocations and output templates.
  • Archive and publish an agent orchestration example as a documented skill on clawhub.
  • Wrap a data processing script into a skill with clear input/output templates and usage steps.
  • Perform an upfront duplicate check and choose a unique slug before publishing.

FAQ

A public GitHub URL and a valid clawhub API token are required; the token should start with clh_.

Can you publish projects that need a GPU or complex local services?

No. Projects requiring local GPUs, large VRAM, specialized hardware, or complex multi-service local deployment are not suitable for this automated skill conversion.

What if a slug is already taken on clawhub?

The process will report a duplicate and prompt you to provide a more descriptive, unique slug before retrying.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
github-to-clawhub skill by openclaw/skills | VeilStrat