Ext Ops Panel
Open dashboard
Comparison

dev-environment-doctor vs server-healthcheck

dev-environment-doctor is a plugin bundle for AI coding tools published by DhruvTilva. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). server-healthcheck is a plugin bundle for AI coding tools published by EvilFreelancer. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacedev-environment-doctorserver-healthcheck
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Community marketplace evilfreelancer/rpa-skills Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

dev-environment-doctor vs server-healthcheck
Factdev-environment-doctorserver-healthcheck
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)5Not published
LicenceMITMIT
Repository (differs)github.com/dhruvtilva/dev-env-doctorgithub.com/evilfreelancer/server-healthcheck
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-18

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

dev-environment-doctor

In its own words, on Claude Code: claude-plugins-community:

Detect and fix local environment issues before they break your workflow. Dev Environment Doctor runs safe, read-only checks for environment variables, services, and tool versions, and provides clear, actionable fixes to keep your development setup healthy.

server-healthcheck

In its own words, on Community GitHub marketplaces:

Check whether a host or a whole namespace of a fleet harness repository is healthy, read-only: a POSIX pass over boot history, clock, units, disks, OOM, containers, resolvers, ports, NVIDIA and Intel Arc GPUs and PCIe AER, drift against the host card, stacks against the mirror, and functional probes of every service, rolled up into healthy, warming up, degraded, broken or unreachable.

How to run each

dev-environment-doctor As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dev-environment-doctor@claude-community

server-healthcheck As a Claude Code plugin

Claude Code
/plugin marketplace add evilfreelancer/rpa-skills
/plugin install server-healthcheck@rpa-skills

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: dev-environment-doctor · What it can do: server-healthcheck · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built