agentleFS
MohamedRamadanSalahMohamedRamadanSalah/claude-qa-toolkit/.claude/skills/test-data/SKILL.md

test-data

Skill0 starsChanged 17 days agoMITView on GitHub

Generate realistic test data — users, products, orders as CSV/JSON/SQL files, including edge-case values (unicode, boundaries, injection strings). Use when the user needs test data, dummy data, or data files for testing.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask only what's not obvious: entity type, how many rows, and format (CSV / JSON / SQL).

    line 12
  2. Distinctive:

    NEVER generate real personal data.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Data Generator

A ready-made Python generator does the accurate work. DO NOT hand-write rows of data — run the script.

Workflow (mandatory)

  1. Ask only what's not obvious: entity type, how many rows, and format (CSV / JSON / SQL).
  2. Run the generator:
python .claude/skills/test-data/scripts/generate_data.py --type users --count 50 --format csv --out test-data/users.csv
  • --type: users | products | orders
  • --format: csv (Excel-friendly, UTF-8 BOM) | json | sql (add --table <name>)
  • --seed <n>: same seed → identical data every run (default 1234)
  • --no-edge-cases: plain data only

By default the script APPENDS edge-case rows (marked in the _note column): empty/max-length strings, unicode + Arabic RTL text, SQL/XSS probe strings, zero/negative/huge numbers, leap day and invalid dates. Tell the user these rows exist and what they are for.

  1. Show the user the script's output line (row counts + file path) and the first few rows of the file.

If the user needs an entity the script doesn't have

(e.g. patients, invoices, bookings): copy the pattern in generate_data.py — add a make_<entity> function and register it in MAKERS, then run it. Keep it stdlib-only, keep the _note column, keep emails on @example.com and phones in the fake 555 range.

Hard rules

  • NEVER generate real personal data. For credit cards use official test numbers only (e.g. Stripe's 4242 4242 4242 4242).
  • Output files always go in the test-data/ folder.
  • For a quick copy-paste list of nasty input strings (no file), just print the EDGE_STRINGS list from the script.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.