portable-schema-generator

Emit Postgres.sql and SQLite.sql from a single schema spec so tools work across both drivers without duplicating DDL by hand. Use when designing a schema that needs to support both shared Postgres deployments and zero-config SQLite. Reduces two-file sync burden to a single source edit.

Zur Installation springen

Repository: Tibsfox/gsd-skill-creator
Letzte Quellaktivität: 4. Juni 2026 um 07:57
Erkannte Sprache von SKILL.md: Englisch
Sterne: 69
Forks: 9

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill portable-schema-generator

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

goal-ambiguity-gate

Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.

2026-07-19

memory-hubness-gate

Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.

2026-07-19

memory-use-warrant

Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.

2026-07-19

Alle aus diesem Repository ansehen

Portable Schema Generator

Two-driver schemas mean two migration files. Hand-keeping them in sync drifts fast. This skill captures the translation rules and the minimal tooling that keeps them aligned.

When to Use

Your tool needs to work on both Postgres and SQLite

You want fresh-project onboarding to be zero-config (SQLite default) while shared-infra deployments keep Postgres

A single schema change should land in both driver files with no manual diff-copying

Core Differences

Concern

Postgres

SQLite

Schemas

CREATE SCHEMA foo; SET search_path TO foo

Namespace-flat — prefix names instead

Autoincrement

BIGSERIAL PRIMARY KEY

INTEGER PRIMARY KEY AUTOINCREMENT

Timestamps

TIMESTAMPTZ DEFAULT now()

TEXT DEFAULT (strftime('%Y-%m-%dT%H:%M:%fZ','now'))

Booleans

BOOLEAN

INTEGER (0/1)

Enums via CHECK

CHECK (col IN ('a','b'))

Same — both support inline CHECK

Foreign keys

On by default

PRAGMA foreign_keys = ON required at connect

Updated-at trigger

CREATE TRIGGER ... EXECUTE FUNCTION touch_updated_at()

CREATE TRIGGER ... BEGIN UPDATE ... END

Cascading drops

ON DELETE CASCADE

Same, but only enforced with foreign_keys = ON

Reserved-word casing

Case-insensitive

Case-insensitive, but be consistent

Translation Rules

When authoring the Postgres version first:

Strip schema prefix for SQLite — CREATE SCHEMA IF NOT EXISTS foo; and SET search_path are removed. Keep bare table names.

Replace BIGSERIAL with INTEGER PRIMARY KEY AUTOINCREMENT.

with ; default becomes .

Portable Schema Generator

Two-driver schemas mean two migration files. Hand-keeping them in sync drifts fast. This skill captures the translation rules and the minimal tooling that keeps them aligned.

When to Use

Your tool needs to work on both Postgres and SQLite

You want fresh-project onboarding to be zero-config (SQLite default) while shared-infra deployments keep Postgres

A single schema change should land in both driver files with no manual diff-copying

Core Differences

Concern

Postgres

SQLite

Schemas

CREATE SCHEMA foo; SET search_path TO foo

Namespace-flat — prefix names instead

Autoincrement

BIGSERIAL PRIMARY KEY

INTEGER PRIMARY KEY AUTOINCREMENT

Timestamps

TIMESTAMPTZ DEFAULT now()

TEXT DEFAULT (strftime('%Y-%m-%dT%H:%M:%fZ','now'))

Booleans

BOOLEAN

INTEGER (0/1)

Enums via CHECK

CHECK (col IN ('a','b'))

Same — both support inline CHECK

Foreign keys

On by default

PRAGMA foreign_keys = ON required at connect

Updated-at trigger

CREATE TRIGGER ... EXECUTE FUNCTION touch_updated_at()

CREATE TRIGGER ... BEGIN UPDATE ... END

Cascading drops

ON DELETE CASCADE

Same, but only enforced with foreign_keys = ON

Reserved-word casing

Case-insensitive

Case-insensitive, but be consistent

Translation Rules

When authoring the Postgres version first:

Strip schema prefix for SQLite — CREATE SCHEMA IF NOT EXISTS foo; and SET search_path are removed. Keep bare table names.

Replace BIGSERIAL with INTEGER PRIMARY KEY AUTOINCREMENT.

with ; default becomes .

name	portable-schema-generator
description	Emit Postgres.sql and SQLite.sql from a single schema spec so tools work across both drivers without duplicating DDL by hand. Use when designing a schema that needs to support both shared Postgres deployments and zero-config SQLite. Reduces two-file sync burden to a single source edit.
format	"2025-10-02T00:00:00.000Z"
version	1.0.0
status	stable
updated	"2026-04-17T00:00:00.000Z"
type	skill
category	gsd-meta
origin	tibsfox
modified	false
first_seen	"2026-04-17T00:00:00.000Z"
first_path	examples/skills/gsd-meta/portable-schema-generator/SKILL.md
superseded_by	null

name	portable-schema-generator
description	Emit Postgres.sql and SQLite.sql from a single schema spec so tools work across both drivers without duplicating DDL by hand. Use when designing a schema that needs to support both shared Postgres deployments and zero-config SQLite. Reduces two-file sync burden to a single source edit.
format	"2025-10-02T00:00:00.000Z"
version	1.0.0
status	stable
updated	"2026-04-17T00:00:00.000Z"
type	skill
category	gsd-meta
origin	tibsfox
modified	false
first_seen	"2026-04-17T00:00:00.000Z"
first_path	examples/skills/gsd-meta/portable-schema-generator/SKILL.md
superseded_by	null

portable-schema-generator

Installationsoptionen

Quelldateien prüfen