agentleFS
Sign inStart free
PostHogKnown publisherPostHog/duckgres/.claude/skills/ducklake-test/SKILL.md

ducklake-test

Skill189 starsChanged 9 months agoMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start duckgres with DuckLake configuration:

    line 6
  2. Distinctive:

    Start dependencies (PostgreSQL metadata store + MinIO object storage):

    line 8
  3. Very specific:

    Ensure config file exists at duckgres_local_test.yaml:

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Start duckgres with DuckLake configuration:

  1. Start dependencies (PostgreSQL metadata store + MinIO object storage):
    docker-compose up -d
  2. Kill any existing duckgres process:
    pkill -f duckgres || true
  3. 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"
  4. Build and run duckgres:
    go build -o duckgres . && ./duckgres --config duckgres_local_test.yaml
  5. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free