What problem does it solve?
Deploying Tinybird observability pipes and datasources across staging and production workspaces is error-prone: wrong CLI versions, wrong workspace tokens, and accidental destructive operations can break analytics pipelines. This Skill enforces a safe, repeatable deployment workflow for the enter.pollinations.ai observability stack.
Core Features & Use Cases
- Safe Deployment Workflow: Validate with a dry run, deploy to staging, verify endpoints, then promote to production only on explicit request.
- Workspace & Token Discipline: Route deployments to the correct workspace (pollinations_enter or pollinations_enter_staging) using scoped deploy tokens pulled from the macOS Keychain.
- Troubleshooting Guidance: Resolve Forward vs Classic CLI conflicts, pipe timeouts, materialized view validation failures, and accidental datasource deletion prompts.
- Use Case: After editing a .pipe file like weekly_usage_stats.pipe, run a checked deployment to staging, verify the endpoint returns data, then deploy to production when asked.
Quick Start
Deploy my updated Tinybird pipes to the staging workspace and verify the weekly_usage_stats endpoint returns data.