Skip to content
Back to skills

Justhandledlabs Env Doctor

ASecurity

Diagnose why a local Node, Python, Go, or Docker project will not start by checking runtimes, dependencies, ports, environment-key presence, permissions, and required services before changing application code.

  • 36 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 2, 2026
ai-agentspythongosqlnodedockergitdocumentation

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add agentskillexchange/skills --skill justhandledlabs-env-doctor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Justhandledlabs Env Doctor?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Justhandledlabs Env Doctor
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agentskillexchange-justhandledlabs-env-doctor/badge)](https://www.skillsdirectory.com/skills/agentskillexchange-justhandledlabs-env-doctor)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "Diagnose local setup failures with Env Doctor"
slug: "justhandledlabs-env-doctor"
description: "Diagnose why a local Node, Python, Go, or Docker project will not start by checking runtimes, dependencies, ports, environment-key presence, permissions, and required services before changing application code."
verification: "listed"
source: "https://github.com/justhandledlabs/skills/tree/main/skills/env-doctor-free"
author: "JustHandled Labs"
category: "Runbooks & Diagnostics"
framework: "Codex"
---

# Diagnose local setup failures with Env Doctor

Use Env Doctor when an application fails to start, works on one machine but not another, or appears broken before the application code has been proven responsible. The skill detects project type from files such as `package.json`, `pyproject.toml`, `go.mod`, and `Dockerfile`; checks installed runtime versions and missing dependencies; inspects common development ports with operating-system-appropriate commands; compares `.env.example` keys with `.env` without exposing values; and checks likely Postgres, Redis, MySQL, or Docker service state.

The workflow is evidence-first and deliberately cautious. It reports the process that owns a port before suggesting a stop action, never terminates a process without explicit approval, never displays environment-variable values, and explains mutating commands such as `go mod tidy` before they run. Results are returned as a prioritized checklist with evidence, a proposed fix, the likely start command, and a record of what was checked. Review the upstream [Env Doctor documentation](https://justhandledlabs.com/skills/env-doctor/?utm_source=agentskillexchange&utm_medium=directory&utm_campaign=env_doctor) for the complete workflow and safety fixtures.

## Installation

No source-backed install or usage instructions could be extracted automatically. Review the upstream project before running this skill in a sensitive workflow.

- Source: https://github.com/justhandledlabs/skills/tree/main/skills/env-doctor-free

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.