pipecat-ai
13 verified skills689 total stars
.claude/skills/deploy
# Deploy Full deployment: edge functions then bot. ## Parameters The user specifies the environment as an argument: `/deploy dev` or `/deploy prod`. If not provided, ask which environment. ## Steps 1. Run the `/deploy-functions` skill 2. Run the `/deploy-bot <env>` skill with the same environment
development53
.claude/skills/character-create
# Create Character Creates a new game character for an authenticated user via the public `user_character_create` edge function. ## Parameters IMPORTANT: Always ask the user for ALL of these before proceeding. Do NOT assume defaults or use values from CLAUDE.md. - **Email**: user email (required) - **Password**: user password (required) - **Name**: character name (required, 3-20 chars, alphanumeric/underscores/spaces) ## Steps ### 1. Ask the user Use AskUserQuestion to ask the user for the
data-ai53
.claude/skills/npc
# NPC Runs an autonomous AI task agent as a game character. Resolves a character name to its UUID, then launches the `npc-run` script which connects to the game server and executes the given task using a Pipecat + Gemini LLM pipeline. ## Parameters - **character_name** (required): The character's display name (e.g. `JOETRADER`). Passed as the argument to `/npc`. - **task** (required): A natural language description of what the character should do (e.g. "Explore and find 5 new sectors"). If `
devops53
.claude/skills/reset-world
# Reset World Resets the game database, generates a fresh universe, loads quest definitions, and seeds combat cron config. ## Parameters The user specifies the environment as an argument: `/reset-world local`, `/reset-world dev`, or `/reset-world prod`. If not provided, ask which environment. - `local` → env file: `.env.supabase` - `dev` → env file: `.env.cloud.dev` - `prod` → env file: `.env.cloud` Additional optional parameters (ask if not provided, or use defaults): - **Sector count**: n
development53
.claude/skills/combat
# Combat Initiates a combat encounter for testing. Calls the `combat_initiate` edge function to start combat in the sector of a given character/ship. ## Parameters - **target** (required): Either a character name (e.g. `JOETRADER`) or a ship UUID to initiate combat from that ship's character. If not provided, ask the user for a character name or ship ID. ## Steps ### 1. Source environment variables ```bash set -a && source .env.supabase && set +a ``` ### 2. Resolve the character and ship
testing53
.claude/skills/load-quests
# Load Quest Data Loads quest definitions from JSON files in `quest-data/` into Supabase. ## Parameters Ask the user for: - **Mode**: `upsert` (default) or `force` (deletes all existing quest data first) - **Dry run**: whether to validate only without writing (default: no) ## Steps ### 1. Source environment variables ```bash set -a && source .env.supabase && set +a ``` ### 2. Run the quest loader Upsert mode (default — updates existing quests, inserts new ones): ```bash uv run -m gradien
testing53
.claude/skills/deploy-bot
# Deploy Bot Deploys the bot to Pipecat Cloud using cloud builds. ## Parameters The user specifies the environment as an argument: `/deploy-bot dev` or `/deploy-bot prod`. If not provided, ask which environment to deploy to. - `dev` → config file: `deployment/pcc-deploy.dev.toml` - `prod` → config file: `deployment/pcc-deploy.prod.toml` ## Steps ### 1. Deploy to Pipecat Cloud ```bash pipecat cloud deploy --config-file deployment/pcc-deploy.<env>.toml --yes ``` The `--yes` flag skips all
development53
.claude/skills/deploy-functions
# Deploy Supabase Functions Deploys all Supabase edge functions. ## Parameters The user specifies the environment as an argument: `/deploy-functions dev` or `/deploy-functions prod`. If not provided, ask which environment. - `dev` → env file: `.env.cloud.dev` - `prod` → env file: `.env.cloud` ## Steps ### 1. Source environment variables and deploy ```bash set -a && source <env-file> && set +a && npx supabase functions deploy --workdir deployment/ --no-verify-jwt ``` ### 2. Verify Confir
development53
.claude/skills/init
# Init — Full Project Setup from Scratch Sets up the entire Gradient Bang local development environment from a fresh clone. ## Prerequisites Before running this skill, the user must have: - **Docker** running - **uv** installed - **Node.js 18+** installed - **pnpm** installed Verify these are available before proceeding. If any are missing, tell the user what to install and stop. ## Steps ### 1. Install Python dependencies ```bash uv sync --all-groups ``` ### 2. Start the local Supabase
development53
.claude/skills/migrate
# Run Database Migration Applies pending Supabase migrations to the local or production database. This skill is strictly additive — it only applies new migrations and NEVER resets, truncates, or drops existing data. ## Safety rules — READ BEFORE PROCEEDING **You MUST follow every rule below. No exceptions.** 1. **NEVER** run `supabase db reset`, `supabase db reset --linked`, or any command that drops/recreates the database. 2. **NEVER** run `DROP TABLE`, `DROP SCHEMA`, `TRUNCATE`, or `DELETE
data-ai53
.claude/skills/analyze-context
# Analyze Context Analyzes a gameplay session context dump from Gradient Bang. Summarizes agent activity and, if the user reports a problem, identifies where it occurred and scans source code for the root cause. ## Parameters - **context** (required): The gameplay session context dump (paste inline or provide a file path). - **problem** (optional): A description of what went wrong during the session. ## Steps ### 1. Receive input The user provides a context dump, either inline in the messa
development53
.claude/skills/destroy-ship
# Destroy Ship Destroys a corporation ship for testing. Performs the full end-to-end flow: database soft-delete, pseudo-character cleanup, and `ship.destroyed` event emission so connected clients update in real-time. Uses the Supabase REST API and existing `record_event_with_recipients` RPC — no new edge functions required. ## Parameters Ask the user for: - **ship_id**: UUID of the ship to destroy (required) ## Steps ### 1. Source environment variables ```bash set -a && source .env.supaba
tools53
.claude/skills/restore-ship
# Restore Ship Restores a ship to a healthy state for testing. Clears the `destroyed_at` flag, restocks fighters/shields/warp power to max values from the ship definition, re-adds corporation ships to `corporation_ships` if missing, and recreates the pseudo-character record for corp ships so tasks can be issued. No events are emitted — this is a database-only operation. ## Parameters Ask the user for: - **ship_id**: UUID of the ship to restore (required) ## Steps ### 1. Source environment
testing53