Agent skill

DB Sculptor

by EliasOulkadi in EliasOulkadi/shokunin

Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and…

MITAuto-check: notesDatabases

Install DB Sculptor

skills CLI
$ npx skills add EliasOulkadi/shokunin --skill db-sculptor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install EliasOulkadi/shokunin db-sculptor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/EliasOulkadi/shokunin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.pack/skills/db-sculptor .claude/skills/db-sculptor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
db-sculptor
GitHub stars
114
Token cost
~3.1k tokens
SKILL.md length
953 words
Files
6 (incl. scripts, references, assets)
Skills in repo
49
Repo updated
First seen
Licence
MIT

At a glance

Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and…

  • Works in 5 steps: Model for access patterns → Primary key strategy → Add indexes strategically → …
  • User asks to design schema
  • SKILL.md covers Sub-Commands, Workflow, Error Handling and Production Checklist, plus 3 more sections
  • Runs Shell scripts from its folder

What it does

DB Sculptor is an agent skill from EliasOulkadi/shokunin. Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and sharding/partitioning. Use when user asks to design schema, create migrations, optimize slow queries, add indexes, choose between SQL/NoSQL, or set up Prisma/Drizzle. Do NOT use for data warehouse dimensional modeling, ETL pipeline design, or non-relational (MongoDB, DynamoDB) schema design.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts, reference files and assets (for example `references/index-strategies.md`, `references/migration-patterns.md` and `references/query-optimization.md`). Compatibility notes: opencode

It sits in Databases, covering Query optimization, NoSQL databases and ORMs and data access. It works with Prisma, PostgreSQL, Amazon DynamoDB and MongoDB. The repository describes itself as: 職人 Shokunin 62 AI agent skills for OpenCode, Claude Code, Cursor, Windsurf. ChromaDB memory, MCP servers, declarative self-updates. Multi-model, open source, zero cost. The licence is MIT.

When your agent uses it

  • User asks to design schema
  • Create migrations
  • Optimize slow queries
  • Choose between SQL/NoSQL

Example prompts

  • “/db-sculptor”

Requirements

  • Node.js
  • A Bash shell
  • Compatibility (from SKILL.md): opencode
  • Pre-approved tools (allowed-tools): Read, Bash, Write, Grep

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Model for access patterns
  2. Primary key strategy
  3. Add indexes strategically
  4. Optimize queries
  5. Safe migrations (expand/contract)

What it can do on your machine

Read from SKILL.md and the folder at commit 4c68e5b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Write
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    opencode

    From compatibility in the SKILL.md frontmatter.

Context cost

DB Sculptor loads about 3.1k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 125 tokens; SKILL.md has 953 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~125
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~18k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Write, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from EliasOulkadi/shokunin at commit 4c68e5b, republished under its MIT licence (© EliasOulkadi). 953 words, ~3,112 tokens.

Download SKILL.mdSave it as .claude/skills/db-sculptor/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
db-sculptor
description
Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and sharding/partitioning. Use when user asks to design schema, create migrations, optimize slow queries, add indexes, choose between SQL/NoSQL, or set up Prisma/Drizzle. Do NOT use for data warehouse dimensional modeling, ETL pipeline design, or non-relational (MongoDB, DynamoDB) schema design.
allowed-tools
Read, Bash, Write, Grep
compatibility
opencode
triggers
design database schema, Prisma schema, Drizzle schema, PostgreSQL index, optimize query, EXPLAIN ANALYZE, create migration, zero-downtime migration, database…
negatives
database backup, database administration, data warehouse, ETL pipeline, MongoDB, DynamoDB, non-relational
license
MIT
metadata.workflow
backend
metadata.audience
developers
metadata.version
4.0.0
metadata.author
shokunin

DB Sculptor

Design performant database schemas. Model for access patterns first, normalize later. Based on PostgreSQL internals, Prisma/Drizzle best practices, and production patterns from PlanetScale, Neon, and pganalyze.

Sub-Commands

CommandDescription
designDesign a schema from access patterns and data volume estimates
indexAnalyze queries and recommend/create optimal indexes
optimizeDiagnose slow queries with EXPLAIN ANALYZE and fix them
migrateCreate a safe, zero-downtime migration (expand/contract)
auditAudit existing schema against best practices and anti-patterns

Workflow

