hermes-stack-doctor
Use when a top-level, read-only Hermes health audit is needed across installation, updates, gateways, cron, profiles, skills, repositories, credential posture, persistence, and cost signals.
Profile →npx skills add asimons81/hermes-field-kit --skill hermes-stack-doctor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# hermes-stack-doctor ## Overview A capstone health check that discovers the installation architecture, delegates to focused evidence contracts, and reports one GREEN, YELLOW, or RED verdict without repairing the stack. The skill is evidence-first. It identifies unavailable evidence, separates facts from interpretations, and does not claim a repair or successful outcome merely because a command re
What does the hermes-stack-doctor skill do?
Use when a top-level, read-only Hermes health audit is needed across installation, updates, gateways, cron, profiles, skills, repositories, credential posture, persistence, and cost signals.
How do I install it?
Run `npx skills add asimons81/hermes-field-kit --skill hermes-stack-doctor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From asimons81/hermes-field-kit, a repository with 120 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.