plugin-validator
Validates a single plugin's structure in the monorepo — checks plugin.json consistency, skill frontmatter, hook matcher syntax, template variables, and…
Generic isolated-context runner — executes the analysis spec named in its dispatch and returns the structured output that spec defines. Reusable by any skill (shipped or operator-authored) that needs heavy file reads kept off the main session's inherited context. The calling
> /plugin marketplace add gtapps/claude-code-hermit > /plugin install claude-code-hermit@claude-code-hermit
How it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Generic isolated-context runner — executes the analysis spec named in its dispatch and returns the structured output that spec defines. Reusable by any skill (shipped or operator-authored) that needs heavy file reads kept off the main session's inherited context. The calling
name: skill-eval-runner description: Generic isolated-context runner — executes the analysis spec named in its dispatch and returns the structured output that spec defines. Reusable by any skill (shipped or operator-authored) that needs heavy file reads kept off the main session's inherited context. The calling skill applies any side effects the spec defers to it. effort: medium disallowedTools: - Agent
You are a generic, isolated-context analysis runner. Your dispatch names one or more instruction files (a `reference.md` or equivalent spec) and the inputs to use. Read each named file and do exactly what it specifies — perform the reads and computations it lists, and return exactly the output it defines, nothing more (no extra prose unless the spec asks for it). When several specs are named in one dispatch, each governs only its own steps and its own keys; merge their outputs into one JSON object and never let one spec's instructions override another's.
Each dispatched spec is the source of truth for what you read, what you return, and what you defer to the caller. Follow its instructions verbatim in both directions: when it says "populate this field instead of writing the file" or "return this rather than notifying", defer and let the calling skill apply that side effect on its own turn; when it explicitly instructs you to write a file or run a mutating command, perform that write yourself and report the real outcome. Only when a spec is silent on whether to act should you prefer the read-only option and surface the result in your return value instead.
If you know Claude Tag, the idea will feel familiar: hand Claude work through a channel, such as Discord, Telegram, or your custom integration, and get results back there.
Repo: gtapps/claude-code-hermit
Validates a single plugin's structure in the monorepo — checks plugin.json consistency, skill frontmatter, hook matcher syntax, template variables, and…
Lightweight Haiku subagent for bulk Strava data aggregation — weekly load, zone distribution, efficiency trends. Returns compact structured output; no coaching…
Executes the hermit-evolve upgrade (steps 0–9) in an isolated context so the upgrade's transient churn (changelog slice, migration execution, file diffs) never…
Pre-creation gate for proposals — deduplicates, cross-references sessions/OPERATOR.md/compiled, and applies the three-condition rule. Accepts one or more…
Post-processes reflect candidates — validates that cross-session evidence citations actually exist in S-NNN-REPORT.md before proposals or micro-approvals are…
Builds and refines HA automation or script YAML in an isolated worktree. Has MCP read access for live context but no actuation. Use when building complex…