prerequisites
/prerequisites
Raportuje w trybie tylko do odczytu, jakich zewnętrznych narzędzi wymagają włączone wtyczki i których brakuje na maszynie, niczego nie instalując.
- Autor
- melodic-software ↗
- Repozytorium
- claude-code-plugins ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/check-prerequisites.mjs, scripts/check-prerequisites.test.sh
Co robi i kiedy
Raportuje w trybie tylko do odczytu, jakich zewnętrznych narzędzi wymagają włączone wtyczki i których brakuje na maszynie, niczego nie instalując.
Oryginalny opis (EN)
Read-only report of external tools the enabled plugin fleet declares, and which of them are missing. Use when a hook says a formatter or CLI is missing, or when asking whether this machine has what the enabled plugins need. Never installs.
Jak działa
- Purpose
- Run
- Next
- Gotchas
Podgląd SKILL.md
---
description: "Read-only report of external tools the enabled plugin fleet declares, and which of them are missing. Use when a hook says a formatter or CLI is missing, or when asking whether this machine has what the enabled plugins need. Never installs."
user-invocable: true
disable-model-invocation: false
metadata:
workflow-stage: operator
summary: Report external tools the enabled fleet declares missing. Never installs.
cadence: weekly
---
## Purpose
Answer "does this host have what the enabled plugins need?" Read `prerequisites.json` in each enabled plugin, resolve each declared dependency with the shared Node checker, and print one table. Do not install, download, or run `npx`.
**Claim:** the fleet check lives here, not as a `deps` action on `plugins` and not as a machine-health category. `plugins` brings marketplace versions current and is `disable-model-invocation: true`. This question is read-only and model-invocable. Each plugin that needs an external dependency declares it in `prerequisites.json` at the plugin root, in the schema `docs/conventions/prerequisites/` owns, which this skill and the per-plugin check both read.
- **Pointer**: when checking what `disable-model-invocation` governs, fetch [skills: frontmatter reference](https://code.claude.com/docs/en/skills#frontmatter-reference) live. **As of**: 2026-10-11. **Recheck trigger**: a Claude Code release adds a manifest field for external binaries, or `plugins` becomes model-invocable for a read-only action.
## Run
```bash
node "${CLAUDE_SKILL_DIR}/scripts/check-prerequisites.mjs"
```
The table columns are plugin, id, kind, need, status, the check skill, and the install hints. `missing=N present=M` is the last line. The status is `present`, `missing`, `outdated` (below its version floor), `unverified` (the version could not be read) or `agent-check` (an MCP server only the agent can see). Exit 1 means a required entry is missing or below its floor, and a missing optional entry leaves exit 0. Exit 2 means no plugin roots could be read, the listing was not JSON, or a `prerequisites.json` fails the schema.
With no arguments and a `claude` executable on PATH, the script reads the enabled set and each `installPath` from `claude plugin list --json`. That output lists installs across every project, so it keeps user and managed rows, and project or local rows only when their `projectPath` is the current project (`CLAUDE_PROJECT_DIR`, else the git toplevel); an id resolves by its most specific scope, so user-enabled and project-disabled is disabled. When `claude` is absent or prints nothing, it merges `enabledPlugins` from the settings files instead: the user settings in `~/.claude` (`CLAUDE_CONFIG_DIR` overrides that directory) and the project's `.claude/settings.json` and `settings.local.json`. A file holding any non-Boolean `enabledPlugins` value contributes none of its keys, and the managed scope is not read there. Output that is not a JSON list stops the run with exit 2 instead. Only when none of that state exists does it scan `plugins/*/prerequisites.json` in the current repository; a state with nothing enabled prints an empty table.
We read `claude plugin list --json` as one row per install with `id`, `scope`, `enabled`, `installPath` and, for project and local rows, `projectPath`, observed on Claude Code 2.1.284 (user and project rows only; a managed row was not observed), and we let an id's most specific scope decide whether it is enabled.
- **Pointer**: when checking which scope wins for `enabledPlugins`, fetch [settings reference: enabledPlugins](https://code.claude.com/docs/en/settings-reference#enabledplugins) live. **As of**: 2026-10-11. **Recheck trigger**: a release note changes `plugin list --json` fields or its scope values, or that entry changes the precedence.
## Next
- A formatter or linter binary is missing: /actionlint:check, /bash-format:check, /biome-format:check, /go-format:check, /markdown-format:check, /powershell-format:check, /ruff-format:check or /typos-format:check
- Record the whole machine's facts and identity domains, not only binaries: /harness-ops:machine-profile
- The fleet's versions, a different question: /harness-ops:plugins audit
## Gotchas
Node is the only runtime this skill needs; the checker is `lib/prerequisites.mjs`, generated from the repository's canonical copy. A plugin whose `prerequisites.json` is still in the retired `tools` shape fails the schema and exits 2.
A missing row is a report, not an install. Do not run `npx`, `npm install`, or `go install` from this skill.
The table's `check` column names the skill for that row. When that skill is model-invocable, run it. When it is a setup skill (a `:setup check` command), it is human-only, so the model cannot invoke it and can only relay the command: tell the user to type it and show the row's install command. Install nothing unless the user asked.
Pliki w paczce (4)
- SKILL.md 5 KB
- evals/evals.json 3 KB
- scripts/check-prerequisites.mjs 8 KB
- scripts/check-prerequisites.test.sh 12 KB
Wersje
W bazie nie ma innych skilli o nazwie prerequisites.
Migawka bazy z 13.11.2026 · wersja paczki 12f79e337484 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 84check
Sprawdza w trybie tylko do odczytu, czy narzędzia wymagane przez wtyczkę knowledge (node, python, yt-dlp, ffmpeg, ImageMagick) są dostępne, niczego nie instalując. - 84audit-plugin-landscape
Raportuje w trybie tylko do odczytu, które zainstalowane wtyczki i marketplace'y są nieaktualne lub nakładają się, i co warto przyjąć, dostosować albo porzucić. - 100context-hub-setup
Sprawdza, czy zainstalowano wtyczki Serena i Context7, i raportuje braki wraz z poleceniem instalacji każdej z nich. - 100rudder-environment-check
Sprawdza wymagania wstępne narzędzi RudderStack i raportuje, których brakuje, przed pierwszym uruchomieniem przepływów pracy. - 100context-hub-setup
Sprawdza, czy działają wtyczki Serena i Context7, i podaje polecenia instalacji dla brakujących elementów, gdy łączność MCP szwankuje. - 100study-team
Prowadzi interaktywny przegląd gotowego raportu z głębokiej analizy z trzech perspektyw, gdy zespoły agentów Claude Code są włączone w trybie in-process.