byarchestra-ai· 19 skills
Use BEFORE writing or running any Drizzle migration that touches the interactions table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a write-blocking lock and stall the proxy. Covers which operations are safe vs table-rewriting/lock-taking, the "never rebuild an index in a transactional migration" rule, and a read-only audit procedure against the GKE staging database to size the risk first.
$npx -y skills add archestra-ai/archestra --skill archestra-dev-interactions-migrationsInstalls into the current project.
Run `npx skills use "https://github.com/archestra-ai/archestra" --skill "archestra-ai/archestra/archestra-dev-interactions-migrations"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/archestra-ai/archestra" that are relevant to the current task. Run `npx skills add "https://github.com/archestra-ai/archestra"` and select the relevant skills, then follow their instructions.