dev-setup

A setup and diagnostic tool for preparing an OpenMetadata development checkout on macOS or Linux. It checks or installs tools such as Java, Maven, Node, Yarn, Python, and Docker, then prepares the project environment.

In plain words
What is it for?
Use it for a fresh setup, environment repair, dependency and model generation setup, or a read-only check of an existing checkout.
Why use it?
It removes much of the manual work after cloning the project or creating a separate worktree. It also helps explain failures caused by missing or incompatible tool versions.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/open-metadata/openmetadata/dev-setup
Any agent
npx skills add open-metadata/OpenMetadata --skill dev-setup
Clone the repo
git clone --depth 1 https://github.com/open-metadata/OpenMetadata

Made for: Claude Code, Codex.

Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,164 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00105 $0.02164
Opus 5 $0.00053 $0.01082
Sonnet 5 $0.00021 $0.00433
Haiku 4.5 $0.00011 $0.00216

Measured yesterday against content hash 5e9185199460, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

dev-setup scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

`sudo systemctl enable --now docker` and `sudo usermod -aG docker $USER`, then log out and
skills/dev-setup/SKILL.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dev Environment Setup

Bring a checkout from "just cloned" to "can build the backend, the UI, and the ingestion framework" with one call.

When to Activate

  • "set up my dev environment", "onboard me", "I just cloned this repo"
  • "set up this worktree" (a Claude Code worktree does not inherit the main repo's venv)
  • A build fails on a missing or wrong-version tool: antlr4: command not found, class file has wrong version, Unsupported engine … node, ModuleNotFoundError: metadata.generated
  • "check my environment", "why doesn't make generate work"

The One Call

./scripts/dev_setup.sh          # or: make dev_setup

Everything is idempotent — re-running skips what is already correct. Useful flags (pass through the Makefile as make dev_setup ARGS="--slim -y"):

Flag Effect
--check Diagnose only, change nothing. Returns nonzero when issues are found. Always start here on an existing checkout.
--slim Install ingestion[dev] instead of [all-dev-env]. Minutes instead of tens of minutes; omits most connector deps. Right choice unless the work touches a specific connector.
-y Non-interactive (assumes yes for Homebrew/nvm/Docker prompts).
--with-build Also runs mvn clean install -DskipTests -T 1C.
--with-docker Also starts docker/development/docker-compose.yml.
--skip-tools Verify system packages instead of installing them (no sudo/brew writes).
--skip-python / --skip-ui / --skip-generate / --skip-precommit Skip that phase.
--python <bin> Force the interpreter the venv is built from.

Process

Step 1 — Diagnose before changing anything

./scripts/dev_setup.sh --check

Read the warnings. They name the exact missing piece; do not install anything the check reports as already present.

Step 2 — Choose the depth

  • Backend/UI work only, or a new worktree → ./scripts/dev_setup.sh --slim -y
  • Connector or ingestion work → ./scripts/dev_setup.sh -y (full [all-dev-env])
  • Ask the user before running the full install if they are on a metered/slow link — it downloads every connector's dependencies.

Read the full file on GitHub · 172 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 172 lines · 105 tokens per session scan B 5e9185199460

Subscribe to this mod's changes

dev-setup is a skill published in the GitHub repository open-metadata/OpenMetadata (15,032 stars, last pushed yesterday), licensed Apache-2.0. It adds 105 tokens to every session and 2,164 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

test-review

You are an expert DataHub test reviewer. Your role is to evaluate smoke tests and integration tests against established testing standards, identify issues, and provide actionable feedback.

datahub-project/datahub · 0 tokens

oss-fuzz

Run Tika's OSS-Fuzz Jazzer targets locally against a working-tree checkout — build the image, build fuzzers from local source, fuzz a target, run a corpus as a regression pass, reproduce a crash, and add seeds. Use for "fuzz the OneNote parser", "run OneNoteParserFuzzer against these files", "reproduce an OSS-Fuzz…

apache/tika · 90 tokens

amazon-bestseller-listing

Amazon Best Sellers listing scraper: extract product cards from any Amazon Best Sellers (zgbs) or /gp/bestsellers/ category page — returns rank (position on chart), asin, title, url, image, imageAlt, price, stars, reviewCount, ratingRaw per item, plus category metadata (categoryName, categoryFullName, categoryUrl) and…

browser-act/skills · 300 tokens

amazon-reviews-api-skill

This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…

browser-act/skills · 124 tokens

amazon-competitor-analyzer

Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.

browser-act/skills · 48 tokens

file-forensics

Examine what a file claims about itself and what it actually contains — powered by Apache Tika. True content-based type detection (extensions lie), provenance claims (authors, dates, creating application), revision and tamper signals (PDF incremental updates, tracked changes, hidden slides, zip integrity), hidden and…

apache/tika · 142 tokens