Close clubs by updating database status and creating a Prisma migration.
npx skills add https://github.com/gioe/laughtrack --skill close-club
Please help me install this Agent Skill. Skill: close-club Source: https://github.com/gioe/laughtrack/tree/main/.agents/skills/close-club Command: npx skills add https://github.com/gioe/laughtrack --skill close-club
Permanently mark defunct clubs as closed in the primary database to prevent them from appearing in active listings, while recording a Prisma migration for audit and version-control purposes.
Invoke the command /close-club with the club's ID or name to permanently close the venue.
High-intent search queries and answers about installing and using this skill.
To permanently close a defunct club in a Prisma database, you update the record by setting status='closed', visible=false, and closed_at=NOW(), and generate a Prisma migration file to audit the schema changes.
Closing a club permanently deactivates it by setting status='closed', visible=false, and closed_at=NOW(), whereas hiding a club only sets visible=false to temporarily remove it from active listings while preserving its status.
You resolve a club target by providing its numeric ID or exact name, which validates the current status to avoid re-closing an already closed venue and records the migration path for audit review.
Yes, closing a club automatically creates a Prisma migration file so the database schema changes are auditable and can be deployed via standard version-control pipelines.
The workflow validates the current status of the club before processing to avoid re-closing an already closed venue, ensuring the database migration only targets active defunct clubs.
The close-club workflow reports the action and provides the migration file location for review after updating the database, ensuring the Prisma migration path is recorded for audit purposes.
gioeResolve SeaTable venue IDs and report health status with show counts.
CleanExpoValidate Prisma schemas and generate reviewed migration SQL for Supabase/PostgreSQL.
gioeHide a club by setting visible to false and creating a Prisma migration.
gioeQuery the SeatEngine API to categorize scraped clubs as Healthy, Empty, Dead, or Errors.
