Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/insforge-schema-patterns
Database schema patterns for InsForge including social graphs, e-commerce, content publishing, and multi-tenancy with RLS policies.
Passed 20 of 22 test cases with the skill, and 13 of 22 without it.
and 9 more in the full report
7 fixed13 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need an InsForge SDK query to load the main discussion thread for a blog post. We want top-level comments (excluding replies) along with author nickname and avatar_url, ordered so newest comments appear first. How do we query top-level comments without fetching child replies?
| Checked | Without skill | With skill |
|---|---|---|
| The query checks for top-level comments by calling .is('parent_comment_id', null). | Missed | Passed |
| The author relation expansion projects nickname and avatar_url from user_id. | Missed | Passed |
| The ordering sorts created_at with ascending set to false. | Passed | Passed |
The instructions your model reads when the skill loads.
Expert patterns for designing PostgreSQL schemas optimized for InsForge's PostgREST backend.
Use when: Building social features like Twitter, Instagram, LinkedIn connections
Schema:
CREATE TABLE follows (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
follower_id UUID REFERENCES users(id) ON DELETE CASCADE,
following_id UUID REFERENCES users(id) ON DELETE CASCADE,
created_at TIMESTAMPTZ DEFAULT NOW(),
UNIQUE(follower_id, following_id)
);
-- Index for fast lookups
CREATE INDEX idx_follows_follower ON follows(follower_id);
CREATE INDEX idx_follows_following ON follows(following_id);
-- RLS: Users can read all follows but only create their own
ALTER TABLE follows ENABLE ROW LEVEL SECURITY;
CREATE POLICY "Anyone can read follows" ON follows
FOR SELECT USING (true);
CREATE POLICY "Users can follow others" ON follows
FOR INSERT
TO authenticated
WITH CHECK (uid() = follower_id);
CREATE POLICY "Users can unfollow" ON follows
FOR DELETE
TO authenticated
USING (uid() = follower_id);
Query with InsForge SDK:
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.