Step 1: Model for access patterns
QuestionDetermine
Read/write ratio?How many indexes can the table support
Data volume?Current rows, growth rate/month
Consistency requirements?ACID vs eventual, read replicas OK?
Latency budget?p50 < 5ms, p95 < 50ms, p99 < 200ms

Decision tree:

  • High write volume, simple reads → Normalize (3NF). Minimum indexes.
  • High read volume, complex joins → Denormalize strategically. Add composite + covering indexes.
  • Time-series data → Partition by time (monthly). BRIN indexes on timestamp.
  • Full-text search needed → GIN index with tsvector + tsquery.
  • JSON queries → GIN index on JSONB column.
Step 2: Primary key strategy
PK typeProsConsWhen
UUIDv7Time-sortable, globally unique, no collision riskLarger than bigint (16 bytes vs 8)Default for user-facing. Distributed systems.
UUIDv4Random, globally uniqueNon-sortable = index fragmentationLegacy. Avoid for new schemas.
bigint (auto-increment)Fast, compact, sequentialPredictable, not globally uniqueInternal/analytics tables. Never for user-facing.
ULIDTime-sortable, URL-safe26 charsWhen human-readable time ordering matters.

Default: UUIDv7 for all user-facing tables.

Step 3: Add indexes strategically
Index typeUse caseExample
B-tree (default)Equality, range, sort, ORDER BYCREATE INDEX ON users (email)
CompositeMulti-column WHERE, ORDER BYCREATE INDEX ON orders (user_id, status, created_at DESC)
PartialFiltered queries (WHERE clause)CREATE INDEX ON orders (created_at) WHERE status = 'active'
Covering (INCLUDE)Avoid heap fetchesCREATE INDEX ON users (email) INCLUDE (name, avatar)
GINFTS, arrays, JSONB, trigramCREATE INDEX ON articles USING GIN (to_tsvector('english', body))
GiSTGeometric, range queriesCREATE INDEX ON events USING GiST (tsrange(start_date, end_date))
BRINVery large tables, ordered dataCREATE INDEX ON events USING BRIN (created_at) WITH (pages_per_range = 32)

Rules:

  • Max 3-4 indexes per write-heavy table
  • Order composite columns by selectivity (most selective FIRST)
  • Use partial indexes for common WHERE filters
  • Use INCLUDE for read-heavy queries with small related columns
Step 4: Optimize queries
sql
EXPLAIN (ANALYZE, BUFFERS) SELECT * FROM orders WHERE user_id = 123 AND status = 'active';
Scan typeMeaningFix
Seq ScanReading entire tableAdd index on WHERE columns
Index ScanUsing index + heap lookupGood. Consider covering index.
Index Only ScanUsing index only (no heap)Best. Efficient.
Bitmap Heap ScanMultiple indexes → bitmap → heapOK. Consider composite index.
Nested LoopJoin: outer × innerAdd FK index, or consider hash join
Hash JoinBuild hash table, probePreferred for medium-large joins
sql
-- Slow (~235ms): Seq Scan on 500k rows
-- Fix: composite index
CREATE INDEX CONCURRENTLY idx_orders_user_status
  ON orders (user_id, status, created_at DESC);

-- After fix: Index Only Scan, ~0.3ms

Common optimization patterns:

sql
-- Pattern 1: Function on indexed column → expression index
-- Slow: WHERE LOWER(email) = 'user@example.com'
-- Fix:
CREATE INDEX idx_users_email_lower ON users (LOWER(email));

-- Pattern 2: Missing FK index → Nested Loop join
-- Slow: SELECT * FROM orders JOIN users ON orders.user_id = users.id WHERE users.name = 'Alice'
-- Fix:
CREATE INDEX idx_orders_user_id ON orders (user_id);

-- Pattern 3: ORDER BY + LIMIT without index → full sort
-- Slow: SELECT * FROM events ORDER BY created_at DESC LIMIT 20;
-- Fix:
CREATE INDEX idx_events_created_at ON events (created_at DESC);

-- Pattern 4: COUNT on large table without WHERE → estimated count
-- Slow: SELECT COUNT(*) FROM huge_table;
-- Fix (approximate):
SELECT reltuples::bigint FROM pg_class WHERE relname = 'huge_table';

-- Pattern 5: Pagination with OFFSET → performance degrades
-- Slow: SELECT * FROM items ORDER BY id LIMIT 20 OFFSET 100000;
-- Fix (keyset pagination):
SELECT * FROM items WHERE id > 100000 ORDER BY id LIMIT 20;

