Add demo accounts and starter content to production
Fill a production app with demo accounts and starter content safely, through its own API or CLI instead of raw database inserts. Validation and audit logs run as for any user. Idempotent scripts with a dry run, short-lived tokens in a private file, a cleanup step that revokes them, and a guard that shows which database you are about to write to. Never prints tokens.
- Activity
- New: be the first to try it
Will this work for me?
- Effort
- Needs about 10 minutes of setupOur guess from what the kit says it needs.
- Works in
- Claude Code, claude.ai and the desktop app
- You need
PostgreSQL account: setup steps
- What it is
- This kit works with your own PostgreSQL account.
- Where to get it
- Sign in to PostgreSQL, or make a free account if it offers one.
Safety label
- Who made it
How this works
- It is a skill: written instructions Claude reads when your request matches what the skill is for. You do not call it by name; just ask for the task.
- While it works, it reads files in the places it lists, nowhere else.
- It runs these commands on your computer: node scripts/seed-guard.mjs.
- Nothing runs until you choose to use it, and you can remove it any time.
What it can access
What this kit says it will touch, the same list you see before you add it. These are its Permissions: What a kit is allowed to touch on your computer or accounts, such as reading a folder or using the internet. You see them before you add it.. In Claude Code they become rules, so Claude stops anything not on the list.
Command
Runs the command: node scripts/seed-guard.mjs (with any arguments, without asking)
Reads
Reads files in ./examples/**
- Works with
- Claude Code
- License