Index of every page on this site: llms.txt
All skills
dosco avatar

/add-graphjin-database

@ffd0367
by Spacydosco/graphjin3.2k stars
206
Run it yourself

Use when adding a new GraphJin database, warehouse, or CQL/NoSQL backend; building a simulator because no live service is available; wiring a dialect, discovery, tests, scripts, README/CONFIG/FEATURES, or website database support surfaces.

  • 3 files
  • 7.2 KB
  • Updated 4 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/dosco/graphjin/add-graphjin-database

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈66 tokens for metadata: the name and description. ≈868 when used: this file. ≈902 more on demand in 2 files.

Description uses 3.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈263 characters, or 3.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Add GraphJin Database

Use this skill to add a database end to end without leaving half-public support behind. GraphJin is a compiler, not a resolver stack: push behavior into dialect, discovery, schema metadata, and tests.

Workflow

  1. Ground in docs and repo truth.

    • Read the database's official SQL, DDL, type, catalog, and limitations docs before coding.
    • Inspect existing GraphJin seams: config validation, dialect factory, introspection, tests/dbint_test.go, hosted emulators, scripts, README, CONFIG, FEATURES, and website components.
    • Decide and state the public support level: experimental queries, mutations, subscriptions, full support, or simulator-only.
  2. Build a simulator first when live service access is unavailable or slow.

    • Add tests/hostedemu/<db> and tests/<db>emu around hostedemu.NewConnector.
    • Add tests/<db>.sql using database-native DDL, types, constraints, and metadata features.
    • Keep parser/translator code owned by the target database. Reuse hosted emulator patterns, not another database's grammar, unless docs prove the syntax is identical.
    • Translate setup and discovery into DuckDB, but expose the database's real discovery surfaces.
    • Add parser, type mapping, metadata, discovery, wrapper, default-fixture, and large-catalog tests.
  3. Use the simulator to build public support.

    • Register the DB type in core/config.go, the psql dialect factory, subscription dialect lookup, introspection switches, and schema-DDL/diff code if public DDL support is claimed.
    • Add a DB-owned dialect. Inherit behavior only after target-specific tests prove it.
    • Add discovery using the docs-recommended catalog path first, with fallbacks only where needed.
    • Wire tests/dbint_test.go, focused skip helpers for unsupported features, and scripts/test-<db>.sh.
    • Keep GraphJin's collision-free managed artifact SQLite database runtime-only. Its identifier is allocated at startup and must never become an application source, primary database candidate, catalog source, or security-report database.
  4. Update public surfaces only after the runtime is wired.

    • Update README, CONFIG, FEATURES, website database logos/frontpage copy, website database matrix, and test-parallel scripts.
    • If the database uses graphjin serve new --db-url, update the URL parser and the rendered cmd/tmpl/prod.yml and cmd/tmpl/agentic.yml sources. Verify a real generated app loads without test-only placeholder replacement.
    • Make feature claims match tests. Use "experimental" and "query/discovery only" when writes, subscriptions, GIS, full-text, or migrations are not verified.
    • Preserve unrelated dirty worktree edits. Patch on top; never revert user changes.
    • Do not add artifact, watch, agent, stateful-MCP, or primitive-tool enablement to new dev.yml / agentic.yml examples; parsed mode defaults already provide them. Configure an artifact source only when documenting a shared clustered store.
  5. Verify and leave evidence.

    • Run simulator tests, dialect/introspection tests, the new scripts/test-<db>.sh, and affected shared suites.
    • If shared compiler or introspection code changed, run existing dialect scripts likely to be affected.
    • Before finalizing, recheck docs/website claims against the support level that actually passed.

References

  • Read references/checklist.md for the detailed implementation checklist and Redshift-specific notes.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at ffd0367. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 months ago

README badge

README badge for dosco/graphjin/add-graphjin-database