.claude/skills/load-quests/SKILL.md
# 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
npx skillsauth add pipecat-ai/gradient-bang .claude/skills/load-questsInstall 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.
Loads quest definitions from JSON files in quest-data/ into Supabase.
Ask the user for:
upsert (default) or force (deletes all existing quest data first)set -a && source .env.supabase && set +a
Upsert mode (default — updates existing quests, inserts new ones):
uv run -m gradientbang.scripts.load_quests_to_supabase --from-json quest-data/
Force mode (wipes all quest definitions and reloads from scratch):
uv run -m gradientbang.scripts.load_quests_to_supabase --from-json quest-data/ --force
Dry run (validate JSON files without writing to database):
uv run -m gradientbang.scripts.load_quests_to_supabase --from-json quest-data/ --dry-run
Confirm the output shows "Success!" and check the stats summary for expected quest/step/subscription counts.
.json file in quest-data/ represents one quest chain. The loader picks up all *.json files in the directory.code, so it's safe to re-run after editing quest data.--force deletes ALL quest definitions (cascades to steps and subscriptions) before reloading. Player quest progress (player_quests, player_quest_steps) is NOT affected — but orphaned progress rows will reference deleted step IDs.docker exec supabase_db_gb-world-server psql -U postgres -d postgres -c "NOTIFY pgrst, 'reload schema'" then retry.testing
# 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