Skill

sql

Guides SQL query writing, schema design, migrations, and best practices for SQLite databases, including strict tables, prefixed IDs, timestamps, triggers. Useful for SQLite and Go-SQLite code.

SQL

SQLite

database

npx claudepluginhub maragudk/fabrik --plugin fabrik

Tool Access

This skill uses the workspace's default tool permissions.

Preview

This skill provides guidance for working with SQLite databases. It covers query writing, schema design, and SQLite-specific best practices.

SKILL.md

Similar Skills

cache-components

139.4k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

pdf

131.6k

Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.

11 files

document-skills

Stats

Stars7

Forks0

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

SQL

Overview

This skill provides guidance for working with SQLite databases. It covers query writing, schema design, and SQLite-specific best practices.

When to Use This Skill

Use this skill when:

Writing SQL queries for SQLite databases

Analyzing or optimizing existing queries

Designing database schemas

Creating database migrations

Working with Go code that interacts with SQLite

SQLite Best Practices

Query Writing

ALWAYS write lowercase queries. Uppercase queries make me sad.

Prefer select * over explicit column names

Prefer CTEs over long nested subqueries

Schema Design

ALWAYS use strict tables

ALWAYS write timestamps like this: strftime('%Y-%m-%dT%H:%M:%fZ')

Time modifications should also use strftime

Usually start with the primary key, which is usually defined like this: id text primary key default ('p_' || lower(hex(randomblob(16)))) (where the p_ is a prefix depending on the table name; two-letter prefixes are okay too, so the prefix is unique among tables)

After the primary key come created/updated columns like this: created text not null default (strftime('%Y-%m-%dT%H:%M:%fZ'))

Updated timestamps are automatically updated with a trigger like this:

create trigger table_name_updated_timestamp after update on table_name begin
update table_name set updated = strftime('%Y-%m-%dT%H:%M:%fZ') where id = old.id;
end;

SQL

Overview

This skill provides guidance for working with SQLite databases. It covers query writing, schema design, and SQLite-specific best practices.

When to Use This Skill

Use this skill when:

Writing SQL queries for SQLite databases
Analyzing or optimizing existing queries
Designing database schemas
Creating database migrations
Working with Go code that interacts with SQLite

SQLite Best Practices

Query Writing

ALWAYS write lowercase queries. Uppercase queries make me sad.
Prefer select * over explicit column names
Prefer CTEs over long nested subqueries

Schema Design

ALWAYS use strict tables
ALWAYS write timestamps like this: strftime('%Y-%m-%dT%H:%M:%fZ')
Time modifications should also use strftime
Usually start with the primary key, which is usually defined like this: id text primary key default ('p_' || lower(hex(randomblob(16)))) (where the p_ is a prefix depending on the table name; two-letter prefixes are okay too, so the prefix is unique among tables)
After the primary key come created/updated columns like this: created text not null default (strftime('%Y-%m-%dT%H:%M:%fZ'))

Updated timestamps are automatically updated with a trigger like this:

create trigger table_name_updated_timestamp after update on table_name begin
update table_name set updated = strftime('%Y-%m-%dT%H:%M:%fZ') where id = old.id;
end;