What you get
It checks the official changelog before writing, rather than trusting training data.
Supabase's Two Skills
Added 2026-08-06There are only two: one for Supabase itself, one for Postgres best practice. The latter's reference directory holds 34 documents, grouped into eight impact classes with priorities marked.
The first principle is do not trust the training data — pull the official changelog and scan for breaking-change tags first. The third is fixed: stop after the same approach fails two or three times, do not loop. The security checklist names Supabase-specific traps: user_metadata is user-editable and must never enter an RLS authorisation decision, app_metadata is the one to use; deleting a user does not invalidate access tokens already issued. The build script is a stopgap the author plans to replace once the official Action lands.