fishbowlz

Name: fishbowlz
Availability: InStock
Author: Zaal

Sync ZAO OS changes to GitHub and deploy to fishbowlz.com.

1|1|Updated Mar 12, 2026

Search Tags:#git #deployment #repository #vercel #sync #standalone #fishbowlz

Ready to run

npx skills add https://github.com/bettercallzaal/ZAOOS --skill fishbowlz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fishbowlz
Source: https://github.com/bettercallzaal/ZAOOS/tree/main/.claude/skills/fishbowlz
Command: npx skills add https://github.com/bettercallzaal/ZAOOS --skill fishbowlz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage the lifecycle of the standalone FISHBOWLZ project by syncing changes from ZAO OS, pushing to GitHub, and deploying to fishbowlz.com.

Core Features & Use Cases

Sync workflow: keep the ZAO OS and standalone repos in lockstep so features, configs, and assets are current.
Deployment automation: push updates to GitHub and trigger a Vercel deployment for production-ready builds.
Cross-project handoff: allow features defined in ZAO OS to be shipped to the standalone site with minimal friction.

Quick Start

Initialize the fishbowlz workflow from ZAO OS to update and deploy the standalone repository.

Frequently Asked Questions about fishbowlz

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

FAQPage Schema

How do I sync changes between a main repository and a standalone site?▼

Vercel deployment is triggered automatically after the Skill pushes synced updates to GitHub, managing the end-to-end build pipeline for the standalone FISHBOWLZ site to ensure production-ready releases.

Can I deploy repository updates to Vercel directly from a sync workflow?▼

Yes, repository updates are deployed to Vercel directly by pushing changes to GitHub, which triggers the production deployment hooks for the standalone site without requiring separate manual build steps.

What is the best way to hand off features from ZAO OS to a standalone project?▼

The best way to hand off features is using the Skill's cross-project handoff mechanism, which syncs configurations and assets from ZAO OS to the standalone repository before executing Git operations and Vercel deployment triggers.

Do I need separate Git commands to push and deploy my standalone project?▼

No, you do not need separate Git commands. The Skill handles Git push operations and Vercel deployment triggers automatically after synchronizing files from ZAO OS to the standalone repository.

Are there limitations when syncing cross-repo configurations for a Vercel deployment?▼

Limitations apply to cross-repo syncing since the Skill is specifically configured for the FISHBOWLZ project and ZAO OS handoff, meaning automated file synchronization and deployment hooks may not generalize to unrelated repository structures.