Skills / db-seed
db-seed
Generate realistic, deterministic seed or fixture data for a database from a short spec, as SQL inserts, JSON or CSV, with a seed so reruns match. Use when the user needs sample data, test fixtures or a populated development database. Do not use to copy or anonymize production data.
- Author
- agentsaisle
- Latest
- v0.1.0
- Aisle
- database
- Works with
- Claude Code, Codex, Cursor
- Source
- HazemSalah29/agentsaisle
- Stars
- 2
Install
Install db-seed
npx @agentsaisle/cli add db-seedInstalls into your project's skills folder. Add --global to install it for every project.
Runs scriptsThis skill includes scripts
Your agent may run these scripts on your machine. A maintainer has read every one in full, and the CLI lists the files when you install. You can read them on GitHub first.
Read the files on GitHubAudit
- Critical
- 0
- High
- 0
- Medium
- 1
- Low
- 0
5 files · audited 2026-10-29 · rules 1.0.0
MediumAA-P02Can write files and run interpreters without disable-model-invocation
SKILL.md:6
Read Write Edit Glob Grep Bash(node *)Why The agent may load this skill on its own and then write files and run code in one go.
Fix Set disable-model-invocation: true so the user starts it, or narrow the Bash patterns.
What this skill can use
Tools
- Read
- Write
- Edit
- Glob
- Grep
- Bash(node *)
Scripts
- scripts/seed-data.mjs
Domains mentioned
None
Automated checks found the patterns listed here. An audit reduces risk; it is not a guarantee of safety. How audits work · Read the rules
Show this grade in a README
The badge updates when the registry is rebuilt. Paste this Markdown into the README:
[](https://agentsaisle-vercel.vercel.app/skills/db-seed)SKILL.md
Rendered from commit 276ea59
Database seed data
Use when
- Development or test data is needed, with believable names, emails, dates and relationships.
Don't use when
- The data must come from production. Never copy real personal data; ask the user to follow their own anonymization process.
Steps
- Read the schema (migrations or models) for tables, column types and foreign keys.
- Write a spec file
seed.spec.json: tables, row counts, and a generator per column. Use{ "ref": "table.column" }for foreign keys. Generators: serial, uuid, fullName, firstName, lastName, email, company, city, word, sentence, bool, int, decimal, oneOf, timestamp, date, constant. Seereferences/spec.md. - Run
node <skill>/scripts/seed-data.mjs seed.spec.json --seed 42 --format sql --out seed.sql. The same seed always gives the same rows. - Check the output against the schema: required columns present, uniques not repeated, enum values valid.
- Load it into a development database only, when one is available, and say how.
Budget
- Search first (grep, glob, symbol search). Read line ranges, not whole files.
- Read at most 8 files per step. If you need more, write down what you learned and narrow the question.
- Do not re-read a file you just wrote or edited.
- Prefer the smallest command output that answers the question: head, tail, quiet flags, filtered lists.
- Generate small sets first (10 to 50 rows per table); scale only when asked.
Output
- The spec file, the generated file path, the seed used and the load command.
Done when
- The script runs without errors and the output loads into the schema, when a database is available.
- Re-running with the same seed gives identical output.
- Emails use
example.com; no real people or companies appear.
Version history
| Version | Commit | Install |
|---|---|---|
| 0.1.0latest | 276ea59 | add db-seed |