check

i2p — Consolidated dependency check

Six plugins each ship a /check. This runs them all and gives you one readiness picture, so you don't have to remember to probe each plugin separately.

Stance — advisory, never a false PASS. A missing tool narrows a capability, it does not break the marketplace. Report gaps plainly; with --strict, surface a non-OK overall status when a required tool is missing.

---

1. Run each installed plugin's check

For each plugin that is installed and ships a check, run it, passing $ARGUMENTS through (--strict, --tier=recommended, …):

Plugin	Check
market-scanner	/market-scanner:check
ideator	/ideator:check
foundry	/foundry:check
atelier	/atelier:check
sentinel	/sentinel:check
pressroom	/pressroom:check
mission-control	/mission-control:check

Prefer running them in parallel. Do not re-implement any probe here — each plugin's check reads its own canonical skills/check/requirements.tsv.

2. Consolidate

Merge every row into one table grouped by plugin: plugin · tool · tier · ✓/✗ · install hint. Then a one-line summary: <N> present, <M> missing (<K> required) across the suite.

3. Summarise & guide

• Call out the required gaps first (these are the ones that matter), then recommended/optional.
• Point at the marketplace PREREQUISITES/ folder and the per-row install hints.
• Name any plugin that is not installed so the picture is complete (e.g. "sentinel not installed — no security tooling checked").

---

Self-improvement covenant

Inherits the front door covenant (knowledge/covenant.md). If a tool a plugin needs isn't being checked, the fix is upstream in that plugin's requirements.tsv — not a patch here.