-- Pattern 6: Unused indexes bloating writes
-- Identify unused indexes:
SELECT schemaname, tablename, indexname, idx_scan
FROM pg_stat_user_indexes
WHERE idx_scan = 0
ORDER BY pg_relation_size(indexrelid) DESC;

-- Pattern 7: Parallel query for large scans
-- Force parallel workers on large analytical queries:
SET max_parallel_workers_per_gather = 4;
EXPLAIN (ANALYZE, BUFFERS) SELECT ...;
Step 5: Safe migrations (expand/contract)

Prisma example:

prisma
// prisma/schema.prisma
model User {
  id        String   @id @default(uuid()) @db.Uuid
  email     String   @unique
  timezone  String?  // Phase 1: nullable
  createdAt DateTime @default(now()) @map("created_at")
  updatedAt DateTime @updatedAt @map("updated_at")

  @@index([email])
  @@map("users")
}

Drizzle ORM example:

typescript
// db/schema/users.ts
import { pgTable, text, timestamp, uuid, index } from "drizzle-orm/pg-core";

export const users = pgTable("users", {
  id: uuid("id").defaultRandom().primaryKey(),
  email: text("email").notNull().unique(),
  timezone: text("timezone"), // Phase 1: nullable
  createdAt: timestamp("created_at", { withTimezone: true }).defaultNow().notNull(),
  updatedAt: timestamp("updated_at", { withTimezone: true }).defaultNow().notNull(),
}, (table) => ({
  emailIdx: index("idx_users_email").on(table.email),
}));

// Migration command: npx drizzle-kit generate && npx drizzle-kit migrate

Expand/contract SQL:

sql
-- Phase 1 (expand): Add column as nullable
ALTER TABLE users ADD COLUMN timezone text;

-- Phase 2 (backfill): Fill data in separate deployment
UPDATE users SET timezone = 'UTC' WHERE timezone IS NULL;

-- Phase 3 (contract): Make NOT NULL, clean up
ALTER TABLE users ALTER COLUMN timezone SET NOT NULL;

-- Phase 4 (future): Drop old column
ALTER TABLE users DROP COLUMN old_timezone;

Safety rules:

  • CREATE INDEX CONCURRENTLY — never blocks writes
  • lock_timeout = '5s' on migration connections
  • One logical change per migration file
  • Backfill in separate migration from schema change
  • Rollback written BEFORE applying forward
  • Never rename + change type in same migration
PgBouncer connection pooling
ini
# pgbouncer.ini
[databases]
mydb = host=localhost port=5432 dbname=mydb

[pgbouncer]
listen_addr = 0.0.0.0
listen_port = 6432
auth_type = scram-sha-256
auth_file = /etc/pgbouncer/userlist.txt
pool_mode = transaction
default_pool_size = 25
max_client_conn = 200
max_db_connections = 25

Rules:

  • Use pool_mode = transaction (default) for most workloads — session-level pooling breaks SET and LISTEN/NOTIFY
  • Use pool_mode = session only when you need prepared statements, SET session variables, or listen/notify
  • Set max_db_connections to 25-50% of PostgreSQL max_connections — PgBouncer multiplexes client connections
  • Set default_pool_size based on CPU cores: 4× cores for mixed workloads, 1× for CPU-bound
  • Never use pool_mode = statement — breaks multi-statement transactions
Show full SKILL.md (400 more words)Show less

Error Handling

ScenarioCauseFix
Migration lock timeoutLong-running query on same tableSet lock_timeout = '5s'. Run in low-traffic window.
Query slow in prod, fast in devDifferent data volume and distributionTest with prod-size data (~1M+ rows) in staging
CREATE INDEX blocks writesNon-concurrent CREATEAlways use CREATE INDEX CONCURRENTLY
N+1 queriesORM lazy loadingUse eager loading (include/JOIN), DataLoader, or batch queries
Sequence gap on PKROLLBACK increments sequenceAccept gaps. Switch to UUIDv7 for new tables.
DeadlockConflicting lock order across transactionsEnsure consistent lock ordering. Keep transactions short.

