What does a 'Ready' status indicate?

It indicates all core checks passed (tools, Claude Code version, project structure, and Git state); warnings may still appear for non-critical items.

What should I do if a required file is missing?

Follow the follow-up actions suggested in the report, such as creating package.json, .gitignore, or the src directory, and re-run the check.

Can I customize or extend the checks?

Yes. While this skill defines a core set of checks, you can extend it by adding new validations or integrating additional tooling in your workflow or by modifying the underlying skill configuration.

check-environment

npx machina-cli add skill claude-world/director-mode-lite/check-environment --openclaw

Files (1)

SKILL.md

1.3 KB

Environment Check

Verify your development environment is ready for Director Mode.

Checks Performed

1. Essential Tools

Tool	Purpose	Check
git	Version control	`git --version`
node	JavaScript runtime	`node --version`
npm/pnpm	Package manager	`npm --version`

2. Claude Code Version

claude --version

Minimum: 2.0.0+

3. Project Structure

package.json exists
.gitignore exists
Source directory exists

4. Git Status

Inside git repository
Clean working tree
On feature branch

Output Format

## Environment Check Results

### Essential Tools
- [x] git: 2.39.0
- [x] node: 20.10.0
- [x] pnpm: 8.12.0

### Claude Code
- [x] Version: 2.1.3 (up to date)

### Project Structure
- [x] package.json found
- [x] .gitignore found
- [x] src/ directory found

### Git Status
- [x] Git repository initialized
- [ ] Warning: 3 uncommitted changes

### Summary
**Status**: Ready (with warnings)

Follow-up Actions

Issue	Action
Missing git	Install git
Missing node	Install Node.js LTS
No package.json	Run `npm init`
Old Claude Code	Update Claude Code

Source

git clone https://github.com/claude-world/director-mode-lite/blob/main/skills/check-environment/SKILL.mdView on GitHub

Overview

This skill verifies your development setup for Director Mode by running a structured suite of checks. It validates essential tools, Claude Code version, project structure, and Git status to prevent setup issues from slowing you down.

How This Skill Works

It performs a series of validations by executing commands such as git --version, node --version, and claude --version (minimum 2.0.0+), and by verifying the presence of package.json, .gitignore, and a src directory. It then assesses Git status (repository presence, clean working tree, and current feature branch) and reports a clear readiness status with any warnings.

When to Use It

Before starting work on a new Director Mode project
When onboarding to a new developer workstation
Before running critical Director Mode tasks or deployments
As part of a CI pipeline to gate environment readiness
After updating dependencies or tool versions to confirm continued compatibility

Quick Start

Step 1: Ensure essential tools are installed (git, node, npm/pnpm) and Claude Code is reachable
Step 2: Run the environment check for check-environment
Step 3: Review the Environment Check Results and apply any follow-up actions

Best Practices

Run the environment check before primary development tasks to catch setup gaps early
Pin and track versions for git, Node, and package managers (npm/pnpm) to ensure consistency
Verify core files exist: package.json, .gitignore, and a src directory
Ensure Claude Code version is at least 2.0.0+ and up to date with the project
Review the Environment Check Results and follow up on warnings or missing items

Example Use Cases

A developer on a fresh workstation runs check-environment to confirm tooling is ready before coding
A feature branch workflow includes a pre-commit check that runs the environment validator
CI gates fail if essential tools or project structure are missing, preventing risky merges
New joiner validates their setup during onboarding to avoid early project delays
After a dependency upgrade, the team re-runs the check to ensure Claude Code and tools are compatible

Frequently Asked Questions

Add this skill to your agents