claude-worldclaude-world/director-mode-lite/skills/check-environment/SKILL.md

check-environment

Skill80 starsChanged 8 months agoMITView on GitHub

Verify Claude, Codex, and Grok availability plus Director guidance, relay, agents, and skills. Audit optional hooks only when selected. Use after installation or when a native surface misbehaves.

Installs packages

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Verify your development environment is ready for Director Mode.
line 9

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Environment Check

Verify your development environment is ready for Director Mode.

Checks Performed

1. Director Mode Dependencies

Tool	Purpose	Check	Required
git	Version control	`git --version`	Yes
python3	Installer, adapters, and relay	`python3 --version`	Yes
jq	Legacy automation hooks only	`jq --version`	No

2. CLI versions

claude --version
codex --version
grok --version

Minimum: 2.0.0+

3. Project-Specific Tools

Auto-detect project type and check relevant tools:

Project Type	Detected By	Tools to Check
Node.js	`package.json`	`node --version`, `npm --version` or `pnpm --version`
Python	`requirements.txt`, `pyproject.toml`	`python3 --version`, `pip --version`
Rust	`Cargo.toml`	`rustc --version`, `cargo --version`
Go	`go.mod`	`go version`
Java	`pom.xml`, `build.gradle`	`java --version`, `mvn --version` or `gradle --version`

4. Director Mode Installation

.claude/ directory exists
.claude/skills/ populated (35 skills expected)
.agents/skills/ populated when the Codex adapter is selected
.director-mode/bin/director-relay is executable
.director-mode/bin/director-open is executable
.claude/agents/ populated (14 agents expected)
.codex/agents/ and .grok/agents/ populated for selected adapters
no active hooks for the default install
optional hooks match the explicitly selected mode and contain no surprise deny/block response
CLAUDE.md exists

5. Git Status

Inside git repository
Clean working tree (or note uncommitted changes)

Output Format

## Environment Check Results

### Director Mode Dependencies
- [x] git: 2.54.0
- [x] python3: 3.14.8
- [x] jq: 1.8.2

### Claude Code
- [x] Version: 2.1.305

### Project Tools (Node.js detected)
- [x] node: 24.11.0
- [x] pnpm: 11.22.0

### Director Mode Installation
- [x] .claude/ directory exists
- [x] 35 skills installed
- [x] Cross-CLI guidance and relay installed
- [x] 14 agents installed
- [x] default hook mode: none
- [x] native open launcher installed
- [x] CLAUDE.md exists

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

### Summary
**Status**: Ready

Follow-up Actions

Issue	Action
Missing python3	Install Python 3: `brew install python3` (macOS) or `apt install python3` (Linux)
Missing jq	Ignore unless legacy `--hooks automation` was explicitly selected
Missing git	Install git for your OS
Missing node	Install Node.js LTS: https://nodejs.org
Old Claude Code	Run `claude update`
No .claude/	Run install script: `./install.sh .`
Unexpected hooks active	Inspect Claude user settings and `grok inspect --json`; Grok may load Claude-compatible hooks
No CLAUDE.md	Run `/project-init` or `/claude-md-template`

Download now (ZIP)

In this repository36 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- changelog-observerSkill
- agent-checkSkill
- agentsSkill
- agent-templateSkill
- auto-loopSkill
- changelogSkill
- claude-md-checkSkill
- claude-md-templateSkill
- code-reviewerSkill
- debuggerSkill
- director-modeSkill
- doc-writerSkill
- evolving-loopSkill
- evolving-statusSkill
- focus-problemSkill
- getting-startedSkill
- handoff-claudeSkill
- handoff-codexSkill
- handoff-geminiSkill
- handoff-grokSkill
- hooks-checkSkill
- hook-templateSkill
- interop-routerSkill
- mcp-checkSkill
- planSkill
- project-health-checkSkill
- project-initSkill
- session-relaySkill
- skill-checkSkill
- skillsSkill
- skill-templateSkill
- smart-commitSkill
- test-firstSkill
- test-runnerSkill
- workflowSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free