cf-switch-backendlisted

Switch ContentForge's tracking and delivery backend between Google Sheets + Drive, Airtable, and local filesystem — guiding credential setup, verifying access, optionally migrating existing tracking records and output files (migration is additive and never deletes source data), and updating tracking.backend in the brand profile so the next run uses it immediately. Triggers on "/contentforge:cf-switch-backend", "switch tracking to Airtable", "move tracking to Google Sheets", "which backend am I using", "migrate my tracking data". Runs backend-migrator.py, sheets-tracker.py, airtable-tracker.py, or local-tracker.py; --status reports current backend health. Pairs with /contentforge:cf-cowork-setup for the Cowork Drive route and /contentforge:cf-style-guide, whose Step G sets the initial backend.
teachskillofskills-ai/ContentForge-techshu · ★ 1 · API & Backend · score 78

Install: claude install-skill teachskillofskills-ai/ContentForge-techshu

# Switch Tracking Backend Switch ContentForge's tracking and delivery backend between **Google Sheets + Drive**, **Airtable**, or **Local filesystem**. Optionally migrate existing tracking data and output files to the new backend. ## When to Use - Switching from local (default) to a cloud backend for collaboration - Migrating from Google to Airtable (or vice versa) for simpler auth - Downgrading to local when cloud access isn't needed - Checking current backend status before switching **Running in Cowork?** The "local" backend writes to the ephemeral sandbox filesystem — files vanish at session end. For Cowork team setups, use the Google (Drive) route and run `/contentforge:cf-cowork-setup` first to wire the Drive folder layout. ## How to Use ``` /contentforge:cf-switch-backend airtable /contentforge:cf-switch-backend google_sheets /contentforge:cf-switch-backend local /contentforge:cf-switch-backend --status ``` ## What This Command Does ### Step 1: Identify Current Backend Read the active brand profile's `tracking.backend` field. Report current state: ``` Current backend: local Records: 47 tracking records (~/.claude-marketing/{brand}/tracking/tracking.json) Output files: 42 files in ~/.claude-marketing/{brand}/outputs/{YYYY}/{MM}/ ``` ### Step 2: Validate Target Backend **If switching to Airtable:** 1. Check `AIRTABLE_TOKEN` environment variable exists 2. If missing, guide through setup: - Go to [airtable.com/create/tokens](https://airtable.com/create/tokens