@gitlobster/bridge

Migrate legacy OpenClaw skills into GitLobster packages with manifest.json and SKILL.md.

19|2|Updated Feb 3, 2026

Search Tags:#automation #scaffolding #migration #openclaw #gitlobster #skill package

Ready to run

npx skills add https://github.com/ClawStackStudios/GitLobster --skill gitlobster-bridge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: @gitlobster/bridge
Source: https://github.com/ClawStackStudios/GitLobster/tree/main/packages/%40gitlobster/bridge
Command: npx skills add https://github.com/ClawStackStudios/GitLobster --skill gitlobster-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the migration of legacy OpenClaw skills into the modern GitLobster capability package format, streamlining the transition to a new skill ecosystem.

Core Features & Use Cases

Automated Scaffolding: Generates manifest.json, SKILL.md, and basic src/index.js for new GitLobster packages.
Directory Structure: Organizes migrated skills into the standard GitLobster package structure.
Use Case: If you have a collection of skills developed for an older system, this tool can quickly create the foundational files needed to publish them to the GitLobster registry.

Quick Start

Run the gitlobster bridge skill to begin migrating your existing skills.

Frequently Asked Questions about @gitlobster/bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate legacy OpenClaw skills to a new package format?▼

Automated skill migration works by scanning existing skill directories and scaffolding new package structures with manifest.json, SKILL.md, and a basic src/index.js entry point. This process transforms legacy OpenClaw skill formats into modern GitLobster capability packages for local development environments.

What files are generated when scaffolding a GitLobster capability package?▼

Scaffolding a GitLobster capability package generates manifest.json, SKILL.md, and a basic src/index.js entry point script. These files establish the standard directory structure required to organize and publish migrated skills to the GitLobster registry.

When do I need to scaffold a new package structure for skill migration?▼

You need to scaffold a new package structure when transitioning a collection of skills developed for an older system to a modern registry. This automated process quickly creates the foundational files required to publish legacy OpenClaw skills as GitLobster capability packages.

Can I automate skill migration for local development environments?▼

Yes, skill migration automation supports local development environments for skill supply chain transformation. It scans existing local skill directories and scaffolds modern GitLobster package structures to streamline the transition to a new skill ecosystem.

Does the GitLobster bridge tool require any dependencies to migrate OpenClaw skills?▼

The GitLobster bridge tool operates without dependencies, running scripts to automate the migration of legacy OpenClaw skills. It directly scans existing skill directories and scaffolds new capability package structures in your local environment.