- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add athola/claude-night-market --skill night-market-build-and-env -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add athola/claude-night-market --skill night-market-build-and-env -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add athola/claude-night-market --skill night-market-build-and-env -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add athola/claude-night-market --skill night-market-build-and-env -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/athola/claude-night-market/tree/HEAD/.claude/skills/night-market-build-and-envFrom the publisher
Recreate a working claude-night-market development environment from a bare machine, verify it in under an hour, and avoid the traps that have broken it before. Everything below was verified against the repo on 2026-07-02 (v1.9.15).
One rule dominates: every Python tool runs through uv run. uv is
Astral's Python package and environment manager. On first uv run it
creates .venv/ and syncs it from uv.lock. Never install repo
dependencies with bare pip.
Install in this order. "via uv" means the tool resolves from uv.lock
automatically. There is no manual install step for those rows.
Notes on the optional rows:
.github/workflows/python39-compat.yml.package.json pins
@google/gemini-cli at ^0.25.1. Run npm install at the repo root
only if you use conjure delegation.make validate-skills,
make analyze-skills) has a Python fallback, so you can skip Rust
entirely.gh discussion subcommand. They are reachable only through
gh api graphql.Version numbers observed on the reference machine (2026-07-02):
uv 0.8.22, Python 3.12.3, ruff 0.14.13, mypy 1.19.1, bandit 1.9.2,
pre-commit 4.5.1. Newer versions of uv are fine. The ruff version must
match uv.lock (see traps).
Run these in order after installing rows 1-3 above. Each step lists the output shape that means success.
Step 1: clone and check uv.
git clone [email protected]:athola/claude-night-market.git
cd claude-night-market
uv --version
Expected: a single line like uv 0.8.22. Any 0.8+ version works. CI
pins astral-sh/[email protected].
Step 2: validate all plugin structures (also proves the venv syncs).
make validate-all
Expected: one block per plugin (26 directories) shaped like:
>>> Validating plugins/abstract:
Plugin Validation Report: abstract
...
OK Plugin validation passed
Blue "Recommendations" lines are advisory and fine. A red failure line
or (validation failed) is not.
Step 3: run one fast plugin test suite.
make -C plugins/leyline test
Expected: verbose pytest output ending with a coverage table and a
summary like 710 passed, 6 warnings in 9.96s (counts and timing
drift, but zero failures is the invariant). This proves uv run, pytest,
and per-plugin coverage thresholds all work.
Step 4: install the git hooks.
uv run pre-commit install
Expected: pre-commit installed at .git/hooks/pre-commit. From now on
commits run the full hook chain (file validation, bandit, ruff, mypy,
changed-plugin tests, structure validation). Never bypass it with
--no-verify; CONSTITUTION.md forbids that.
If any step fails, load night-market-debugging-playbook.
This is the number-one onboarding misconception. The README says "Python 3.9+ for hooks", and newcomers read that as "the repo runs on 3.9". It does not. There are three tiers:
Per-plugin requires-python as of 2026-07-02 (22 of 26 plugin dirs
have a pyproject.toml):
<3.14), imbue, leyline, minister,
sanctum, scryWhy the hook tier exists: Claude Code executes hook scripts with
whatever interpreter the host provides, not the repo venv. A hook file
AND everything it transitively imports must therefore stay
3.9-compatible, even inside a plugin whose package requires 3.12. CI
enforces this with two gates in python39-compat.yml: gate 1 runs
ruff check --select UP007 --target-version py39 on hook files (bare
X | Y union annotations), gate 2 builds a real 3.9 venv with
uv venv --python 3.9 and runs hook tests with
--override-ini="addopts=".
Consequences you must respect in hook-reachable code:
timezone.utc, never datetime.UTC (a 3.11+ alias). The root
ruff config extend-ignores UP017 specifically so autofix does not
reintroduce the alias. This break recurred three times before the
ignore plus an AST guard test held the line.yaml, anthropic) in hook entrypoints.
The system interpreter has none of the repo's dependencies, and an
unguarded import makes every git commit emit ModuleNotFoundError.VOW_SHADOW_MODE, quality gates): use night-market-config-catalog.uv --version prints a version at the repo root.uv run ruff --version prints the uv.lock version (0.14.13 as
of 2026-07-02), not the .uv-tools version.make validate-all prints Plugin validation passed for every
plugin and no (validation failed) lines.make -C plugins/leyline test ends with N passed and zero
failures, plus a coverage table.uv run pre-commit install created .git/hooks/pre-commit.Compiled 2026-07-02 against repo v1.9.15 (branch discussions-fix-1.9.14). Observed tool versions and test counts in this file are snapshots and will drift. Re-verify with:
rg -n "requires-python" pyproject.tomlrg -n "requires-python" plugins/*/pyproject.tomlrg -n -A1 'name = "ruff"$' uv.lockrg -n "setup-uv" .github/workflows/*.ymlrg -n -B2 "id: bandit" .pre-commit-config.yamlrg -n "UV_TOOL_DIR|SKRILLS_REPO \?=" Makefilerg -n "norecursedirs" pyproject.tomlrg -n -A8 "addopts" plugins/imbue/pyproject.tomlrg -n "gemini-cli" package.jsonmake -C plugins/leyline testRebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for daily commands; use night-market-operations.
---name: night-market-build-and-envdescription: Rebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not…---# .claude/skills/night-market-build-and-env/SKILL.mdFAQ
Download .claude/skills/night-market-build-and-env/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/athola/claude-night-market.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.