_migrate-workers

Consolidate legacy Cloudflare background workers into a unified shared worker architecture.

34|6|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/flavien-ia/hypervibe-harness --skill migrate-workers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _migrate-workers
Source: https://github.com/flavien-ia/hypervibe-harness/tree/main/skills/_migrate-workers
Command: npx skills add https://github.com/flavien-ia/hypervibe-harness --skill migrate-workers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires wrangler, and includes scripts (resource) components.

What problem does it solve?

This skill resolves technical debt for users upgrading from older Hypervibe versions by consolidating fragmented, legacy Cloudflare background workers into a single, efficient, and unified shared worker.

Core Features & Use Cases

  • Automated Consolidation: Safely migrates database backups, quota monitors, and cron dispatchers into the new hypervibe-jobs architecture.
  • Verification & Safety: Ensures the new system is fully functional and verified before decommissioning legacy components, preventing any data loss.
  • Use Case: If you are upgrading your Hypervibe installation from a version older than 2.5, this skill automatically cleans up your Cloudflare environment and optimizes your background task management.

Quick Start

Run the start command in your terminal to trigger the migration process and consolidate your background workers.

Frequently Asked Questions about _migrate-workers

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

FAQPage Schema
How do I consolidate legacy Cloudflare background workers during a Hypervibe migration?

To consolidate legacy Cloudflare background workers during a Hypervibe migration, this skill automatically merges database backups, quota monitors, and cron dispatchers into a unified shared worker architecture.

What is the unified shared worker architecture for Cloudflare background tasks?

The unified shared worker architecture is a consolidated hypervibe-jobs framework that replaces fragmented legacy Cloudflare workers to optimize resource usage and simplify maintenance.

Do I need wrangler CLI to migrate legacy background workers?

Yes, you need the wrangler CLI, Node.js, and vault-managed credentials to perform secure, idempotent migration and verification of legacy background workers.

When should I migrate my background workers to the hypervibe-jobs architecture?

You should migrate your background workers to the hypervibe-jobs architecture when upgrading your Hypervibe installation from a pre-2.5 version to optimize resource usage and simplify maintenance.

How does the migration process handle decommissioning legacy Cloudflare workers?

The migration process ensures the new unified shared worker is fully functional and verified before decommissioning legacy Cloudflare components, preventing any data loss.

Can I use this skill to automate refactoring for Cloudflare Workers without Node.js?

No, this skill requires Node.js and wrangler CLI access to execute the automated consolidation and verification of background workers into the unified job registry.