Data & Analytics Skill
Airflow DAG Patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and…
$15
Data Weaver
Supabase/Postgres schema, RLS and API engineer
A data engineer for Supabase and Postgres. It designs schemas, writes migrations and RLS policies, closes security gaps, and tunes queries, balancing security and performance together. Every new table ships with row-level security enabled and a policy written, advisor findings get walked down to zero, and slow pages get EXPLAIN-ANALYZE treatment before anyone reaches for a bigger server.
$79 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Agent
- Category Data & Analytics
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Statistics tables are known to lie after a restart, so every claim here gets two independent queries. Schemas ship with RLS enabled by default, and destructive operations follow a three-step ritual: check cascades, snapshot, then execute.
- Loads its data toolkit skill and the binding rules (Supabase client routing, the sales data model, security order) before any SQL is written.
- Scans the real database state first: information_schema for existing tables, pg_policies for current RLS coverage, the Supabase security and performance advisor for open holes. Blind DDL against an unseen schema is forbidden.
- Builds with non-negotiable defaults: every new table gets UUID keys, timestamps, soft delete and RLS ENABLED with at least one policy, no exceptions; migrations are atomic, numbered, carry a written rollback and use CONCURRENTLY for indexes.
- Treats destructive operations as a 3-step ritual: check foreign key CASCADE constraints (a cascade delete flag is a red alarm), snapshot the data as JSON, only then execute and verify row counts afterward.
- Proves every claim with two independent queries: pg_stat statistics alone are known to mislead, so real counts come from SELECT count(*), performance claims from EXPLAIN ANALYZE, security claims from the advisor or an anon-request returning 401.
- Tests each RLS policy in three scenarios (anonymous, normal user, admin), commits migrations through base_tree-safe pushes and returns with command output as evidence, never a bare 'done'.
One power source. 5 lines out.
data-weaver · core
core active · 5 lines
- ✓ designing a new database
Designing a new database schema and migration
- ✓ writing or auditing row
Writing or auditing Row Level Security policies
- ✓ closing a security gap w…
Closing a security gap where anon can read data
- ✓ tuning a slow query with
Tuning a slow query with EXPLAIN ANALYZE
- ✓ architecting an api endp…
Architecting an API endpoint or webhook
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Data that is locked down by default, not leaking to anon
license: perpetual -
Fast queries from proper indexes, not N+1 surprises
license: perpetual -
Migrations that never wipe existing data
license: perpetual -
Security and performance handled in one pass
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Schema design and migrations with RLS enabled on every new table: no exceptions
6 parts · one working system · ships instantly by email
From the field · a real case
This wasn’t written at a desk.
The problem
The fix
The result
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Teams on Supabase/Postgres that need secure, performant data foundations.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
We're on plain Postgres without Supabase. Does this still apply?
Its core, schema design, migrations, RLS policies, and query tuning, is Postgres work, so plain Postgres is squarely in scope. Supabase features layer on top, but the database foundations hold either way.
-
What happens when an RLS policy I need slows a query down?
Balancing security and performance together is the explicit point, so it does not just bolt on a policy and walk away. It weighs the policy against the query cost and tunes both, rather than treating them as separate problems.
-
Does it touch my application code, or only the database layer?
It works at the data layer: schemas, migrations, policies, and queries on Supabase or Postgres. Your API routes and frontend are a separate concern, so pair it with application work when a change spans both.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.