Production Checklist

  • Primary key: UUIDv7 or bigint. Never expose sequential PKs in URLs.
  • created_at + updated_at on every table. updated_at auto-set via trigger.
  • Indexes match WHERE + ORDER BY + JOIN columns. Verified with EXPLAIN ANALYZE.
  • Composite indexes ordered by selectivity (most selective first)
  • Partial indexes for common filtered queries
  • Covering indexes (INCLUDE) for read-heavy lookups
  • lock_timeout = '5s' on migration connections
  • Migrations tested on staging with production-like data volume
  • Connection pooling configured (PgBouncer for PostgreSQL)
  • TEXT over VARCHAR(n) — no arbitrary length limits
  • TIMESTAMPTZ over TIMESTAMP — always store with timezone
  • FKs indexed — mandatory for join performance
  • Soft deletes via deleted_at TIMESTAMPTZ (nullable)

Anti-Patterns

Anti-patternFix
No primary keyEvery table needs one (UUIDv7 preferred)
Index on every columnMax 3-4 per write-heavy table. Check usage with pg_stat_user_indexes.
SELECT * in application codeName explicit columns. Avoids breaking changes + unnecessary data transfer.
Functions on indexed columns (WHERE LOWER(email) = ...)Use expression index: CREATE INDEX ON users (LOWER(email))
VARCHAR(255) on all stringsTEXT unless max length is a business rule
Migrations without testingTest against prod copy (anonymized). Never just run on dev.
ENUM type for evolving valuesTEXT with CHECK constraint or reference table
Missing FK indexesEvery FK column needs an index for join performance
Sorting by unindexed column on large tablesAdd composite index with sort column last
COUNT(*) on large tables without WHEREUse estimates: SELECT reltuples FROM pg_class WHERE relname = 'table'

Sources

  • PostgreSQL docs (postgresql.org/docs)
  • Use the Index, Luke! (use-the-index-luke.com)
  • pganalyze EXPLAIN analyzer
  • Prisma migration docs
  • Drizzle ORM docs
  • PlanetScale schema migration patterns
  • Stormatics — composite and partial indexes
  • Neon serverless PostgreSQL patterns

Checklist

  • Skill loads without errors in the AI agent
  • YAML frontmatter is valid (description, compatibility, audience)
  • Workflow section provides clear step-by-step instructions
  • Error handling section covers common failure modes
  • All referenced files (references/, scripts/, assets/) exist
  • Skill triggers correctly for intended use cases
  • No broken links or missing resources

© EliasOulkadi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references, assets) in .pack/skills/db-sculptor of EliasOulkadi/shokunin.

  • SKILL.md
  • assets/prisma-schema.template.prisma
  • references/index-strategies.md
  • references/migration-patterns.md
  • references/query-optimization.md
  • scripts/generate-schema.sh

Open the folder on GitHubat commit 4c68e5b

Compare with similar skills

DB Sculptor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

DB Sculptor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
DB Sculptor this skillEliasOulkadi/shokunin114—~3.1kAutomated safety check: NotesMIT
Discover Databaserand/cc-polymath181—~2kAutomated safety check: PassMIT
Database FundamentalsDanielPodolsky/ownyourcode2901 repos~1.6kAutomated safety check: PassMIT
Database Expertcin12211/orca-q224—~2.8kAutomated safety check: PassMIT
DatabasesMicrock/ordinary-claude-skills404—~1.9kAutomated safety check: NotesMIT
Database Testingpetrkindlmann/qa-skills170—~4.2kAutomated safety check: PassMIT

Similar skills

  • Discover Database

    rand/cc-polymath

    Automatically discover database skills when working with SQL, PostgreSQL, MongoDB, Redis, database schema design, query optimization, migrations, connection pooling, ORMs, or database selection.

    181 GitHub stars~2k tokensUpdated 7 mo ago
    DatabasesAuto-check passed
  • Database Fundamentals

    DanielPodolsky/ownyourcode

    Reviews schema design, SQL queries, ORM patterns. An agent skill from DanielPodolsky/ownyourcode.

    290 GitHub starsUsed in 1 repo~1.6k tokens
    DatabasesAuto-check passed
  • Database Expert

    cin12211/orca-q

    Database performance optimization, schema design, query analysis, and connection management across PostgreSQL, MySQL, MongoDB, and SQLite with ORM integration.

    224 GitHub stars~2.8k tokensUpdated 19 days ago
    DatabasesAuto-check passed
  • Databases

    Microck/ordinary-claude-skills

    Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin).

    404 GitHub stars~1.9k tokensUpdated 1 mo ago
    DatabasesAuto-check: notes
  • Database Testing

    petrkindlmann/qa-skills

    Validate database integrity, test migrations forward and backward, verify schema constraints, manage seed data, detect migration drift, and identify query performance issues.

    170 GitHub stars~4.2k tokensUpdated 4 mo ago
    DatabasesAuto-check passed
  • Prisma Database Setup

    curvenote/curvenote

    Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.).

    170 GitHub starsUsed in 3 repos~1.4k tokens
    DatabasesAuto-check passed

