specialist-seed

Generates idempotent SQL seed data for Supabase specialist profiles in local development.

Updated May 1, 2026
One-click install
npx skills add https://github.com/RomeroSilvia/Eos --skill specialist-seed-romerosilvia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specialist-seed
Source: https://github.com/RomeroSilvia/Eos/tree/main/agents/skills/specialis-seed
Command: npx skills add https://github.com/RomeroSilvia/Eos --skill specialist-seed-romerosilvia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers testing specialist verification flows (M3/M4/M5) need realistic test accounts with different license statuses, but creating them manually through the app is slow and repetitive. ## Core Features & Use Cases - Seed Data Generation: Creates SQL inserts for profiles and specialist_profiles tables covering pending, rejected (with rejection_reason), and verified specialists. - Safe Fake Data: Enforces clearly fake emails (e.g., [email protected]) and fake license numbers (e.g., MAT-PENDING-0001) so no real personal data ever enters the database. - Idempotent Seeds: Prefers fixed UUIDs and idempotent statements so tests can reference the same records consistently across runs. - Use Case: A developer setting up a local Supabase instance needs to test the admin license-verification flow; this Skill produces a seed file with one pending, one rejected, and one verified specialist ready to insert. ## Quick Start Ask the assistant to generate a local Supabase seed SQL file with pending, rejected, and verified specialist accounts for development testing.

Frequently Asked Questions about specialist-seed

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Supabase seed data for testing user roles?

Write SQL inserts into the profiles and specialist_profiles tables using fixed UUIDs and clearly fake emails. Make the statements idempotent so the seed can run repeatedly without duplicate key errors.

How to test specialist license verification flows locally?

Seed one specialist per license_status value: pending, rejected (including a rejection_reason), and verified. This lets you exercise approval and rejection paths without manual account setup.

Should seed data go inside a database migration file?

No, seed data should live in a separate development seed or documentation file, not inside the E2 migration, unless explicitly requested. This keeps production migrations clean of test fixtures.

Can I use real personal data in development seed files?

No, never include real DNI numbers, real license numbers, or real personal data in seeds. Use obviously fake values like [email protected] and MAT-PENDING-0001 to avoid leaking sensitive information.

Why use fixed UUIDs in SQL seed scripts?

Fixed UUIDs let tests and other seed records reference the same rows consistently across runs. They also make idempotent upserts straightforward since the primary keys are known in advance.