migrate-wayne-chunks-to-core

Migrate new chunks from polaris_dev_wayne.chunks to polaris_core.chunks.

1|1|Updated May 31, 2026
One-click install
npx skills add https://github.com/WayneSHC/polaris-desk --skill migrate-wayne-chunks-to-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-wayne-chunks-to-core
Source: https://github.com/WayneSHC/polaris-desk/tree/main/.claude/skills/migrate-wayne-chunks-to-core
Command: npx skills add https://github.com/WayneSHC/polaris-desk --skill migrate-wayne-chunks-to-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-cloud-bigquery, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the migration of chunks from the 'polaris_dev_wayne.chunks' dataset to the 'polaris_core.chunks' dataset, ensuring that all relevant data is synchronized and up-to-date.

Core Features & Use Cases

  • Data Synchronization: Migrates new chunks from 'polaris_dev_wayne.chunks' to 'polaris_core.chunks' to maintain a unified dataset.
  • Recurring Execution: Designed for recurring execution to keep the dataset current as new chunks are added.
  • Use Case: Ideal for teams working with evolving datasets, where regular synchronization between development and production datasets is crucial.

Quick Start

Run the migration by executing the command: uv run python scripts/migrate_wayne_chunks_to_core.py

Frequently Asked Questions about migrate-wayne-chunks-to-core

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

FAQPage Schema
How do I automate BigQuery dataset synchronization between development and production?

You can automate BigQuery dataset synchronization by running a script that migrates new chunks from a development dataset to a production one. This ensures your production environment stays current with evolving data.

What is the best way to migrate new data chunks to a core BigQuery dataset?

Migrating new data chunks to a core BigQuery dataset is best handled by a recurring execution script. This approach regularly checks for and migrates new chunks, ensuring continuous synchronization between your environments.

Do I need specific environment variables to run BigQuery chunk migration scripts?

Yes, you need specific environment variables for authorization to run BigQuery chunk migration scripts. The script requires Google Cloud BigQuery access to successfully transfer data between the development and production datasets.

Can I use this tool for recurring dataset synchronization in BigQuery?

Yes, you can use this tool for recurring dataset synchronization in BigQuery. It is specifically designed for regular execution to keep your production core dataset up-to-date as new chunks are added to development.

Does the chunk migration script support incremental data transfers?

The chunk migration script supports incremental data transfers by targeting new chunks added to the development dataset. This ensures only the relevant new data is migrated to the core production dataset during each execution.