Design and generate Convex database schemas with proper validation, indexes, and relationships.
Works with
Provides schema templates and patterns for one-to-many, many-to-many, and hierarchical relationships using ID references instead of nesting
Includes validator reference for all Convex types ( v.string() , v.id() , v.union() , etc.) and guidance on when to use arrays versus relational structures
Covers index strategy with single-field and compound index examples for common query patterns
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionschema-builderExecute the skills CLI command in your project's root directory to begin installation:
Fetches schema-builder from get-convex/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate schema-builder. Access via /schema-builder in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
21
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
21
stars
Build well-structured Convex schemas following best practices for relationships, indexes, and validators.
convex/schema.ts filev.* typesimport { defineSchema, defineTable } from "convex/server";
import { v } from "convex/values";
export default defineSchema({
tableName: defineTable({
// Required fields
field: v.string(),
// Optional fields
optional: v.optional(v.number()),
// Relations (use IDs)
userId: v.id("users"),
// Enums with union + literal
status: v.union(
v.literal("active"),
v.literal("pending"),
v.literal("archived")
),
// Timestamps
createdAt: v.number(),
updatedAt: v.optional(v.number()),
})
// Index for queries by this field
.index("by_user", ["userId"])
// Compound index for common query patterns
.index("by_user_and_status", ["userId", "status"])
// Index for time-based queries
.index("by_created", ["createdAt"]),
});
export default defineSchema({
users: defineTable({
name: v.string(),
email: v.string(),
}).index("by_email", ["email"]),
posts: defineTable({
userId: v.id("users"),
title: v.string(),
content: v.string(),
}).index("by_user", ["userId"]),
});
export default defineSchema({
users: defineTable({
name: v.string(),
}),
projects: defineTable({
name: v.string(),
}),
projectMembers: defineTable({
userId: v.id("users"),
projectId: v.id("projects"),
role: v.union(v.literal("owner"), v.literal("member")),
})
.index("by_user", ["userId"])
.index("by_project", ["projectId"])
.index("by_project_and_user", ["projectId", "userId"]),
});
export default defineSchema({
comments: defineTable({
postId: v.id("posts"),
parentId: v.optional(v.id("comments")), // null for top-level
userId: v.id("users"),
text: v.string(),
})
.index("by_post", ["postId"])
.index("by_parent", ["parentId"]),
});
export default defineSchema({
users: defineTable({
name: v.string(),
// Small, bounded collections are fine
roles: v.array(v.union(
v.literal("admin"),
v.literal("editor"),
v.literal("viewer")
)),
tags: v.array(v.string()), // e.g., max 10 tags
}),
});
// Primitives
v.string()
v.number()
v.boolean()
v.null()
v.id("tableName")
// Optional
v.optional(v.string())
// Union types (enums)
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
erichowens/some_claude_skills
Useful defaults in schema-builder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
schema-builder has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for schema-builder matched our evaluation — installs cleanly and behaves as described in the markdown.
schema-builder reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in schema-builder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
schema-builder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
schema-builder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend schema-builder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
schema-builder reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend schema-builder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 74