Setup Dependencies
npx machina-cli add skill avi1234/claude-team-plugins/setup-dependencies --openclawCheck all required dependencies for this team's development environment:
- Check Node.js: Run
which nodeandnode --version- minimum version: {YOUR_MIN_VERSION} - Check npm: Run
which npm - Check git: Run
which git - Check gh CLI: Run
which gh- if not found, suggestbrew install gh && gh auth login- If found, verify auth:
gh auth status
- If found, verify auth:
- {YOUR_TOOL}: Run
which {tool}- fail if not found - {YOUR_PLUGIN}: Run
grep "{plugin-name}@{marketplace}" ~/.claude/settings.json- warn if not found - {YOUR_MCP}: Use ToolSearch with query "{mcp-name}" - fail if no tools found
Report status for each check. If any required checks fail, provide install commands.
Source
git clone https://github.com/avi1234/claude-team-plugins/blob/main/team1-plugin/skills/setup-dependencies/SKILL.mdView on GitHub Overview
This skill checks required development dependencies for the team's environment, including Node.js, npm, git, gh CLI, and specific tool/plugin/MCP checks. It reports the status of each gate and suggests install commands when a check fails, helping teams start consistently.
How This Skill Works
The skill runs a sequence of environment checks: it uses which to detect executables, node --version for minimum versions, gh auth status for authentication, and reads ~/.claude/settings.json to verify plugin presence. For MCP validation it runs ToolSearch with the MCP name. It then reports the status of each check and provides install commands when failures are found.
When to Use It
- Onboarding a new developer to ensure core tools (Node.js, npm, git, gh) are installed and configured.
- Auditing local or CI environments to catch missing dependencies before work begins.
- Troubleshooting a flaky dev setup by pinpointing missing or misconfigured tools.
- Preparing plugin releases by confirming required tools, plugins, and MCPs exist and are accessible.
- Automatically generating a report of missing dependencies to guide onboarding and remediation.
Quick Start
- Step 1: Review the required minimums in the SKILL.md (e.g., {YOUR_MIN_VERSION}).
- Step 2: Run the dependency checks in a clean terminal or CI environment and collect statuses.
- Step 3: Install any missing tools using the suggested commands and re-run until all checks pass.
Best Practices
- Pin minimum tool versions (e.g., Node.js) and document them in a central policy.
- Document required tool installation steps and commands for quick remediation.
- Ensure PATH and environment variables are correctly configured to avoid conflicts.
- Run the checks in both local and CI environments to catch discrepancies early.
- Keep the min-version placeholders up to date as the tech stack evolves.
Example Use Cases
- A new hire runs the setup checks and quickly resolves missing Node.js and gh CLI before coding.
- CI fails due to missing gh CLI; the checks suggest install and gh auth login to proceed.
- A plugin author verifies required MCPs exist via ToolSearch before release.
- Developers resolve a mismatch in Node.js by following the install commands provided by the checks.
- An automation script runs these checks before every code review to ensure readiness.
