Install any skill in seconds. Free to start, no credit card required.
Get Started Free →bybren-llc/migration-patterns
Database migration creation with mandatory RLS policies and ARCHitect approval workflow.
Passed 23 of 25 test cases with the skill, and 12 of 25 without it.
and 18 more in the full report
12 fixed11 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We created table user_bookmarks with primary key id and column user_id. We enabled RLS and created SELECT policies. What database GRANT statement is required at the end of this migration file?
| Checked | Without skill | With skill |
|---|---|---|
| Includes GRANT statement specifying SELECT, INSERT, and UPDATE permissions to {{PROJECT}}_app_user. | Missed | Passed |
The instructions your model reads when the skill loads.
Guide database migration creation with mandatory RLS policies, following security-first architecture and approval workflow.
-- FORBIDDEN: RLS policies in separate file
-- RLS MUST be in the same migration.sql file as the table creation
-- FORBIDDEN: Table without RLS
CREATE TABLE user_data (...);
-- Missing: ALTER TABLE user_data ENABLE ROW LEVEL SECURITY;
-- FORBIDDEN: Resolve applied migrations
npx prisma migrate resolve --applied "migration_name"
-- This bypasses migration verification
-- FORBIDDEN: Missing user_id index
CREATE TABLE payments (...);
-- Missing: CREATE INDEX idx_payments_user_id ON payments(user_id);
-- FORBIDDEN: Schema changes without ARCHitect approval
-- All migrations require approval before PR
test cases passed, vs 12 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.