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.
Works with
---
name: ducklake-test
description: Start duckgres with DuckLake (S3-backed storage with PostgreSQL metadata) for local testing. Use when testing duckgres against DuckLake or reproducing Fivetran sync issues.
license: MIT
---
Start duckgres with DuckLake configuration:
1. Start dependencies (PostgreSQL metadata store + MinIO object storage):
```bash
docker-compose up -d
```
2. Kill any existing duckgres process:
```bash
pkill -f duckgres || true
```
3. Ensure config file exists at `duckgres_local_test.yaml`:
```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"
```
4. Build and run duckgres:
```bash
go build -o duckgres . && ./duckgres --config duckgres_local_test.yaml
```
5. Connect with psql (in another terminal):
```bash
PGPASSWORD=postgres psql "host=127.0.0.1 port=35437 user=postgres sslmode=require"
```
To cleanup: `pkill -f duckgres && docker-compose down`More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

