mcpbeat

Ducklake Test

posthog/ducklake-test

Start duckgres with DuckLake (S3-backed storage with PostgreSQL metadata) for local testing. Use when testing duckgres against DuckLake or reproducing Fivetran sync issues.

338 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
160
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/PostHog/duckgres --skill ducklake-test

The instruction itself

as written by the author

Start duckgres with DuckLake configuration:

  • Start dependencies (PostgreSQL metadata store + MinIO object storage):
   docker-compose up -d
  • Kill any existing duckgres process:
   pkill -f duckgres || true
  • Ensure config file exists at duckgres_local_test.yaml:
   host: "0.0.0.0"
   port: 35437
   data_dir: "./data"
   users:
     postgres: "postgres"
   extensions:
     - ducklake
   ducklake:
     metadata_store: "postgres:host=localhost port=5433 user=ducklake password=ducklake dbname=ducklake"
     object_store: "s3://ducklake/data/"
     s3_provider: "config"
     s3_endpoint: "localhost:9000"
     s3_access_key: "minioadmin"
     s3_secret_key: "minioadmin"
     s3_region: "us-east-1"
     s3_use_ssl: false
     s3_url_style: "path"
  • Build and run duckgres:
   go build -o duckgres . && ./duckgres --config duckgres_local_test.yaml
  • Connect with psql (in another terminal):
   PGPASSWORD=postgres psql "host=127.0.0.1 port=35437 user=postgres sslmode=require"

To cleanup: pkill -f duckgres && docker-compose down

How to use it

Copy the folder

Take posthog/ducklake-test from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.