More from EliasOulkadi/shokunin

All 49 skills in this repo
  • CI CD

    EliasOulkadi/shokunin

    Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…

    114 GitHub stars~3.4k tokensUpdated 6 days ago
    Auto-check: notes
  • Component Forge

    EliasOulkadi/shokunin

    Build production-grade components for React, Vue 3, and Svelte 5 with all states (loading, empty, error, success, idle), TypeScript strict, WCAG 2.2 accessibility, server components (RSC), and…

    114 GitHub stars~3.6k tokensUpdated 6 days ago
    Auto-check: notes
  • DB Admin

    EliasOulkadi/shokunin

    PostgreSQL database administration — backup/restore (pgdump, PITR, WAL archiving), health monitoring (connections, bloat, cache hit ratio, dead tuples), connection pooling (PgBouncer), replication…

    114 GitHub stars~2k tokensUpdated 6 days ago
    Auto-check: notes
  • Docker

    EliasOulkadi/shokunin

    Optimize Docker images with multi-stage builds, distroless bases, BuildKit cache mounts, multi-arch builds, compose watch, security hardening (non-root, seccomp, capabilities drop), and…

    114 GitHub stars~3.8k tokensUpdated 6 days ago
    Auto-check: notes
  • Error Handler

    EliasOulkadi/shokunin

    Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead…

    114 GitHub stars~3.6k tokensUpdated 6 days ago
    Auto-check: notes
  • Kubernetes

    EliasOulkadi/shokunin

    Deploy, manage, and debug Kubernetes in production — Deployments, Services, Gateway API, Service Mesh (Istio/Linkerd/Cilium), eBPF observability (Cilium Hubble), security hardening (Pod Security…

    114 GitHub stars~3.3k tokensUpdated 6 days ago
    Auto-check: notes

Categories

Questions about DB Sculptor

What does DB Sculptor do?

Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and…. DB Sculptor is an agent skill from EliasOulkadi/shokunin. Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and sharding/partitioning.

When should I use DB Sculptor?

DB Sculptor fits situations like: user asks to design schema; create migrations; optimize slow queries; choose between SQL/NoSQL.

How do I install DB Sculptor in Claude Code?

Run `npx skills add EliasOulkadi/shokunin --skill db-sculptor -a claude-code`. Or copy the skill folder (.pack/skills/db-sculptor in EliasOulkadi/shokunin) into .claude/skills/db-sculptor in your project. Claude Code loads it when a task matches its description.

How do I install DB Sculptor in Codex?

Run `npx skills add EliasOulkadi/shokunin --skill db-sculptor -a codex`. Or copy the skill folder (.pack/skills/db-sculptor in EliasOulkadi/shokunin) into .agents/skills/db-sculptor in your project. Codex loads it when a task matches its description.

Can I use DB Sculptor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EliasOulkadi/shokunin --skill db-sculptor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/db-sculptor, .gemini/skills/db-sculptor, .github/skills/db-sculptor and .opencode/skills/db-sculptor in your project.

What does DB Sculptor need to run?

Going by SKILL.md and its folder, DB Sculptor needs a shell for the scripts in its folder. Our summary lists: Node.js; A Bash shell. Its frontmatter pre-approves these tools: Read, Bash, Write, Grep. Compatibility (from SKILL.md): opencode.

Does DB Sculptor access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is DB Sculptor safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does DB Sculptor use?

DB Sculptor is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does DB Sculptor use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.

What are the alternatives to DB Sculptor?

Skills that share tags, products or a category with DB Sculptor: Discover Database (rand/cc-polymath, 181 stars), Database Fundamentals (DanielPodolsky/ownyourcode, 290 stars), Database Expert (cin12211/orca-q, 224 stars) and Databases (Microck/ordinary-claude-skills, 404 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains DB Sculptor?

EliasOulkadi (a GitHub user) maintains it in EliasOulkadi/shokunin, which has 114 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 5, 2026.

Source: EliasOulkadi/shokunin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.