/plugin marketplace add https://developers.blu-ce.horizonmedia.com/plugins/claude-code/marketplace.json
/plugin install blu@blu

/blu:check [module folder; default: the current repository]

Run blu check on a Blu module (the folder with blu.module.json and its code) and fix what it reports, until it passes. Use when asked to check, verify or validate a Blu integration, or after changing a module's manifest, build config, SDK usage or API.

This is the skill's own text, which Claude reads when the skill runs. $ARGUMENTS stands for what you type after the command.

Check a Blu module

1. Find the module's folder: $ARGUMENTS, or the folder containing blu.module.json. If there's no manifest yet, the module isn't integrated; offer /blu:integrate instead.

2. Run the check there, using the package manager the repo uses:

   • npx blu check (npm), pnpm exec blu check (pnpm) or yarn blu check (yarn);
   • add --json if you want machine-readable results.

   If blu isn't found, @blu/sdk isn't installed: see the integrate skill's install reference.

3. For each ✘, fix the cause, not the symptom. The message says what to change. The gotchas table explains each one. Never weaken a check: don't remove the @blu/sdk singleton, delete manifest tools to silence a mismatch, or drop manifest from the MCP endpoint.

4. Re-run until it prints All checks passed. Treat ⚠ as advice: fix it if it's cheap, otherwise explain why it stays.

5. Run the project's own build and tests too, since blu check is static and doesn't run the code.

6. Report what was wrong, what you changed, and anything still needing a person (environment URLs, the role mapping, Blu admin steps).