Confirm your working environment is properly set up before starting substantive work.
Overview
Before diving into complex tasks, take a moment to verify that your development environment is ready. This prevents wasted effort troubleshooting missing files, incorrect paths, or incomplete setup later.
Steps
Initialize your working directory - Set up or navigate to your project root
List directory contents - Run ls -la or equivalent to see what's present
Verify key files exist - Confirm essential files (package.json, requirements.txt, Dockerfile, etc.) are in place
Check configuration - Review README, config files, or setup docs to understand the project structure
Test basic commands - Run a simple command (like --version checks or echo tests) to ensure tools are accessible
Document findings - Note any missing dependencies or configuration needed
Tips
Don't skip this step even if you think everything is ready—environment issues compound quickly
If something is missing, fix it now rather than discovering it mid-task
Take 2-3 minutes here to save 20+ minutes debugging later
Use the verification as your mental checkpoint before declaring "ready to code"
1---2name: verify-environment-ready3description: verify-environment-ready4---5# verify-environment-ready67Confirm your working environment is properly set up before starting substantive work.89## Overview10Before diving into complex tasks, take a moment to verify that your development environment is ready. This prevents wasted effort troubleshooting missing files, incorrect paths, or incomplete setup later.1112## Steps13141. **Initialize your working directory** - Set up or navigate to your project root152. **List directory contents** - Run `ls -la` or equivalent to see what's present163. **Verify key files exist** - Confirm essential files (package.json, requirements.txt, Dockerfile, etc.) are in place174. **Check configuration** - Review README, config files, or setup docs to understand the project structure185. **Test basic commands** - Run a simple command (like `--version` checks or `echo` tests) to ensure tools are accessible196. **Document findings** - Note any missing dependencies or configuration needed2021## Tips2223- Don't skip this step even if you think everything is ready—environment issues compound quickly24- If something is missing, fix it now rather than discovering it mid-task25- Take 2-3 minutes here to save 20+ minutes debugging later26- Use the verification as your mental checkpoint before declaring "ready to code"
Run npx skillmds@latest add claudiawong522/verify-environment-ready in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
verify-environment-ready It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
claudiawong522 (@claudiawong522) published this skill. Their other Agent Skills are listed on their SkillMD profile.
claudiawong522