Run and ship this repo: make targets, artifacts, release runbook. Use when testing, linting, or releasing. Do not use for setup; use night-market-build-and-env.
This skill is the runbook for operating the claude-night-market repo:
what each make target actually executes, where artifacts land, and the
exact sequence that ships a release. Every command below was verified
against the Makefile, scripts/, and .github/workflows/ on 2026-07-02
(repo v1.9.15).
Terms used once and reused throughout:
Plugin: a directory under plugins/ with a
.claude-plugin/plugin.json manifest. Most have their own Makefile,
pyproject.toml, and tests/.
skrills: a Rust CLI for skill validation and token analysis,
vendored at plugins/abstract/bin/skrills. Every skrills target has
a Python fallback, so a missing binary never blocks you.
ClawHub export: a cross-framework skill package format written to
clawhub/ by scripts/clawhub_export.py.
All commands run from the repo root unless a cd is shown. uv is
required for everything Python. For environment setup, see
night-market-build-and-env.
Command anatomy
Command
What it actually executes
When to use
Expected output shape
make test
./scripts/run-plugin-tests.sh --all: per plugin, runs make test --quiet if the plugin Makefile has a test: target, else uv run python -m pytest tests/ --tb=short --quiet if pyproject mentions pytest. Skips plugins without tests/.
uv run ruff format plugins/, then uv run ruff check --fix plugins/, then ruff format again, then uv run bandit --quiet -c pyproject.toml -r plugins/. All use root pyproject.toml config.
Before every commit. Mutates files (auto-fix).
Four staged sections ending "Lint Complete".
make typecheck
./scripts/run-plugin-typecheck.sh --all: per-plugin uv run mypy under each plugin's own strict config, plus a separate uv run mypy hooks/ pass when hooks/*.py exists.
After type-touching changes and before release.
Per-plugin pass/fail. Hooks checked as a sub-step.
make validate-all
python3 plugins/abstract/scripts/validate_plugin.py <plugin> for every plugin. Failures print "(validation failed)" but do NOT stop the loop or fail the target.
Structure audit after manifest edits.
One validation block per plugin. Read output, not exit code.
make plugin-check
For each plugin whose Makefile has a plugin-check: target: timeout 180 make -C plugins/<p> plugin-check. Failures and timeouts print a note, exit code stays 0.
Dogfood/demo sweep before release.
Per-plugin sections. Watch for "(plugin-check failed or timed out)".
make docs-sync-check
bash scripts/capabilities-sync-check.sh
PR touches plugin manifests or skills (mirrors capabilities-sync.yml CI).
Drift list or clean pass. Fix drift with /sanctum:sync-capabilities --fix.
make supply-chain-scan
python3 scripts/supply_chain_scan.py
After dependency or lockfile changes.
Scan report between banner lines.
make validate-skills
skrills validate --skill-dir plugins --target claude (plugin bin, then PATH). Falls back to uv run python scripts/check_plugin_hooks.py.
Skill frontmatter/structure check.
skrills report, or the Python fallback notice plus its output.
make analyze-skills
skrills analyze --skill-dir plugins. Falls back to uv run python scripts/generate_dependency_map.py.
Skill token-budget and dependency analysis.
Token/dependency stats.
make status
make -C <plugin> status for every plugin.
Quick overview.
Per-plugin status or "(status unavailable)".
make clean
make -C <plugin> clean for every plugin, errors ignored.
Reset build artifacts.
"Done."
Two targets have soft failure modes worth repeating: make validate-all
and make plugin-check keep going past failures and can exit 0 while a
plugin is broken. Read their output. Do not treat a green exit as proof.
Scoping runs: one plugin, one file
The root Makefile auto-generates delegation targets for every plugin
that has a Makefile. make <plugin>-<target> is identical to
make -C plugins/<plugin> <target>:
make sanctum-test # run sanctum's test suite
make imbue-lint # run imbue's lint target
make abstract-help # list a plugin's own targets
Run a single test file from inside the plugin directory:
cd plugins/imbue && uv run pytest tests/unit/test_deferred_capture.py -x -q
Rules that save you an hour:
Never run root pytest expecting plugin tests to run. Root
pyproject.toml sets norecursedirs = ["plugins/*", ...] because
plugin conftest.py files collide on import paths. Plugin tests run
per-plugin, always.
Some plugins force coverage on every run. imbue's pytest addopts
include --cov=scripts, --cov-report=html:htmlcov, and
--cov-report=xml, so even a single-file run writes htmlcov/ and
coverage.xml into plugins/imbue/. This is normal, not a mess you
made.
Coverage thresholds: root coverage fail_under = 85. Per-plugin
overrides live in each plugin's [tool.nightmarket]coverage_threshold (per-plugin values: see
night-market-validation-and-qa, the designated home for the
threshold inventory). run-plugin-tests.sh reads that value and
passes --cov-fail-under=<n> when the plugin runs via the pytest
path.
Artifact conventions
Artifact
Producer
Location
Committed?
htmlcov/, coverage.xml
pytest coverage addopts
Repo root and per-plugin dirs
Present in tree but regenerated. Never hand-edit
reports/skill-graph.json
skill-graph tooling
reports/
No, generated locally (reports/ is gitignored). Rebuild with the skill-graph tooling
clawhub/
make clawhub-export
clawhub/manifest.json plus one nm-<plugin>-<skill>/ dir per exported skill
No, generated locally. make clawhub-export rebuilds it, and the release workflow regenerates it in CI
bridge/openclaw/, bridge/a2a/
make bridge-build, make a2a-cards
bridge/
Build outputs. make bridge-clean removes skills and a2a
The ecosystem ships as one version. .claude-plugin/marketplace.json
is the version source of truth, fanned out to every plugin manifest.
Gates and review policy are night-market-change-control territory.
This is the mechanical sequence.
Preflight. Run Skill(sanctum:git-workspace-review) (read-only
workspace check). Confirm you are on a <topic>-<version> branch,
not master.
Bump the version everywhere. Dry-run first:
uv run python plugins/sanctum/scripts/update_versions.py 1.9.16 --dry-run
uv run python plugins/sanctum/scripts/update_versions.py 1.9.16
git diff --stat
The script rejects anything not matching ^\d+\.\d+\.\d+$, then
rewrites the version field in every match of these globs (cache and
venv dirs excluded): **/pyproject.toml, **/Cargo.toml,
**/package.json, **/.claude-plugin/plugin.json,
**/.claude-plugin/metadata.json,
**/.claude-plugin/marketplace.json, **/openpackage.yml, and any
**/__init__.py containing __version__. Expect a large diff
of roughly 100 files. That is the design.
CHANGELOG entry. CHANGELOG.md follows Keep a Changelog 1.1.0
with SemVer. Keep ## [Unreleased] at the top and insert
## [X.Y.Z] - YYYY-MM-DD directly below it. Never rewrite or
de-slop historical entries.
Docs sync. Update the per-plugin version column in
docs/api-overview.md. Then:
make docs-sync-check
If it reports drift between plugin.json registrations and the
capabilities reference (book/src/reference/, generated content),
run /sanctum:sync-capabilities --fix.
PR and gates. Open the PR and clear the gates per
night-market-change-control (pre-commit hooks, slop-check on docs,
capabilities-sync, typecheck, security workflows).
Merge to master. trust-attestation.yml fires on the push: it
runs make test, writes trust-report.json, and attaches a SLSA
provenance attestation via actions/attest-build-provenance@v4.
Tag. Run /sanctum:create-tag v1.9.16. It pushes a v-prefixed
annotated tag and confirms the release pipeline started.
Release pipeline. cross-framework-publish.yml fires on v*
tags: it strips the v, validates the version against
^[0-9]+\.[0-9]+\.[0-9]+, runs the cross-framework unit tests
(clawhub_export, build_bridge, a2a_cards, framework_detect), runs
make cross-framework, packages four tarballs
(night-market-clawhub, night-market-openclaw-bridge,
night-market-a2a-cards, night-market-cross-framework), and
creates the GitHub release. Precondition: the publish job fails if
clawhub/manifest.json is missing or its total_exported is 0
(currently 188). Post-release ClawHub submission is manual:
./scripts/clawhub-submit.sh v<version>.
Release checklist:
make test, make lint, make typecheck all pass locally
update_versions.py diff reviewed and marketplace.json shows the
new version
CHANGELOG has the new section, [Unreleased] still on top
make docs-sync-check clean
Tag pushed, both workflows green, release has 4 tarball assets
Book publishing
The mdBook under book/ deploys via deploy-book.yml:
Triggers: push to master or main touching book/** or the workflow
file itself, plus PRs on the same paths (build-only) and manual
dispatch.
Build: peaceiris/actions-mdbook@v2 with mdbook-version: 'latest',
then mdbook build with working-directory book. Output
book/build uploads via actions/upload-pages-artifact@v5 and
deploys with actions/deploy-pages@v5, with one retry step if the
first deploy fails.
Known fragility: mdbook is unpinned ("latest"), so a new upstream
mdbook release can break the build with no change in this repo. If
the book job fails right after an mdbook release, suspect that first.
Local preview, if mdbook is installed:
cd book && mdbook build # output in book/build/
Cross-framework export surface
make clawhub-export # export all skills to clawhub/, then validate
make clawhub-export-top # top 20 most marketable skills only
make clawhub-validate # re-validate an existing export
make clawhub-stats # export statistics, no writes
make bridge-build # (depends on clawhub-export) build bridge/openclaw/
make a2a-cards # generate A2A agent cards into bridge/a2a/
make a2a-list # list agents eligible for card generation
make detect-framework # detect the active agentic framework
make cross-framework # all of the above: export + bridge + cards
make cross-framework is exactly what the release pipeline runs, so
running it locally before tagging catches export failures early. It
prints skill and agent counts and ends with framework detection.
When NOT to use
You want
Use instead
Set up uv, Python, tools from scratch
night-market-build-and-env
Classify a change, know which gates apply
night-market-change-control
Diagnose a failing test or broken hook
night-market-debugging-playbook
Configuration axes, env vars, defaults
night-market-config-catalog
Coverage discipline and evidence bar
night-market-validation-and-qa
Plugin/skill/hook mechanics
claude-code-plugin-reference
Measurement tooling interpretation
night-market-diagnostics-toolkit
Stop an egregore loop or its watchdog relaunch machinery
night-market-completion-integrity-campaign (P1b, "Stopping and relaunch machinery")
Exit Criteria
The chosen make target ran and its per-plugin summary was read,
beyond the exit code alone. For make validate-all and
make plugin-check, output was scanned for embedded failure
notes.
Single-plugin or single-file test runs were executed from inside
the plugin directory, never via root pytest.
For a release: update_versions.py diff verified, CHANGELOG
section added, make docs-sync-check clean, tag pushed, and the
GitHub release shows all four tarball assets.
Any generated artifact (htmlcov, coverage.xml, clawhub/,
book/build) was identified as generated and not hand-edited.
Provenance and maintenance
Compiled 2026-07-02 against repo v1.9.15, branch discussions-fix-1.9.14.
Coverage-threshold inventory delegated to night-market-validation-and-qa
and the egregore stop cross-reference added on 2026-07-03.
Volatile facts and how to re-verify them:
# Make target wiring
sed -n '60,150p' Makefile && sed -n '150,300p' Makefile
# Test runner behavior (delegation, coverage threshold, skip logic)
sed -n '1,110p' scripts/run-plugin-tests.sh
# Version bump globs and semver regex
rg -n "patterns|re.match" plugins/sanctum/scripts/update_versions.py
# Release pipeline gates
rg -n "tags|total_exported|tar -czf" \
.github/workflows/cross-framework-publish.yml
# Attestation flow
rg -n "make test|attest|trust-report" \
.github/workflows/trust-attestation.yml
# Book deploy and mdbook pin
rg -n "mdbook-version|deploy-pages|working-directory" \
.github/workflows/deploy-book.yml
# Current export count (was 188 on 2026-07-02)
python3 -c "import json; \
print(json.load(open('clawhub/manifest.json'))['total_exported'])"
# Coverage thresholds
rg -n "coverage_threshold" plugins/*/pyproject.toml
rg -n "fail_under" pyproject.toml
1---2name: night-market-operations3description: Run and ship this repo: make targets, artifacts, release runbook. Use when testing, linting, or releasing. Do not use for setup; use night-market-build-and-env.4---567# Night Market Operations89This skill is the runbook for operating the claude-night-market repo:10what each make target actually executes, where artifacts land, and the11exact sequence that ships a release. Every command below was verified12against the Makefile, scripts/, and .github/workflows/ on 2026-07-0213(repo v1.9.15).1415Terms used once and reused throughout:1617- **Plugin**: a directory under `plugins/` with a18 `.claude-plugin/plugin.json` manifest. Most have their own Makefile,19 pyproject.toml, and tests/.20- **skrills**: a Rust CLI for skill validation and token analysis,21 vendored at `plugins/abstract/bin/skrills`. Every skrills target has22 a Python fallback, so a missing binary never blocks you.23- **ClawHub export**: a cross-framework skill package format written to24 `clawhub/` by `scripts/clawhub_export.py`.2526All commands run from the repo root unless a `cd` is shown. `uv` is27required for everything Python. For environment setup, see28night-market-build-and-env.2930## Command anatomy3132| Command | What it actually executes | When to use | Expected output shape |33|---------|---------------------------|-------------|-----------------------|34| `make test` | `./scripts/run-plugin-tests.sh --all`: per plugin, runs `make test --quiet` if the plugin Makefile has a `test:` target, else `uv run python -m pytest tests/ --tb=short --quiet` if pyproject mentions pytest. Skips plugins without `tests/`. | Full sweep before a PR or release. | Per-plugin pass/fail/skip lines. Failures re-run verbose. |35| `make lint` | `uv run ruff format plugins/`, then `uv run ruff check --fix plugins/`, then ruff format again, then `uv run bandit --quiet -c pyproject.toml -r plugins/`. All use root pyproject.toml config. | Before every commit. Mutates files (auto-fix). | Four staged sections ending "Lint Complete". |36| `make typecheck` | `./scripts/run-plugin-typecheck.sh --all`: per-plugin `uv run mypy` under each plugin's own strict config, plus a separate `uv run mypy hooks/` pass when `hooks/*.py` exists. | After type-touching changes and before release. | Per-plugin pass/fail. Hooks checked as a sub-step. |37| `make validate-all` | `python3 plugins/abstract/scripts/validate_plugin.py <plugin>` for every plugin. Failures print "(validation failed)" but do NOT stop the loop or fail the target. | Structure audit after manifest edits. | One validation block per plugin. Read output, not exit code. |38| `make plugin-check` | For each plugin whose Makefile has a `plugin-check:` target: `timeout 180 make -C plugins/<p> plugin-check`. Failures and timeouts print a note, exit code stays 0. | Dogfood/demo sweep before release. | Per-plugin sections. Watch for "(plugin-check failed or timed out)". |39| `make docs-sync-check` | `bash scripts/capabilities-sync-check.sh` | PR touches plugin manifests or skills (mirrors capabilities-sync.yml CI). | Drift list or clean pass. Fix drift with `/sanctum:sync-capabilities --fix`. |40| `make supply-chain-scan` | `python3 scripts/supply_chain_scan.py` | After dependency or lockfile changes. | Scan report between banner lines. |41| `make validate-skills` | `skrills validate --skill-dir plugins --target claude` (plugin bin, then PATH). Falls back to `uv run python scripts/check_plugin_hooks.py`. | Skill frontmatter/structure check. | skrills report, or the Python fallback notice plus its output. |42| `make analyze-skills` | `skrills analyze --skill-dir plugins`. Falls back to `uv run python scripts/generate_dependency_map.py`. | Skill token-budget and dependency analysis. | Token/dependency stats. |43| `make status` | `make -C <plugin> status` for every plugin. | Quick overview. | Per-plugin status or "(status unavailable)". |44| `make clean` | `make -C <plugin> clean` for every plugin, errors ignored. | Reset build artifacts. | "Done." |4546Two targets have soft failure modes worth repeating: `make validate-all`47and `make plugin-check` keep going past failures and can exit 0 while a48plugin is broken. Read their output. Do not treat a green exit as proof.4950## Scoping runs: one plugin, one file5152The root Makefile auto-generates delegation targets for every plugin53that has a Makefile. `make <plugin>-<target>` is identical to54`make -C plugins/<plugin> <target>`:5556```bash57make sanctum-test # run sanctum's test suite58make imbue-lint # run imbue's lint target59make abstract-help # list a plugin's own targets60```6162Run a single test file from inside the plugin directory:6364```bash65cd plugins/imbue && uv run pytest tests/unit/test_deferred_capture.py -x -q66```6768Rules that save you an hour:6970- Never run root `pytest` expecting plugin tests to run. Root71 pyproject.toml sets `norecursedirs = ["plugins/*", ...]` because72 plugin conftest.py files collide on import paths. Plugin tests run73 per-plugin, always.74- Some plugins force coverage on every run. imbue's pytest `addopts`75 include `--cov=scripts`, `--cov-report=html:htmlcov`, and76 `--cov-report=xml`, so even a single-file run writes `htmlcov/` and77 `coverage.xml` into `plugins/imbue/`. This is normal, not a mess you78 made.79- Coverage thresholds: root coverage `fail_under = 85`. Per-plugin80 overrides live in each plugin's `[tool.nightmarket]`81 `coverage_threshold` (per-plugin values: see82 night-market-validation-and-qa, the designated home for the83 threshold inventory). `run-plugin-tests.sh` reads that value and84 passes `--cov-fail-under=<n>` when the plugin runs via the pytest85 path.8687## Artifact conventions8889| Artifact | Producer | Location | Committed? |90|----------|----------|----------|------------|91| `htmlcov/`, `coverage.xml` | pytest coverage addopts | Repo root and per-plugin dirs | Present in tree but regenerated. Never hand-edit |92| `reports/skill-graph.json` | skill-graph tooling | `reports/` | No, generated locally (`reports/` is gitignored). Rebuild with the skill-graph tooling |93| `clawhub/` | `make clawhub-export` | `clawhub/manifest.json` plus one `nm-<plugin>-<skill>/` dir per exported skill | No, generated locally. `make clawhub-export` rebuilds it, and the release workflow regenerates it in CI |94| `bridge/openclaw/`, `bridge/a2a/` | `make bridge-build`, `make a2a-cards` | `bridge/` | Build outputs. `make bridge-clean` removes skills and a2a |95| `book/build/` | `mdbook build` (book/book.toml sets `build-dir = "build"`) | `book/build/` | No, CI-built |96| `trust-report.json` | CI only: trust-attestation.yml on push to master | Workflow workspace, SLSA-attested | No, never in tree |9798## Release runbook99100The ecosystem ships as one version. `.claude-plugin/marketplace.json`101is the version source of truth, fanned out to every plugin manifest.102Gates and review policy are night-market-change-control territory.103This is the mechanical sequence.1041051. **Preflight.** Run `Skill(sanctum:git-workspace-review)` (read-only106 workspace check). Confirm you are on a `<topic>-<version>` branch,107 not master.1081092. **Bump the version everywhere.** Dry-run first:110111 ```bash112 uv run python plugins/sanctum/scripts/update_versions.py 1.9.16 --dry-run113 uv run python plugins/sanctum/scripts/update_versions.py 1.9.16114 git diff --stat115 ```116117 The script rejects anything not matching `^\d+\.\d+\.\d+$`, then118 rewrites the version field in every match of these globs (cache and119 venv dirs excluded): `**/pyproject.toml`, `**/Cargo.toml`,120 `**/package.json`, `**/.claude-plugin/plugin.json`,121 `**/.claude-plugin/metadata.json`,122 `**/.claude-plugin/marketplace.json`, `**/openpackage.yml`, and any123 `**/__init__.py` containing `__version__`. Expect a large diff124 of roughly 100 files. That is the design.1251263. **CHANGELOG entry.** CHANGELOG.md follows Keep a Changelog 1.1.0127 with SemVer. Keep `## [Unreleased]` at the top and insert128 `## [X.Y.Z] - YYYY-MM-DD` directly below it. Never rewrite or129 de-slop historical entries.1301314. **Docs sync.** Update the per-plugin version column in132 `docs/api-overview.md`. Then:133134 ```bash135 make docs-sync-check136 ```137138 If it reports drift between plugin.json registrations and the139 capabilities reference (`book/src/reference/`, generated content),140 run `/sanctum:sync-capabilities --fix`.1411425. **PR and gates.** Open the PR and clear the gates per143 night-market-change-control (pre-commit hooks, slop-check on docs,144 capabilities-sync, typecheck, security workflows).1451466. **Merge to master.** trust-attestation.yml fires on the push: it147 runs `make test`, writes `trust-report.json`, and attaches a SLSA148 provenance attestation via `actions/attest-build-provenance@v4`.1491507. **Tag.** Run `/sanctum:create-tag v1.9.16`. It pushes a v-prefixed151 annotated tag and confirms the release pipeline started.1521538. **Release pipeline.** cross-framework-publish.yml fires on `v*`154 tags: it strips the `v`, validates the version against155 `^[0-9]+\.[0-9]+\.[0-9]+`, runs the cross-framework unit tests156 (clawhub_export, build_bridge, a2a_cards, framework_detect), runs157 `make cross-framework`, packages four tarballs158 (`night-market-clawhub`, `night-market-openclaw-bridge`,159 `night-market-a2a-cards`, `night-market-cross-framework`), and160 creates the GitHub release. Precondition: the publish job fails if161 `clawhub/manifest.json` is missing or its `total_exported` is 0162 (currently 188). Post-release ClawHub submission is manual:163 `./scripts/clawhub-submit.sh v<version>`.164165Release checklist:166167- [ ] `make test`, `make lint`, `make typecheck` all pass locally168- [ ] `update_versions.py` diff reviewed and marketplace.json shows the169 new version170- [ ] CHANGELOG has the new section, `[Unreleased]` still on top171- [ ] `make docs-sync-check` clean172- [ ] Tag pushed, both workflows green, release has 4 tarball assets173174## Book publishing175176The mdBook under `book/` deploys via deploy-book.yml:177178- Triggers: push to master or main touching `book/**` or the workflow179 file itself, plus PRs on the same paths (build-only) and manual180 dispatch.181- Build: `peaceiris/actions-mdbook@v2` with `mdbook-version: 'latest'`,182 then `mdbook build` with working-directory `book`. Output183 `book/build` uploads via `actions/upload-pages-artifact@v5` and184 deploys with `actions/deploy-pages@v5`, with one retry step if the185 first deploy fails.186- Known fragility: mdbook is unpinned ("latest"), so a new upstream187 mdbook release can break the build with no change in this repo. If188 the book job fails right after an mdbook release, suspect that first.189190Local preview, if mdbook is installed:191192```bash193cd book && mdbook build # output in book/build/194```195196## Cross-framework export surface197198```bash199make clawhub-export # export all skills to clawhub/, then validate200make clawhub-export-top # top 20 most marketable skills only201make clawhub-validate # re-validate an existing export202make clawhub-stats # export statistics, no writes203make bridge-build # (depends on clawhub-export) build bridge/openclaw/204make a2a-cards # generate A2A agent cards into bridge/a2a/205make a2a-list # list agents eligible for card generation206make detect-framework # detect the active agentic framework207make cross-framework # all of the above: export + bridge + cards208```209210`make cross-framework` is exactly what the release pipeline runs, so211running it locally before tagging catches export failures early. It212prints skill and agent counts and ends with framework detection.213214## When NOT to use215216| You want | Use instead |217|----------|-------------|218| Set up uv, Python, tools from scratch | night-market-build-and-env |219| Classify a change, know which gates apply | night-market-change-control |220| Diagnose a failing test or broken hook | night-market-debugging-playbook |221| Configuration axes, env vars, defaults | night-market-config-catalog |222| Coverage discipline and evidence bar | night-market-validation-and-qa |223| Plugin/skill/hook mechanics | claude-code-plugin-reference |224| Measurement tooling interpretation | night-market-diagnostics-toolkit |225| Stop an egregore loop or its watchdog relaunch machinery | night-market-completion-integrity-campaign (P1b, "Stopping and relaunch machinery") |226227## Exit Criteria228229- [ ] The chosen make target ran and its per-plugin summary was read,230 beyond the exit code alone. For `make validate-all` and231 `make plugin-check`, output was scanned for embedded failure232 notes.233- [ ] Single-plugin or single-file test runs were executed from inside234 the plugin directory, never via root pytest.235- [ ] For a release: `update_versions.py` diff verified, CHANGELOG236 section added, `make docs-sync-check` clean, tag pushed, and the237 GitHub release shows all four tarball assets.238- [ ] Any generated artifact (htmlcov, coverage.xml, clawhub/,239 book/build) was identified as generated and not hand-edited.240241## Provenance and maintenance242243Compiled 2026-07-02 against repo v1.9.15, branch discussions-fix-1.9.14.244Coverage-threshold inventory delegated to night-market-validation-and-qa245and the egregore stop cross-reference added on 2026-07-03.246Volatile facts and how to re-verify them:247248```bash249# Make target wiring250sed -n '60,150p' Makefile && sed -n '150,300p' Makefile251252# Test runner behavior (delegation, coverage threshold, skip logic)253sed -n '1,110p' scripts/run-plugin-tests.sh254255# Version bump globs and semver regex256rg -n "patterns|re.match" plugins/sanctum/scripts/update_versions.py257258# Release pipeline gates259rg -n "tags|total_exported|tar -czf" \260 .github/workflows/cross-framework-publish.yml261262# Attestation flow263rg -n "make test|attest|trust-report" \264 .github/workflows/trust-attestation.yml265266# Book deploy and mdbook pin267rg -n "mdbook-version|deploy-pages|working-directory" \268 .github/workflows/deploy-book.yml269270# Current export count (was 188 on 2026-07-02)271python3 -c "import json; \272 print(json.load(open('clawhub/manifest.json'))['total_exported'])"273274# Coverage thresholds275rg -n "coverage_threshold" plugins/*/pyproject.toml276rg -n "fail_under" pyproject.toml277```278279---280281**Source:** [`athola/claude-night-market`](https://github.com/athola/claude-night-market) → `.claude/skills/night-market-operations/SKILL.md`
Run npx skillmds add thedixitjain/night-market-operations in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Run and ship this repo: make targets, artifacts, release runbook. Use when testing, linting, or releasing. Do not use for setup; use night-market-build-and-env. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.
thedixitjain