.claude/skills/character-create/SKILL.md
# 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
npx skillsauth add pipecat-ai/gradient-bang .claude/skills/character-createInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Creates a new game character for an authenticated user via the public user_character_create edge function.
IMPORTANT: Always ask the user for ALL of these before proceeding. Do NOT assume defaults or use values from CLAUDE.md.
Use AskUserQuestion to ask the user for their email, password, and character name. Do not proceed until you have all three values.
set -a && source .env.supabase && set +a
Call the login edge function to authenticate and get an access token.
curl -s -X POST "${SUPABASE_URL}/functions/v1/login" \
-H "Content-Type: application/json" \
-d '{
"email": "<email>",
"password": "<password>"
}'
Extract the session.access_token from the response. If login fails, report the error and stop.
Call the user_character_create edge function using the access token from step 2.
curl -s -X POST "${SUPABASE_URL}/functions/v1/user_character_create" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <access_token>" \
-d '{
"name": "<character_name>"
}'
Show the user the character_id, name, ship.ship_id, ship.ship_type, ship.current_sector, and ship.credits from the response.
After reporting the result, check if BOT_TEST_CHARACTER_ID exists in .env.bot. If it does, ask the user if they want to update it to the newly created character ID. If yes, replace the value in .env.bot.
The edge function applies these defaults:
kestrel_couriertesting
# 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
development
# 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
devops
# 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 `
data-ai
# 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